Tip:
Highlight text to annotate it
X
Satisfying the customer through early and continues delivery of valuable
software is the highest priority of any agile team
let's take a look at planning work and reporting on progress
for scrum teams
Ruby Rails is a dev lead and here we can see her organizing work into several
themes using epics
epics enables scrum teams to organize large and growing backlogs
and track progress toward the big picture over multiples sprint
Ruby organizes stories into epics
so her team can deliver value incrementally and still planned big
picture work across multiple sprints
Ruby views the high-level progress on each epic from the plan mode
as she allocates work on the report board, epic reports show progress for each of
the larger features area
an epic can be contained within a version
or span across multiple versions Ruby works together with the product owner
Brandy Fender to plan the larger release version
Brandy keeps track for across the entire project by version
here Brandy can plan work across versions which contain functionality from multiple sprint
by selecting a version Brandy can see how the work is allocated across each print
from the start date Brandy uses for the version
historical velocity is calculated per day with three project completion dates
Brandy configures non-working days to make this even more accurate
and as the team gets closer to release this version report helps Brandy
keep stake holders properly informed
the entire team can find everything they need to know about work in progress
on the JIRA dashboard from a single glance
anyone can see the number of days remaining sprint burndown chart
stay on track to keep everyone focused on delivering quality products