Abstract: In many companies (especially large ones) there is a need to have one report showing the progress of all projects in a portfolio. These progress reports are typically based on phases because that is traditionally how projects were run and reported. But phase-based metrics are not a good fit for all projects. Many methodologies (such as Scrum and Kanban) are based on outcomes and not phases.
Instead of forcing all teams to create artificial phases to report against, we can look at a different approach to metrics that will allow each kind of project or implementation team to track progress in a meaningful way for them and yet roll-up into one view of progress for the portfolio.
During this talk, we will review different ways of reporting progress at a project level, then will show how to roll that data up into one report of progress for the portfolio. By creating a progress report that is not tied to one specific methodology, we make it possible for any team or project to work in the way that best fits the work and still have a consistent way to report on progress. Finally, we will review methods for using the new progress report to determine which projects may have issues, determine how serious the issues may be, and decide what to do about them.
Example reports and report templates will be available for download to session participants.
Learning Outcomes: - Understand the importance of defining and estimating work items for reporting progress
- Learn about different kinds of scope items and when each is appropriate
- Learn how to report on progress based on scope items
- Understand the importance of trends in interpreting results
- Learn how to interpret the results at the portfolio level
Attachments:
