Eklavya University Students: Prioritising a Backlog With MoSCoW When Resources Are Tiny

With tiny resources, use MoSCoW by first fixing a hard capacity limit, then sorting every backlog item through written must-have tests. If an item fails the tests, it cannot be a Must, however much someone likes it. For a 14-day internship, cap Musts at roughly half your available effort so there is room to absorb surprises.

This guide gives you a worksheet, a worked 15-item backlog and scripts for the awkward conversations that follow. A brief for a four-week project is compressed here into a 14-day plan, so every number below is scaled to two weeks.

Why MoSCoW suits a two-person, two-week project

MoSCoW sorts work into Must have, Should have, Could have and Won’t have (this time). Its strength for students is that it forces a decision about what the project cannot do without. Scoring models such as RICE need reach and impact data you rarely have in a student project. MoSCoW needs only judgement, and the worksheet below makes that judgement explicit and checkable.

The common failure is that everything becomes a Must. A team of two with about 14 days and a few hours daily cannot build twelve Musts. The fix is not stricter wording but a capacity budget set before sorting.

Step zero: set the capacity budget before touching the backlog

Calculate real capacity first. Illustrative figures, to be replaced with yours:

• Working days available: 14 calendar days, minus any days you know you cannot work (exams, travel, festivals). Say 11 usable days.
• Hours per person per day: be honest. Say 2.5 hours.
• People: 2.
• Gross capacity: 11 × 2.5 × 2 = 55 hours.
• Reserve 20% for review, rework and the final write-up: about 11 hours. Net build capacity: 44 hours.
• Must ceiling: no more than 50-60% of net capacity, roughly 22-26 hours.

The remaining capacity is for Shoulds, and Coulds only if everything goes well. This ceiling is the most useful rule in the whole method.

The MoSCoW worksheet: must-have tests tied to the project goal

Before sorting, write a one-sentence project goal and a single measurable success outcome, for example: “A first-year student can find and book a free mentoring slot in under two minutes.” Then run each item through the tests below. An item is a Must only if it passes at least the first three.

Items that pass tests 1 to 3 but fail 5 are not quietly kept as Musts. They trigger a scope conversation: simplify the item, borrow a skill, or change the goal.

The blank worksheet to copy

Add rows as needed. Keep a running total of Must hours at the bottom and compare it with your ceiling after every sort.

Worked backlog: sorting 15 items for an illustrative campus mentoring-slot app

This example is illustrative. The project, estimates and decisions are invented to demonstrate the method; nothing here was built or tested.

Goal: a student can find and book a free mentoring slot in under two minutes. Net capacity: 44 hours. Must ceiling: 24 hours.

Musts total 4+5+2+4+4+3 = 22 hours, under the 24-hour ceiling. Shoulds total 12 hours (7, 8, 9), for a running total of 34, which fits within 44 with 10 hours spare. Coulds total 11 hours, so only some would be attempted.

What the sort revealed

• Item 5 was debated. The workaround test said an admin could edit a spreadsheet. The team kept it as a Must only because neither member could reliably maintain the sheet daily. Writing down this reason matters; if the situation changes, it drops to Should.
• Item 6 passed only three tests, but it is a Must because it affects the headline goal directly.
• Items 13 to 15 are Won’t, but they are recorded, not deleted. A visible Won’t list shows reviewers you considered them.

A 14-day schedule built from the sorted backlog

1. Days 1-2: write the goal and success outcome, set the capacity budget, list every idea.
2. Days 3-4: estimate hours, run the six tests, sort, check the Must ceiling.
3. Days 5-9: build Musts only, in dependency order. Review at the end of day 9.
4. Days 10-12: build Shoulds in order of effort versus value. Stop starting new items on day 12.
5. Days 13-14: test the user journey, fix defects, write the summary of what was shipped and what was deliberately left out.

Trade-off conversations: scripts for pushback on a tiny team

Sorting is the easy part. Defending it to a mentor, a teammate or a stakeholder is where students struggle. Use these scripts and adapt them.

When a teammate wants their favourite feature as a Must

“Let’s run it through the six tests. Which step of the booking journey breaks without it? If we can’t name one, it goes in Should, and it moves up if we finish Musts early.”

When a reviewer asks for something new mid-project

“We can add it. Our capacity is full, so something of similar size has to leave. These are the Should items by hours; which one would you swap out?” This makes the trade-off visible without a refusal.

When a Must turns out to be too big

