All projects have a plan, execute, inspect, accept model
In Business projects are “managed” to ensure accountability and control.
Project Management has become a practice and career unto itself.
There are myriad methods and tools for project management.
All are about “delivered on time and on budget”.
Let’s talk projects:
PDLC – What is it? Project Development Life Cycle: The most commonly used, and generally accepted, project management approach.. (aka SDLC) Feasibility Study
Classic PDLC Characteristics
Requirements & Tasks are well defined at outset.
Methodology is highly document driven.
Project roles are highly structured and well defined.
Communication is through PM and Sponsor.
Typically long cycle
Let’s try something
Must have at least two entrances.
Must have a roof of uniform color.
Must support a quarter
So, what happened?
Did the customer get what was wanted? Were the actual needs met?
After 30 years of PDLC… The 10th edition of the annual CHAOS report from The Standish Group, which researches the reasons for IT project failure in the United States, indicates that project success rates have increased to 34 percent of all projects. That’s more than a 100-percent improvement from the success rate found in the first study in 1994. Software Magazine, January 2005
It’s All About… Change!
The Agile Manifesto–a statement of values Agile Practice favors: Process and tools Individuals and interactions over Following a plan Responding to change over Comprehensive documentation Working Product over Contract negotiation Customer collaboration over
The Big Paradigm Shift Customer is part of team. Customer is removed Action Certain Knowledge Information Radiators. Communication by Document Co-location – one team. Multiple matrixed units in multiple locations make up team Incremental deliverables driven by value and constant learning. Predictable, all at once deliverables Assumed change means no fixed cost. Fixed Budgets Disciplined self managing teams. Project Managers We’re done when it’s done. Time Lines Agile Wants We’re used to
Guides the Agile Execution
Responsible for the process
Responsible for maximizing team productivity
Sets up and conducts meetings
Representative to management and team
Characteristics of a border collie or sheepdog
Performs the work directed by the Customer
Seven plus or minus two performers
Business and technical skills to build an increment of functionality
Responsible for estimating and committing to work
Full autonomy and authority during a Sprint
Is (or is the representative of) the Customer
Develops and maintains the Product Backlog
Prioritizes the Product Backlog
Empowered to make decisions for all customers and users
Presents and explains Product Backlog to team
User Stories – Simple statements of requirements written from the “customer's” point of view. “As an AP processor, I need to be able to retrieve and update vendor address information.”
Product Backlog – Collection of user stories that need to be addressed to consider the effort (Product) complete.
Sprint (aka Iteration) – A fixed length work period in which items taken from the backlog are satisfied. An Agile project is a sequence of sprints.
Sprint Planning Session – A team meeting in which the product owner reviews and explains each backlog items and it’s priority, the other team members task out the items and commit (or not) to performing each item, and the agile coach sets up the sprint management tools.
Sprint Review Session – At the closure of each sprint, work completed is presented and reviewed, lessons learned discussed, the overall sprint is evaluated and reviewed.
‘ Human-centric’ thinking for creating business value
Agile Manifesto. (2001). Manifesto for agile software development . Retrieved September 3, 2008, from http://www.agilemanifesto.org
What makes Agile work?
Better collaboration with business
More adapted to change/learning
Inspect & adapt
Focus on the real thing
Three heads are better than one
Short feedback loops
The Big Paradigm Shift – some reality Customer is in room as part of team. Information Radiators & Conversations Co-location. Incremental deliverables driven by value and constant learning. Assumed change means no fixed cost. Disciplined self managing teams. We’re done when it’s done. Agile Wants Core time in room Information Radiators captured electronically and posted. Daily Meetings Core time in room or on phone Pre-project user story sessions Cost Boxes – not more than x to spend. Collaboration between Coach and P.O. Time Boxes – not more than x time What Works Communication by Document Team spread out Customer is removed Predictable, all at once deliverables Fixed Budgets Project Managers Time Lines We’re used to
When is Agile best?
New Technology Introductions
New Process Designs
Projects driven by critical business timing.
Project with poorly defined needs
A word about ROI
Agile (138 pt.) and Traditional Methods (99 pt.)
Agile Methods fare better in all benefits categories
Agile Methods 459% better than Traditional Methods
Rico, D. F. (2008). What is the ROI of agile vs. traditional methods? TickIT International , 10 (4), 9-18.
59 Minute Scrum
Goal: Develop a brochure in a 2-day sprint
Sprint Planning Meeting 10min
At least 5 Product Backlog Items (do any)
2-3 Tasks per Item
Conduct the Sprint: Day 1 10 min
Conduct a Daily Standup 5 min
Conduct the Sprint: Day 2 10 min
Conduct a Sprint Review and Demo 5 min
Debrief the exercise as a Group 10 min
Source: ADM, 2004
PMI and Agile Oil and Water or Can They Co-exist? Kelly Snavely Tania Broome
Who are you?
Who is a practicing PM?
Who is not a PMP?
Who manages teams?
What’s the Mood of the Room?
Why are we here?
Session objective: To investigate the alignment of PMI and Agile
Can the PMBoK help Agile teams to identify needed project management tasks?
How can traditional project management activities be leveraged in Agile?
PMI Process Groups References: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Third Edition
Sprint Retrospective Evaluate the sprint and identify improvements Product Backlog Customer’s list of prioritized features Product Increment New functionality is demonstrated at end of every sprint Sprint Backlog Features assigned to the current sprint Sprint Daily Standup Meeting Scrum Process 1 - 4 Weeks 24 Hours
Fact or Fiction
PMBOK guide tells the audience what methodology to use
“ A project Management methodology can be either a formal mature process or an informal technique….” ( References: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Third Edition, Ch 4)
“ Methodology. A system of practices, techniques, procedures and rules used by those who work in a discipline ” ( References: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Third Edition, Glossery)
The third edition of PMBOK states it is up to the reader to determine what processes/methodology are most appropriate for their situation
PMI and Scrum: Oil and Water or Can they Co-exist? FICTION
PMI and Scrum: Oil and Water or Can they Co-exist? Fact or Fiction
PMI has an Agile SIG (Special Interest Group)
PMI has placed a moratorium on the creation of any new SIGs, until a new community governance model has been developed ( References: Agile Alliance http://www.agilealliance.com/show/1982)
There is a grass roots effort underway headed by Jesse Fewell to launch an Agile Virtual Community by Q2 2009. You can receive updates by subscribing to Yahoo Group pmiagile http://finance.groups.yahoo.com/group/pmiagile/
PMI and Scrum: Oil and Water or Can they Co-exist? Fact or Fiction
Scrum is CMMI level 2 certified
Scum itself is not ‘certified’
However, “there [is] no fundamental contradiction between agility and CMMI for the maturity/capability levels 2 and 3” (SEPG 2008 presentatioin by Sabine Canditt and Dr. Winfried Russwurm)
In 2006 Boltech Systems achieved CMMI level 4 while utilizing XP and Agile practices (www.agileadvocate.blogspot.com)
Things to Ponder
According to PMBOK: “the project manager, in collaboration with the project team, is always responsible for determining what processes are appropriate and the appropriate degree of rigor for each process”
PMI was founded with the purpose for members to share experiences in project management and discuss issues
APLN (Agile Project Leadership Network) mission: “Connecting, developing, and supporting great project leaders”
PMI and Scrum: Oil and Water or Can they Co-exist?
PMBOK Key Process Areas
Workshop: For each of the key PMBOK process areas consider the following:
How do these activities align with Agile?
Where and why should they take place relative to Scrum?
Do they conflict with Agile and if so, why?
The results of this workshop will be posted to the Agile Richmond Website http:// www.agilerichmond.org /
Other resources to consider:
Agile2008 Wiki (previous sessions results) http://agile2008toronto.pbwiki.com/PMI+and+Agile
The Software Project Manager's Bridge to Agility (The Agile Software Development Series) (Paperback) by Michele Sliger (Author), Stacia Broderick (Author)