PMGT5871 Chap.13 Sprint Planning and Agile Control in Jira
Sprint Planning and Agile Control in Jira
Weeks 11 to 13 put the Scrum plan into Jira, the tool used for the second group assignment. This chapter explains how Scrum tracks progress without traditional status reports, reads an ideal and actual burndown chart, and maps the Jira objects used to plan: issues, epics, sprints, versions, boards and reports.
It works a velocity forecast and an Agile cost estimate, then covers who controls a sprint, the speed boat retrospective and release planning. These weeks are assessed through practice rather than the final exam.
Group Assignment 2 asks for an Agile project plan built in Jira, and the individual reflection asks you to think about Agile planning, both due in Week 13. The Week 11 and 12 tutorials use the second case study to create epics, stories and sprints and then a board, burndown and velocity charts, while the final week is set aside for wrap-up, revision and questions about the Jira work.
What this chapter covers
- 01
Agile performance review without status reports
- 02
Task board and sprint burndown chart
- 03
Jira issues, epics, sprints and versions
- 04
Road maps and release planning
- 05
Velocity and forecasting
- 06
Agile cost estimation
- 07
Control by developers and the product owner
Worked example · free
Forecasting sprints and cost from velocity
- 1Velocity: (38 + 42 + 40) / 3 = 40 points per sprint.
- 1Sprints: 360 / 40 = 9.
- 1Time: 9 x 2 weeks = 18 weeks.
- 1Cost = time x rate: 18 x $24,000 = $432,000.
Key terms
- Burndown chart
- A graph of remaining sprint work over time, compared with an ideal straight-line burndown.
- Task board
- A board that displays the sprint backlog with each task marked as finished, under way or waiting.
- Release planning
- Deciding what one or more major releases should achieve and setting them up with the best chance of success.
- Jira version
- The Jira term for a release, which only project admins can create.
Sprint Planning and Agile Control in Jira FAQ
How does Scrum track progress without status reports?
Progress is tracked continuously through the daily scrum and the sprint review, supported by the task board and the sprint burndown chart. Deviations are corrected immediately under the principle of inspect, adapt and learn.
Who can cancel a sprint?
Only the product owner, even when stakeholders, the development team or the Scrum master recommend it. Within a sprint the self-managed developers decide measures themselves, such as moving an unachievable story to the next sprint.
How is an Agile project's cost estimated?
Start from the charter and an outline of the main epics, give the backlog rough story-point sizes, work out the team's velocity, convert the backlog into total time, and finally multiply that time by the rate for the people involved, as the Week 12 cost rule states.
What does a sprint burndown chart show?
It shows how much work is still outstanding before the sprint ends, how far actual progress has drifted from the ideal line, and how fast the team is really moving. The developers add a new point to the chart at the close of every working day.
What is the speed boat retrospective?
It is a model for running a retrospective. The boat is the Scrum team and the island its goal; sails and wind are what helped, anchors, rocks and icebergs what held it back, the sun what the team liked, and the reef obstacles expected later.
How is a sprint created in Jira?
Open the backlog of the Scrum project, click Create Sprint, drag stories from the backlog into the sprint, then start it. Progress is monitored on the sprint board, and the sprint is closed at the end. Releases are created separately as versions by project admins.
Exam move
Sketch a burndown chart for a ten-day sprint and draw three actual lines: on track, behind with a flat section, and ahead. For each, write what the team should discuss at the next daily scrum. Practise the velocity forecast and cost calculation with your own numbers, and add a sentence on how confident the forecast is given the spread of past sprints.
If you are building the Jira assignment, create the epics, stories, sprints and a version in that order, matching the sequence in the Week 11 slides, and keep the backlog prioritised as you go. In the reflection, use your own burndown and velocity charts as evidence: describe what they showed, what the team did about it and what you would change next time.
Working through Sprint Planning and Agile Control in Jira in PMGT5871? Sia is AskSia’s AI Project Management tutor — ask any PMGT5871 Sprint Planning and Agile Control in Jira question and get a clear, step-by-step explanation grounded in how PMGT5871 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
