Miranda House Students: Agile or Waterfall? Comparing Project Management Internship Settings

Neither is universally better. Agile suits work where requirements will change and feedback arrives early. Waterfall suits work with fixed scope, fixed order and formal sign-offs. For a short internship, the useful question is which method the project already uses and which artifacts you can produce within it. This guide compares the two with sample artifacts, so Miranda House students can choose and explain their approach.

This is an independent guide. It makes no claim about what any department at Miranda House teaches, and it is not an official college document. The comparison is about the methods themselves and about how an internship project can be framed around them.

Why the methodology question matters in an internship

A project management internship usually lasts weeks, not years. That changes how the methods behave. A full Waterfall project might run for a year with six phases. In a short internship, you see one slice of it: a requirements document, a schedule, or a status report. A full Agile project runs many sprints. In an internship, you may see only one or two.

Interviewers and supervisors rarely want a lecture on definitions. They want to know whether you can take a vague task, break it down, track it and report on it. Both methods are ways of doing exactly that, and you can show them through concrete documents.

The two approaches in plain language

Waterfall

Work moves through phases in order: requirements, design, build, test, release. Each phase is completed and approved before the next begins. The plan is made up front, usually as a Gantt chart or milestone list, and changes go through a formal change request.

Agile

Work is divided into short cycles, often one to four weeks, called sprints (in Scrum) or handled as a continuous flow (in Kanban). A prioritised backlog holds the work. The team picks a slice, delivers it, reviews it with stakeholders and adjusts the next slice based on what it learned.

The hybrid reality

Many organisations use both. A fixed budget and deadline may be tracked in a phased plan, while the delivery team runs sprints inside it. Do not be surprised if an internship supervisor describes the process as “a bit of both”. That is common, and describing it accurately is a skill in itself.

Methodology comparison table with sample artifacts

This table is the core asset of this guide. Use it to compare how each method handles the same project concerns and which artifact you could produce as evidence of your work.

Sample artifact one: a sprint board

Illustrative example only. The tasks below are invented to show format and are not from any real organisation.

A sprint board has columns showing the state of each item. A basic board for a one-week sprint on a student-outreach newsletter might look like this:

Features that make a board useful rather than decorative:

• Each card has one owner and a clear “done” definition.
• Work in progress is limited, so cards do not pile up in a single column.
• The sprint goal is written at the top in one sentence.
• Blocked items are marked visibly, with the reason.
• The board is reviewed at a short daily check-in, even if the team is only two people.

Sample artifact two: a phased plan

Illustrative example only. Dates and tasks are invented for format.

A good phased plan does three things. It lists dependencies, so you know which task blocks which. It names the approver at each gate. It carries a baseline, so later you can measure how far reality drifted from the original.

Worked illustrative example: one task, two methods

This scenario is illustrative. It is not a real project and no output below was produced by running software.

The task: a small student society wants a simple online registration process for a two-day cultural festival and has three weeks to prepare.

The Waterfall version

1. Requirements (days 1–3): list every field the form needs, who approves registrations, and the capacity limit. The society president signs this off.
2. Design (days 4–6): sketch the form flow and the confirmation message. A faculty coordinator reviews it.
3. Build (days 7–12): create the form and the tracking sheet.
4. Test (days 13–15): ask five volunteers to register and log problems.
5. Release (days 16–21): open registrations and monitor.

Strength: everyone knows the whole plan and the approvals. Weakness: the volunteers only try the form on day 13, so a confusing question is discovered late.

The Agile version

1. Backlog (day 1): write stories such as “As a participant, I can register for an event in under two minutes.”
2. Sprint 1 (week 1): build the shortest working form with name, event and contact. Show it to three people on day 5.
3. Sprint 2 (week 2): add the capacity limit and confirmation message based on the feedback.
4. Sprint 3 (week 3): add reminders, fix issues, open registrations.

Strength: a usable form exists in week one and feedback shapes it. Weakness: without an agreed “must have” list, extra requests can keep expanding the backlog.

What you would write in a short report

A simple comparison for your supervisor could read: “Because requirements for the form were uncertain, a sprint approach was used, with a fixed capacity limit as the only non-negotiable. Three sprints were planned. Two risks were tracked: duplicate registrations and unclear event names.” That is specific, honest and brief.

How to choose between them for an internship project

Ask these questions in order:

1. Is the end date fixed by an external event, a regulator or a client? If yes, a phased plan for the outer schedule is sensible.
2. Are requirements known and unlikely to change? If yes, Waterfall-style planning works well.
3. Will users or stakeholders be available to give feedback every week? If yes, Agile cycles pay off.
4. Does the work produce something that can be shown in parts (pages, reports, prototypes)? If yes, sprint increments make sense.
5. Does an approval chain exist that cannot be skipped? If yes, include gates, whichever method you use.

If your answers split, use the hybrid approach: a phased outline with sprint-style execution inside the build phase.

A scorecard to rate your own project

Score each statement from 0 (not true) to 2 (clearly true). Add the Agile-leaning and Waterfall-leaning totals separately.

A difference of four points or more suggests a clear lean. Anything closer points to a hybrid. Treat the scorecard as a conversation tool, not a verdict.

Artifacts worth building whichever method you use

