You are set with you team on the Daily Scrum
Stand Up. Your Sprint Planning and Sprint Retrospectives are
flying smoothly. You got your Backlog grooming down to a T.
Yet with all the things going so smoothly your Project Owner
is still uneasy on the project's end date. Sprints every 2
or 3 weeks does not make them comfortable regarding when the
project will be finished.
I’ll show you an example if you are using JIRA. You
can utilize an Epic Burndown Report and provide a view of
the end date to your Project Owner.
A Scrum Master might provide an Epic Burndown report "As Is"
to the project owner. However, this does not provide a
possible end date which will further make the Project Owner
Epic Burndown reports provide all the Sprints that have been
completed, the number of Story points committed by the team
and completed during a particular Sprint, as well as
Incomplete Stories and their associated Story points.
Below is a sample Epic Burndown report.
All you have to do is export all the Completed Sprint
Stories as Tasks, with the Sprint start and end dates. Since
you already have the number of Stories that your team can
produce during a Sprint, and you have your Incomplete
Stories priorities in the Backlog, break down all Incomplete
Stories into the 2 or 3 week future Sprints increments.
Now you have a completion date to show to the Project Owner.
So use you Agile and presentation skills and remember to
make your Project Owner feel at ease.
- For previous articles see PMINJ Past
Newsletters. and PM
- If you have a suggestion for a future topic or want to
share your own success stories, contact Igor at
- To learn more about Igor check his LinkedIn Profile.
- For next steps on Project Manager ladder visit: WITS show where leaders and
experts provide expertise in what it takes to succeed in
career, in job and in personal life.