Agile and Scrum

This Sommerville topic covers Agile practice through Scrum. You learn the roles and their responsibilities, the sprint cycle and its ceremonies, backlog management, and metrics like velocity and burndown that guide planning.

Relation 1 —

Write this relation with symbols exactly as in Software Engineering — Roger Pressman before substituting numbers. Examiners award partial marks for a correct setup even when arithmetic slips.

Relation 2 —

Write this relation with symbols exactly as in Software Engineering — Roger Pressman before substituting numbers. Examiners award partial marks for a correct setup even when arithmetic slips.

Relation 3 —

Write this relation with symbols exactly as in Software Engineering — Roger Pressman before substituting numbers. Examiners award partial marks for a correct setup even when arithmetic slips.

Agile responds to the reality that requirements change by delivering small, working increments frequently and adjusting based on feedback. Scrum structures this with a fixed-length sprint that produces a potentially shippable increment, a Product Owner who prioritises the backlog to maximise value, a Scrum Master who removes impediments and protects the process, and a self-organising development team. Velocity — the story points a team completes per sprint — is an empirical planning measure, not a target to inflate, and the burndown chart makes progress and slippage visible daily. The ceremonies (planning, standup, review, retrospective) create regular inspect-and-adapt points.

State assumptions explicitly before using any relation for agile and scrum — steady state, uniform properties, linear elastic material, ideal gas, incompressible flow, etc., as applicable.

Wrong assumptions invalidate the entire solution even when the formula is correct. In Software Engineering viva and GATE descriptive questions, listing valid assumptions often earns separate marks.

1. Read the question and list given data with SI units (common in Software Engineering papers).
2. Draw a neat labelled diagram where applicable — examiners in Indian universities award diagram marks even when arithmetic slips.
3. Identify which relation from this topic applies to agile and scrum.
4. Use equation 1: .
5. Use equation 2: .
6. Substitute values, compute, and verify units and sign (direction).
7. State conclusion in one line — e.g. safe/unsafe, stable/unstable, feasible/infeasible.

Agile and Scrum appears in product teams and IT services. In Indian it software curricula this topic is tested because it connects theory to SDLC, requirements, and quality.

GATE and semester exams often combine agile and scrum with earlier units — revise prerequisites before attempting mixed problems.

Industry interview panels sometimes ask: "Where did you use agile and scrum?" — answer with a lab, mini-project, or plant visit example if possible.

Students treat the Scrum Master as a project manager who assigns work, use velocity as a performance target across teams, and confuse the product backlog (all work) with the sprint backlog (this sprint’s commitment). Thinking Agile means no planning or documentation is a misconception.

Before attempting agile and scrum problems, confirm you can:

1. Roles: Product Owner, Scrum Master, Development Team
2. Artifacts: product backlog, sprint backlog, increment
3. The daily standup covers done, next, and blockers

Revise the solved examples in Software Engineering — Roger Pressman and one previous-year GATE or university paper for this unit.