• One-page project brief: objective, scope, out-of-scope items, stakeholders, deadline.
• Risk log: risk, likelihood, impact, owner, next action.
• Decision log: what was decided, by whom, on which date, and why.
• Status update: done, next, blocked, in the same order every time.
• Lessons-learned note: three things that worked, three to change.

These five documents are method-neutral and are easy to include in a portfolio or a résumé project description.

Common mistakes when comparing the methods

• Treating Agile as “no planning”. Agile teams plan constantly; they just plan in smaller pieces.
• Treating Waterfall as outdated. Fixed-scope and regulated work still relies on phase gates.
• Renaming tasks as “sprints” without feedback. If no one reviews the output at the end, it is a to-do list with a new label.
• Using jargon to hide gaps. Say what was delivered and measured, not just which ceremony was held.
• Counting activity as progress. Track delivered outcomes, not hours or cards moved.

Turning the comparison into a short project you can complete

A practical way to learn is to run a small project twice on paper. Take a real task from your own life, such as organising a department event or a study-resource drive. Create the phased plan first, then convert the same scope into a backlog and two sprints. Compare where each method would have caught problems earlier.

If you want a structured, low-pressure place to practise, CareerSwami offers a free two-week online internship with 26 tracks, a free offer letter and a free completion certificate after successful completion. Whatever route you take, write down the plan, the artifacts and what you would change.

Miranda House and the Agile-versus-Waterfall internship comparison

Miranda House describes itself as a women’s institution under the University of Delhi. According to its 2024-25 Placement Cell brochure, it offers graduate and postgraduate courses. The same brochure lists B.A. Programme, B.El.Ed, B.A. (Hons) and B.Sc. (Hons) subjects (Botany, Chemistry, Mathematics, Physics, Zoology) and B.Sc. Programme in Physical and Life Sciences. It lists no computer science, IT or MBA programme. For most students here, a project management internship is therefore likely to sit outside the core degree subject, and the comparison in this article is best practised on a project drawn from your own subject or society work.

The first place to look is the college’s Placement Cell microsite, which has sections for The Process, Past Recruiters, Archive and Contact, plus a student login to a career advancement portal. The brochure says the cell arranges jobs and internship opportunities and extension lectures. In practice, ask the cell whether a self-found internship, such as one run in a Scrum-style sprint format or a phased Waterfall plan, can be recorded or needs prior notice. The brochure’s excerpt also mentions a One Student One Offer policy for cell-run recruitment. Read the current rules before applying through the cell so that a parallel self-found internship does not conflict with them.

No internship, project-work or credit rules for Miranda House were confirmed. Internships may be governed by University of Delhi scheme documents, so check those rather than assuming. The college also has an Academic Calendar page. Use it to fit a sprint cycle or a phase plan around term and exam dates, since a fixed-deadline Waterfall plan is harder to adjust than short sprints when exams arrive.

Checks before you commit to a project internship

• Email the Placement Cell via the contact section of its microsite. Ask whether external project internships need to be reported and in what format.
• Ask your department coordinator whether your course scheme has an internship or project component, and request the current University of Delhi scheme document for your programme.
• Check the Academic Calendar for term, exam and break dates before fixing sprint lengths or phase deadlines.
• Ask what proof is accepted: offer letter, completion certificate, or a short report. Get the answer in writing.
• Confirm whether any credit or record applies to short online internships. Do not assume it does.

Frequently Asked Questions

Is Agile better than Waterfall for a beginner?

Agile is easier to practise in small pieces because the cycles are short and feedback is quick. Waterfall teaches discipline in scope, scheduling and approvals. A beginner benefits from seeing both and from knowing when each fits.

Can I do Agile in a two-week internship?

Yes, in a compact form. Two one-week sprints, or one two-week sprint with a mid-point review, is enough to show backlog creation, prioritisation, a board and a retrospective.

Do I need a tool like Jira to show Agile work?

No. A spreadsheet or a simple board with columns is enough to demonstrate the method. The thinking behind the board matters more than the software.

What is the difference between a Gantt chart and a sprint board?

A Gantt chart shows tasks against a calendar and their dependencies, which suits a fixed plan. A sprint board shows the current state of work items, which suits a changing plan. They answer different questions: “when” versus “where are we now”.

Which artifacts should I put on a résumé?

Mention outcomes and one or two artifacts, such as a backlog of prioritised stories or a risk register you maintained. Describe what the artifact helped decide, and avoid exaggerating the scale of the project.

What is a retrospective and why does it matter?

It is a short meeting at the end of a cycle to discuss what worked, what did not and what to change. It is the Agile equivalent of a lessons-learned note, and it shows that you learn from your own work.

Can one project use both methods?

Yes. A common pattern is a phased outline for budget and deadline, with sprints used during execution. State clearly which parts follow which method so that the report is not confusing.

Will a short internship be accepted by my college for credit?

That depends on the college’s and university’s own rules, which this guide cannot state. Use the verification list above and ask in writing before you depend on it.

Related Project Management guides

• Shaheed Sukhdev College of Business Studies: Project Management Internship Skills to Prepare First
• Hansraj College Students: Project Management Internship Documentation Samples Worth Keeping
• Loyola College, Chennai: Project Management Internship Guide to Tools, Trackers and Demos
• All Project Management internship guides