All subjects · Information Technology · WIT13 2 hour written exam on data, enabling technologies and systems development

The agile approach: iterative, incremental, scrum and sprints

Edexcel IAL Information Technology · WIT13 2 hour written exam on data, enabling technologies and systems development

Agile approaches build a system in short cycles, delivering working parts frequently and responding to change. You need agile's concept and features, its phases, and the activities of scrum and sprints. The June 2025 paper's 12-mark essay was on a development method: strong answers covered benefits and drawbacks and applied them to the context (spec 15.3).

Practise this in the app: instant marking and a fix for every mistake. Free, no email needed to start.

Practise this lesson

Concept and features

Agile is a family of approaches that develop software in short cycles, with close and continuous involvement of the customer and the ability to change requirements as the project goes on.

Other features: working software is valued over heavy documentation; small, self-organising, cross-functional teams; frequent communication (often face to face or daily); continuous testing and integration.

Agile phases

PhaseWhat happens
RequirementsGather user needs as short user stories ('As a student I want to see my timetable so that I know where to go'); put them in a prioritised product backlog
PlanChoose the highest-priority stories for the next iteration; estimate effort; agree the iteration goal
DesignDesign just enough for the chosen stories: data, interface, logic
DevelopCode and test the stories; integrate them with the existing product
ReleaseDeliver a working increment to users; collect feedback, which feeds the next cycle's requirements

The phases repeat in each iteration.

Scrum and sprints

Scrum is a popular agile framework.

Advantages and disadvantages

Advantages: copes well with changing or unclear requirements; users see working software early and often, so misunderstandings are caught early; the most valuable features are delivered first, so benefits start sooner; continuous testing improves quality; high customer satisfaction and team motivation.

Disadvantages: needs the customer's time and commitment throughout; final cost and delivery date are hard to predict at the start; scope can keep growing; less documentation can make maintenance harder; works best with small, experienced, co-located teams; can be hard to apply to fixed-price contracts or heavily regulated projects.

Agile versus waterfall: choose agile when requirements are likely to change and the client can be closely involved; choose waterfall when requirements are fixed, documentation is essential and the timetable and budget must be agreed up front.

Worked example

A start-up is building a fitness app and is unsure which features users will want. Evaluate the use of agile (brief plan of a 12-mark answer).

  1. For: requirements are uncertain, so iterative sprints let the team release a basic app quickly and add features based on real user feedback.
  2. For: incremental releases mean the start-up can earn revenue and attract investors earlier.
  3. Against: the founders must act as product owner and give regular time; cost and launch date of the full app are hard to fix, which may worry investors.
  4. Against: light documentation could hinder new developers as the company grows.
  5. Judgement: agile is the better choice because uncertainty about features is the biggest risk, provided the founders commit to sprint reviews and keep a prioritised backlog.

Answer: A supported conclusion weighs both sides in context

Key idea: Agile: iterative (repeat cycles) and incremental (add working parts). Phases: requirements, plan, design, develop, release, repeated. Scrum: product owner, scrum master, team, backlog, sprints, daily scrum, review, retrospective. Best when requirements change and the client is involved.

Check yourself

  1. What does 'incremental' mean in agile development?
    • All the code is written at the end
    • Each cycle adds a working piece of functionality to the product
    • Requirements are fixed at the start
    • Each phase is signed off before the next
    Show answer

    Each cycle adds a working piece of functionality to the product. The product grows in usable increments.

  2. What does 'iterative' mean in agile development?
    • The project has one long phase
    • Testing happens only once
    • There is no planning
    • The development cycle is repeated, refining the product each time from feedback
    Show answer

    The development cycle is repeated, refining the product each time from feedback. Repeated cycles.

  3. Who prioritises the product backlog in scrum?
    • The scrum master
    • The product owner
    • The newest developer
    • The database administrator
    Show answer

    The product owner. The product owner represents the customer.

  4. What is the purpose of the daily scrum?
    • A full demonstration to the client
    • A review of the whole project budget
    • A short meeting where team members share progress, plans and blockers
    • A meeting to write the requirements specification
    Show answer

    A short meeting where team members share progress, plans and blockers. Coordination and spotting obstacles.

  5. What happens in a sprint retrospective?
    • The team reflects on how it worked and agrees improvements
    • The product is demonstrated to stakeholders
    • The final system is installed
    • Requirements are frozen for the rest of the project
    Show answer

    The team reflects on how it worked and agrees improvements. Improving the process.

  6. Which is a disadvantage of agile development?
    • Users never see working software
    • Requirements cannot change
    • The final cost and completion date are hard to predict at the start
    • There is no testing
    Show answer

    The final cost and completion date are hard to predict at the start. Flexible scope makes estimates harder.

  7. Explain why agile is better than waterfall when a client's requirements are likely to change.
    Show answer

    Agile works in short iterations and reprioritises the backlog after each one, so new or changed requirements can be included in the next sprint without redoing the whole project.. Short cycles, so changes absorbed.

Practise with instant feedback

Sources

Last updated 8 November 2026. Spotted a mistake? Tell us.