Agile Project Management

1
Agile Project Management

• Presented by Raffi P. Tikidjian
• CSCI 577B Spring 2006
• Research Presentation

2
Agenda

• Background
• Agile Project Management Framework
• Phases
• Practices (for each phase, if time permits)
• Summary
• References
• QA

3
Introduction

• Builds on agile values
• Individuals and interactions
• Working software
• Customer Collaboration
• Responding to change

4
Business Objectives

• Continuous Innovation
• Product Adaptability
• Reduced Delivery Schedules
• People and Process Adaptability
• Reliable Results

5
Guiding Principles
Product Delivery
Deliver Customer Value
Employ Iterative Feature Delivery
Champion Technical Excellence
Leadership-Collaboration
Build Adaptive Teams
Simplify
Encourage Exploration
6
APM Framework
Envision
Explore
Speculate
Adaptive Action
Release Plan
Vision
Completed Features
Adapt
Feature List
Close
Final Product
7
Envision Phase

• Create a vision for customers and project team
• What
• Product Vision
• Project Scope
• Who
• Community of customers
• Product Managers
• Project Team Members
• Stakeholders
• How
• Collaboration between project team members

8
Speculate Phase

• Gather initial broad requirements
• Define workload
• Create a delivery plan
• Incorporate risk mitigation strategies
• Estimate project costs
• Generate other required administrative and
  financial information

9
Explore Phase

• Project Team Perspective
• Deliver product features.
• Project Manager Perspective
• Manage workload
• Technical practices
• Risk mitigation strategies
• Facilitate
• Collaboration
• Self-organizing project community
• Manage teams interactions
• Customers, product management and other
  stakeholders

10
Adapt Phase

• Monitor plans and Adapt - Control and
  correction
• Evaluate and make adaptations
• Product Functionality
• Product Quality
• Team Performance
• Project Status
• Feed results into re-planning effort for next
  iteration

11
Close Phase and Practice

• Project closing is both a Phase and Practice
• End of each iteration
• Mini project retrospective
• Intra-team learning of process and team dynamics
• End of project
• Celebration
• Clean up open items
• Project retrospective
• Inter-team learning shared within organization

12
Envision Practices

• Product Vision
• Product vision box and elevator test statement
• Product architecture and guiding principles
• Project Scope (Objectives and Constraints)
• Project data sheet
• Project Community
• Get the right people
• Participant identification
• Customer team-development team interface
• Approach
• Process and practice tailoring

13
Speculate Practices

• Feature Breakdown Structure
• Product feature list
• Feature cards
• Performance requirements cards
• Release Planning
• Release, milestone, iteration plan
• Iteration 0
• Project Risk Analysis
• Next Iteration Plan

14
Explore Practices

• Deliver on Vision and Objectives
• Workload management
• Technical Practices
• Low-cost change
• Project Community
• Coaching and team development
• Daily team integration meetings
• Participatory decision making
• Daily interactions with the customer team

15
Adapt Practices

• Customer Focus Groups (CFGs)
• Technical Reviews
• Team Performance Evaluations
• Project Status Reports
• Parking Lot Report by Business Activity
• Parking Lot Report by Month
• Delivery Performance (Features vs. Iterations)
• Features and Value Delivered
• Product and Technical Quality Assessment
• Technical Risk and Uncertainties Assessment (Risk
  Exposure vs. Iterations)
• Project Schedule (Predicted Finish Week vs.
  Iterations)

16
Summary

• Five Phases
• Envision ? Vision
• Speculate ? Release Plan
• Explore ? Features
• Adapt ? Change
• Close ? Final Product, Retrospect
• Iterative
• Feature-Driven
• Value-based

17
References

• Books
• Highsmith, Jim. Agile Project Management Boston,
  MA Addison-Wesley 2004
• Larman, Craig. Agile Iterative Development A
  Manager's Guide Boston, MA Addison-Wesley 2003
• Journal Articles
• Teaching agile project management to the
  PMIGriffiths, M.Agile Conference, 2005.
  Proceedings24-29 July 2005 Page(s)318 - 322
• Magazines
• The Agile Manifesto, by Jim Highsmith and Martin
  Fowler
• Cover article in Software Development magazine,
  August 2001.
• Websites
• Manifesto for Agile Software Development
• http//www.agilemanifesto.org/
• Project Management Declaration of Interdependence
• http//pmdoi.org/
• Agile Project Leadership Network (APLN)
• http//www.agileprojectmgt.com/

18
Question and Answer

• Questions?
• Answers?...Maybe