Python · Advanced level

Advanced level · Module 6: Python Capstone: Deploying a Real Application · Lesson 2 of 5

Building in Sprints and Reporting Progress

Plan the capstone in short sprints with a task board, and keep the client informed with brief progress updates.

In this lesson you will

  • Break the scope into tasks for one-week sprints
  • Report progress, risks and decisions clearly

Key concepts

sprintbacklogtask boardprogress update

The lesson

Large projects fail when everything is left to the end. Breaking the work into one-week sprints, each ending with something that runs, shows progress early and exposes problems while there is still time to fix them.

A backlog lists all tasks in priority order; a task board (To do, Doing, Done) shows where each one stands. Trello, GitHub Projects or paper on a wall all work.

A weekly update to the client covers what was finished, what is next, any risks and any decisions needed. Short, regular updates build trust more than a long report at the end.

Step by step

  1. Turn the scope into a prioritised backlog.
  2. Plan the first sprint with tasks that fit one week.
  3. Set up a task board.
  4. Write the first weekly progress update.

Practice activity

Plan three sprints for your capstone and send two weekly updates to the instructor acting as client, adjusting the plan after the first sprint review.

Expected result: A backlog, a sprint plan, a task board kept up to date and two clear weekly updates.

Check your understanding

  1. Why should each sprint end with something that runs?

    Show answer

    It proves real progress, lets the client give feedback early and exposes problems before the deadline.

Taught live by an instructor — online or in person. Free course lessons are for self-study and do not lead to a certificate — see registration options.