Download as ZIP, PPTX
Uploaded byguy_davis
Project Monitoring and Control
This document discusses project monitoring and control using earned value analysis (EVA) and burn graphs. It provides an overview of EVA, including its origins, explanations of key EVA concepts and metrics, examples of how to apply EVA, and potential shortcomings. It also covers burn graphs as a visual project monitoring tool, how they can be used in agile projects, and examples of burn graph types. Tools for implementing EVA and burn graphs are listed. The document concludes with potential discussion points about applying EVA and adopting burn graphs.
More Related Content
Similar to Project Monitoring and Control
Editor's Notes
- #29 Lean production is a manufacturing process developed at Toyota. Focuses on responding to change to minimize inefficiency. Does not center on long-term planning. (1970s and 1980s) There is a “Lean Software Development” process
- #30 Used heavily in Scrum as the primary project progress metric. Levels of abstraction: Task Request (user story, requirement, use case) Milestone (sprint backlog) Overall project (product backlog) For higher levels, must take into account the project velocity (team member availability)
- #31 Product Backlog: Tradeoffs between cost, time, functionality, and quality (four pillars) Stress that by repeatedly updating and displaying the product backlog graph, management sees the effects of their choices. They can alter priorities with some understanding of the impact. Allows them to steer the project. Sprint Backlog: Allows team to see the impact of their estimates Each team will develop a signature Watch out for deviations from normal practice...
- #32 Just want to show that you don't always get a pretty sloped graph in the real world. This is the burn-down graph of a request I was handling at work. It looked complete after iteration #1, but we found an ambiguity in the requirements that required we revisit it. That's why there are two tasks. Gantt chart is just to elaborate the progress changes.
- #33 Need to find some sources about these as I'm basically just making assumptions!
- #34 Just a burn-up graph... Better than milestone % complete as this graph suffers from “false reporting” problem. People say they're 90% finished forever. Better than features complete graph as this ignores work-in progress.
- #36 Note: I'd like to give a demonstration of OPT if we have time. I can have it on my laptop or off my server via an PC with a web-browser.