Scrum & PMbok @ pmi

1.Scrum & PMI
Howcanthatgo well?
7.6.2011 - Saarbrcker Reihe

2. 7.6.2011 - Saarbrcker Reihe
Pierre Neis
PMO Advisor / Scrum & Lean Coach
3. Project management
4. Project Management Issues
5. Project Management
scope
time
resources
6. Agile Project Management
scope
time
Quality
resources
7. PMBOK
8. Product Life Cycle
Project
Project
Project
Project
Project
Project
Project
Project
9. Product Life Cycle for Small Project
10. I
P
C
E
M&C
Source Rita Mulcahy
11. Product Life Cycle for IT Projects
I
I
I
I
I
I
I
I
P
P
P
P
P
P
P
P
C
C
C
C
C
C
C
C
E
E
E
E
E
E
E
E
M&C
M&C
M&C
M&C
M&C
M&C
M&C
M&C
12. Value Steam
I
I
I
I
I
I
I
I
P
P
P
P
P
P
P
P
C
C
C
C
C
C
C
C
Lead Time
Lead Time
Lead Time
E
E
E
E
E
E
E
E
M&C
M&C
M&C
M&C
M&C
M&C
M&C
M&C
Lead Time
Lead Time
Lead Time
Lead Time
13. How long doesittake?
14. And yourcustomer?
15. Winston W. Royce
(19291995) was an Americancomputer scientist, director atLockheedSoftware Technology Center inAustin, Texas, and one of the leaders insoftware developmentin the second half of the 20th century.[1]He was the first who described theWaterfall modelforsoftware development, although Royce did not use the term "waterfall" in that article,[2]nor advocated the waterfall model as a workingmethodology.
16. Winston Royces Grandiose Model
Single Pass phased model to cope with US DoDregulatory requirements
I believe in this concept, but the implementation is risky and invites failure.
Winston W. Royce, Managing the development of large software systems, Aug 1970
Source: SilvanaWasitova
17. Winston Royces Recommendation
Iterations between phases, hopefully confined to successive steps
18. Winston Royces Problem Model
Problem:Testing phase, at the end ofDevelopment cycle, is the first time the integrated components are experienced.
Failure may require a major redesign, or modifying the requirements.
Can expect up to 100% schedule and/or cost overrun.
19. Scrum
21. Product Life Cycle
Project
Project
Project
Project
Project
Project
Project
Project
22. Product Life Cycle for Small Project
23. I
P
C
E
M&C
Scrum
24. Scrum Project Management Process
25. Project Charter
26. Roadmap
27. Product Backlog
High priority
Sprint
Medium Priority
Release
Future Releases
28. Assumptions
The customer do only have to define the vision
The customer do not really know the whole scope wetoo!
To maximize value and reducerisk, iteration planning sounds the best solution to measureeffectiveness
And give us freedom to on-going change
29. How?
30. Who are the stakeholders?
31. The power of Scrum comesfrom Time-boxing
4 hours
4 hours
4 hours
3hours
Sprint Planning
Sprint Review
Retrospective
Sprint Planning
15
Daily Meetings
SPRINT
30 days
32. PMBOK Strengths
Process oriented
Clearproject kickoff & administrative initiation
Enumeration of stakeholders, formalizedcommunication plan
More explicitly calls for cost management
Outlinesrisk management approach: identification, qualitative and quantitative analysis, response planning
33. Scrum Strengths
Empowered, self-organizing team
Collaboration, cross-fertilization, shared responsibilities & commitments
Allows for adjustments and learnings produce a better results
Risk management
smaller units of work more accurate
Frequent checks fewer surprises & delays
Welcomes voice of the customer
34. Scrum Values
35. Transparency
Inspection
adaptation
38. 3 Examples
39. Fixed time & Fixed Scope
3 months to build a CMS for a Global E-Commerce
40. Scrum to increase Releases
Global industrycompanyneeding to increase the releases of the R&D Departments
41. Scrum to increaseStakeholder participation
Support of Governments PMO
42. Resources
http://www.slideshare.net/wasitova/pmbok-and-scrum-best-of-both-worlds
43. Companies using SCRUM
44. Thanks
45. [email protected]

Business

Scrum & PMbok @ pmi