Split it. Ask what the smallest version is that still passes tests 1 and 2. A booking form with two fields is a Must; validation rules and styling are Shoulds.

When estimates slip

• Check at the end of day 5 whether Must hours burned are within 20% of the plan.
• If not, cut Shoulds first, never the testing time.
• Tell your reviewer early, with the revised list, rather than on day 13.

Common ways a MoSCoW sort quietly goes wrong in student projects

• Skipping the capacity number. Without a ceiling, Must becomes a synonym for “important”.
• Mixing goals and features. “Good user experience” is not a backlog item. Rewrite it as testable work, such as “booking takes three taps or fewer”.
• Treating Should as free. Shoulds still consume hours; they are simply the first to be cut.
• Deleting Won’ts. Keep them in a visible list so the decision is documented and can be revisited.
• Never re-sorting. Revisit the sheet on days 5 and 9, since estimates and knowledge change.

Eklavya University students: using a MoSCoW backlog for internship and project documentation

Eklavya University describes itself on its homepage as a private university with its address on Sagar Road, Damoh, and lists 2026-27 admissions as open. The Management school page lists BBA, PGDM, MBA and Ph.D. programmes and says the school organises internships, short-term training programmes and industry-interface events, but it gives no internship rules. For technical students, the Syllabus page offers scheme-and-syllabus PDFs for B.Tech CSE and several postgraduate programmes; the page was last modified in April 2022, so check that it matches your batch.

For this article, the practical point is documentation. A sorted MoSCoW sheet gives you evidence of how you made decisions, which is useful for a project report, a viva or an interview, whatever your programme. The university’s T&P Team page (last modified September 2024) lists the Training, Placement and Corporate Relations leadership, so that is the natural office to ask about how external internships are treated.

What is not verified is how an online internship is treated for your programme: duration, credits, evaluation, required documents and whether a certificate is accepted. Do not assume any of it. If you want a free, short project to practise on, the free two-week online internship from CareerSwami offers an offer letter and a completion certificate after successful completion, across 26 tracks. CareerSwami is independent and not affiliated with the university.

Steps to verify how your internship work will be recognised

1. Ask your department office or programme coordinator in writing whether an internship or project regulation applies to your batch, and request the document itself.
2. Open the Public Mandatory Disclosure page linked from the university homepage and note any regulation or notice relevant to training or internships.
3. Download the syllabus PDF for your programme and year, and look for any internship, industrial training or project component and its credits.
4. Email the Training and Placement Cell asking whether online internships are accepted and what proof (offer letter, certificate, report) they require.
5. Ask whether approval is needed before starting, and keep the reply as an email or signed note.
6. Confirm your semester-break and submission dates with your department so the 14 days fit your calendar.

Printable checklist: before you lock the backlog

• Goal sentence and success outcome written down.
• Capacity in hours calculated, with a 20% reserve.
• Every item has an hour estimate.
• Every Must has a named journey step that breaks without it.
• Must hours are at or below 50-60% of net capacity.
• Won’t items are listed with reasons.
• Re-sort dates set for days 5 and 9.

Frequently Asked Questions

How many Must-have items is too many for a 14-day project?

Judge by hours, not count. Keep Must effort to about half to 60% of net capacity. For two people on a short project, that often means five to seven small Musts.

Can a Won’t item come back later in the same project?

Yes. Won’t means not this time. If capacity opens up, promote it through the same six tests rather than on enthusiasm.

What if my mentor insists everything is a Must?

Show the capacity arithmetic and ask which Must they would drop if hours run out. Putting numbers in front of them usually shifts the conversation to real priorities.

Is MoSCoW better than RICE for student projects?

For tiny projects with no usage data, MoSCoW is usually easier because it needs no reach or impact figures. RICE becomes useful when you have real user numbers.

How do I estimate hours if I have never built this before?

Break each item into tasks, estimate each in half-hour steps, and add a buffer to unfamiliar tasks. Compare estimates against actuals on day 5 and adjust.

Should bug fixes go in the MoSCoW list?

Yes, if they affect the core journey, treat them as Musts. Cosmetic defects are normally Coulds. Reserve your 20% buffer for them.

Will a MoSCoW sheet count in my university’s internship evaluation?

That depends on rules that should be confirmed in writing with your department or placement cell. Even without formal credit, the sheet is useful evidence of your decisions in a report or interview.

Can I apply this method to a CareerSwami product management internship task?

Yes. A free 14-day internship is short enough that the capacity budget and Must ceiling are essential, so run the six tests on whatever task list your track gives you.