Week 8 Project Presentation

AGILE PROJECT MANAGEMENT

*

GRANTHAM.EDU |

TRADITIONAL PM VERSUS AGILE METHODS

• Traditional PM Approach
• Concentrates on thorough, upfront planning
  of the entire project.
• Requires a high degree of predictability to be effective.
• Agile Project Management (Agile PM)
• Relies on incremental, iterative development cycles
  to complete less-predictable projects.
• Is ideal for exploratory projects in which requirements need to be discovered and new technology tested.
• Focuses on active collaboration between the project team and customer representatives.

*

GRANTHAM.EDU |

TRADITIONAL PROJECT MANAGEMENT VERSUS
AGILE PROJECT MANAGEMENT

*

GRANTHAM.EDU |

12 AGILE PRINCIPLES

*

GRANTHAM.EDU |

AGILE PROJECT MANAGEMENT

• Agile Project Management
• Is related to the rolling wave planning
  and scheduling project methodology.
• Uses iterations (“time boxes”) to develop a workable product that satisfies the customer and other key stakeholders.
• Stakeholders and customers review progress and re-evaluate priorities to ensure alignment with customer needs and company goals.
• Adjustments are made and a different iterative cycle begins that subsumes the work of the previous iterations and adds new capabilities to the evolving product.
• Advantages of Agile Project Management
• Useful in developing critical breakthrough technology or defining essential features
• Continuous integration, verification, and validation of the evolving product.
• Frequent demonstration of progress to increase the likelihood that the end product will satisfy customer needs.
• Early detection of defects and problems.

*

GRANTHAM.EDU |

AGILE PM PRINCIPLES

Focus on customer value

Iterative and incremental delivery

Experimentation and adaptation

Self-organization

Continuous improvement

*

GRANTHAM.EDU |

POPULAR AGILE PM METHODS

*

GRANTHAM.EDU |

AGILE SCRUM FRAMEWORK

*

GRANTHAM.EDU |

ROLES AND RESPONSIBILITIES IN THE SCRUM PROCESS

*

GRANTHAM.EDU |

SCRUM ARTIFACTS

• Product Backlog
• Requirements for a system, expressed as a prioritized list of Backlog Items
• Is managed and owned by a Product Owner
• Spreadsheet (typically)
• Usually is created during the Sprint Planning Meeting
• Can be changed and re-prioritized before each PM
• Sprint Backlog
• A subset of Product Backlog Items, which define the work for a Sprint
• Is created ONLY by Team members
• Each Item has it’s own status
• Should be updated every day

Burn down Charts

Are used to represent “work done”.

Are wonderful Information Radiators

Sprint Burn down Chart (progress of the Sprint)

Release Burn down Chart (progress of release)

Product Burn down chart (progress of the Product)

*

GRANTHAM.EDU |

KANBAN

• Kanban is a Japanese word that means "visual card".
• At Toyota, Kanban is the term used for the visual & physical signaling system that ties together the whole Lean Production system.
• Kanban as used in Lean Production is over a half century old.
• It is being adopted newly to some disciplines as software.

*

GRANTHAM.EDU |

LIMITATIONS AND CONCERNS OF AGILE

• It does not satisfy top management’s need for budget, scope, and schedule control.
• Its principles of self-organization and close collaboration can be incompatible with corporate cultures.
• Its methods appear to work best on small projects that require only five-nine dedicated team members to complete the work.
• It requires active customer involvement and cooperation.

*

GRANTHAM.EDU |

REFERENCES

Faris, R., and I. Abdelshafi, “Project Management and Agile: Perfect Fit,” 2006 PMI Global Congress Proceedings, Seattle, Washington.

Gale, S. F., “The Evolution of Agile,” PM Network, January 2012.

Griffiths, M., Using Agile Principles Alongside: A Guide to the Project Management Body of Knowledge, PMI Global Proceedings, Anaheim, California, 2004.

Highsmith, J., Agile Project Management (Boston: Addison Wesley, 2004).