PMGT5887 Chap.4 Story Points, Sprints, Releases and Jira Reports
Story Points, Sprints, Releases and Jira Reports
Week 4 moves from writing stories to planning and tracking them, and this chapter follows the same path. It explains story points as relative measures of complexity, effort and uncertainty, the Fibonacci-like scale that widens as items grow, the T-shirt sizes used to introduce it, and Planning Poker as a consensus method whose discussion matters as much as its number.
It then covers velocity, the completed points per sprint that turn history into a forecast, and works a release forecast with a scope change. In Jira it walks through creating, starting and completing sprints, the conditions for starting one, and release planning with versions, including the scheduling options and the overbooked warning.
The chapter closes on reporting: reading a burndown chart for scope creep and a likely miss, adding columns and column limits to a board, and building a dashboard from gadgets that a team can see at a glance, the electronic form of an information radiator. Every forecast in the chapter is worked with printed numbers.
What this chapter covers
- 01
Story points and the Fibonacci-like scale
- 02
T-shirt sizing and Planning Poker
- 03
Velocity and release forecasts
- 04
Creating, starting and completing sprints
- 05
Release planning and versions in Jira
- 06
Reading a burndown chart
- 07
Board columns, limits and dashboards
Worked example · free
Forecasting a release from velocity
- +1Average velocity = (16 + 20 + 18) / 3 = 54 / 3 = 18 points per sprint.
- +1Sprints needed = 90 / 18 = 5 sprints, which is 10 weeks at two weeks each.
- +1A one-third capacity drop for one sprint gives about 12 points that sprint, leaving 78 points for later sprints.
- +178 / 18 = 4.33, which rounds up to 5 further sprints, so 6 sprints or 12 weeks in total.
Key terms
- Story Point
- A relative unit for the complexity, effort and uncertainty of a backlog item, not a measure of hours.
- Planning Poker
- A consensus estimating technique: private estimates, discussion of large differences, then re-estimating.
- Burndown Chart
- A chart of work remaining against time in a sprint or epic, showing progress and scope creep.
- Release Plan
- A plan for when sets of usable functionality will reach the customer over the next few releases.
- Information Radiator
- Any display placed where a team and passers-by can see the latest project information at a glance.
Story Points, Sprints, Releases and Jira Reports FAQ
Why do agile teams estimate in points rather than hours?
Points describe how hard an item is relative to others, which people judge more reliably than exact hours. The scale's widening gaps also stop teams pretending to precision on large, uncertain items.
Does a nearly finished story count toward velocity?
No. Velocity is the total story points of completed features only, so a story that is 90 percent done counts zero until it is finished. Splitting stories more finely makes velocity steadier.
When can I start a sprint in Jira?
Only when no other sprint is active, unless parallel sprints are enabled, and only for the sprint at the top of the backlog. Reorder the sprints if you need to start a later one.
What is the difference between a release plan and a product roadmap?
A roadmap gives the high-level scope and timeline for the product. A release plan goes into more detail but only for the next few releases, not years ahead.
Who can create a version in Jira?
Only project administrators can create versions, which is how Jira represents releases. They can be created from the Releases page or from the Versions panel on the backlog, and stories are then dragged onto them.
Assessment move
Practise the velocity chain until it is mechanical: average, divide, round up, multiply by sprint length. Sketch two burndown charts, one healthy and one with scope creep, and label what each part means. In Jira, create a sprint, a version and a dashboard with two gadgets so that the menu paths are familiar. Review the four questions a release plan answers aloud before the quiz.
When you study the burndown, describe each segment in words: flat means nothing finished, a rise means scope was added, a steep fall means stories closed together. Being able to narrate a chart is what a short-answer question about reports usually needs, and it also helps in the team presentation.
Working through Story Points, Sprints, Releases and Jira Reports in PMGT5887? Sia is AskSia’s AI Project Management tutor — ask any PMGT5887 Story Points, Sprints, Releases and Jira Reports question and get a clear, step-by-step explanation grounded in how PMGT5887 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
