Agileindiapresentation2!18!2012 120223023147 Phpapp01
-
Upload
kukuhharsanto -
Category
Documents
-
view
5 -
download
0
description
Transcript of Agileindiapresentation2!18!2012 120223023147 Phpapp01
![Page 1: Agileindiapresentation2!18!2012 120223023147 Phpapp01](https://reader035.fdocuments.net/reader035/viewer/2022062515/563db79a550346aa9a8c98d8/html5/thumbnails/1.jpg)
1
Agile, PMI, and the PMBOK® Guide
Rory McCorkle, MBAPriya Sethuraman, MSProduct Managers – Credentials 18 February 2012
![Page 2: Agileindiapresentation2!18!2012 120223023147 Phpapp01](https://reader035.fdocuments.net/reader035/viewer/2022062515/563db79a550346aa9a8c98d8/html5/thumbnails/2.jpg)
2
PMI in Summary• Global Non-Profit Professional Association
−More than 600,000 members and credential holders−260 chapters, 182 countries
• Global Standards −13 global standards−3 million+ PMBOK® Guide in circulation
• Credentials −6 major credentials, used worldwide ( PMP® | CAPM® |
PgMP® | PMI-RMP® | PMI-SP® | PMI-ACPSM)• Professional and Market Research
−Academic Accreditation Program and Market Research• Advocate for Project Management excellence to
−Business, government, NGOs, C-level executives−Local and regional audiences: chapter outreach
![Page 3: Agileindiapresentation2!18!2012 120223023147 Phpapp01](https://reader035.fdocuments.net/reader035/viewer/2022062515/563db79a550346aa9a8c98d8/html5/thumbnails/3.jpg)
3
PMI’s History with Agile• Congress presentations since 2004
– Dedicated Agile track North America Congress 2011
• SeminarsWorld® sessions since 2005
• PMBOK® Guide 3rd & 4th edition references to
iterative development
• Agile reference sources in PMI Marketplace
![Page 4: Agileindiapresentation2!18!2012 120223023147 Phpapp01](https://reader035.fdocuments.net/reader035/viewer/2022062515/563db79a550346aa9a8c98d8/html5/thumbnails/4.jpg)
4
PMI’s History with Agile
![Page 5: Agileindiapresentation2!18!2012 120223023147 Phpapp01](https://reader035.fdocuments.net/reader035/viewer/2022062515/563db79a550346aa9a8c98d8/html5/thumbnails/5.jpg)
5
PMI’s History with Agile
![Page 6: Agileindiapresentation2!18!2012 120223023147 Phpapp01](https://reader035.fdocuments.net/reader035/viewer/2022062515/563db79a550346aa9a8c98d8/html5/thumbnails/6.jpg)
6
PMI’s History with Agile
![Page 7: Agileindiapresentation2!18!2012 120223023147 Phpapp01](https://reader035.fdocuments.net/reader035/viewer/2022062515/563db79a550346aa9a8c98d8/html5/thumbnails/7.jpg)
7
PMI’s History with Agile• February 2011: PMI Agile Certified Practitioner
(PMI-ACP) certification announced
• May 2011: PMI-ACP launched
• January 2012: First class of 515 PMI-ACP
credential holders awarded (59 from India)
![Page 8: Agileindiapresentation2!18!2012 120223023147 Phpapp01](https://reader035.fdocuments.net/reader035/viewer/2022062515/563db79a550346aa9a8c98d8/html5/thumbnails/8.jpg)
8
PMI’s History with Agile
![Page 9: Agileindiapresentation2!18!2012 120223023147 Phpapp01](https://reader035.fdocuments.net/reader035/viewer/2022062515/563db79a550346aa9a8c98d8/html5/thumbnails/9.jpg)
9
PMI’s History with Agile
![Page 10: Agileindiapresentation2!18!2012 120223023147 Phpapp01](https://reader035.fdocuments.net/reader035/viewer/2022062515/563db79a550346aa9a8c98d8/html5/thumbnails/10.jpg)
10
Usefulness of Agile project management to the organization• 71% of the respondents said Agile project
management is valuable to their organization.
![Page 11: Agileindiapresentation2!18!2012 120223023147 Phpapp01](https://reader035.fdocuments.net/reader035/viewer/2022062515/563db79a550346aa9a8c98d8/html5/thumbnails/11.jpg)
11
How valuable is Agile project management in managing your projects?
![Page 12: Agileindiapresentation2!18!2012 120223023147 Phpapp01](https://reader035.fdocuments.net/reader035/viewer/2022062515/563db79a550346aa9a8c98d8/html5/thumbnails/12.jpg)
12
PMI’s Agile Community of Practice
• Open to all
PMI
members
• Has over
13,000
subscribers
DiscussionsWebinars
Ask the Community
BlogsWikis
![Page 13: Agileindiapresentation2!18!2012 120223023147 Phpapp01](https://reader035.fdocuments.net/reader035/viewer/2022062515/563db79a550346aa9a8c98d8/html5/thumbnails/13.jpg)
13
Project Management Body of Knowledge (PMBOK® Guide)
![Page 14: Agileindiapresentation2!18!2012 120223023147 Phpapp01](https://reader035.fdocuments.net/reader035/viewer/2022062515/563db79a550346aa9a8c98d8/html5/thumbnails/14.jpg)
14
Project Management Body of Knowledge (PMBOK® Guide)
![Page 15: Agileindiapresentation2!18!2012 120223023147 Phpapp01](https://reader035.fdocuments.net/reader035/viewer/2022062515/563db79a550346aa9a8c98d8/html5/thumbnails/15.jpg)
15
Traditional vs. Agile PMTraditional:• Plan what you expect to
happen
Agile:Plan what you expect to
happen with detail appropriate to the horizon
• Enforce that what happens is the same as what is planned– Directive management– Control, control, control
• Use change control to manage change– Change Control Board– Defect Management
“Control” is through inspection and adaptation– Reviews and Retrospectives– Self-Organizing Teams
Use Agile practices to manage change:– Continuous feedback loops– Iterative and incremental
development– Prioritized backlogs
![Page 16: Agileindiapresentation2!18!2012 120223023147 Phpapp01](https://reader035.fdocuments.net/reader035/viewer/2022062515/563db79a550346aa9a8c98d8/html5/thumbnails/16.jpg)
16
The mapping of PMBOK Guide practice to Agile practices courtesy of Michelle Sliger (Sliger Consulting) and her text Bridge to Agility
![Page 17: Agileindiapresentation2!18!2012 120223023147 Phpapp01](https://reader035.fdocuments.net/reader035/viewer/2022062515/563db79a550346aa9a8c98d8/html5/thumbnails/17.jpg)
17
Integration Management
Traditional
Project Plan Development
Project Plan Execution
Direct, Manage, Monitor, Control
Integrated Change Control
AgileRelease and Iteration
Planning
Iteration Work
Facilitate, Serve, Lead, Collaborate
Constant Feedback and a Ranked
Backlog≈
≈
≈
≈
![Page 18: Agileindiapresentation2!18!2012 120223023147 Phpapp01](https://reader035.fdocuments.net/reader035/viewer/2022062515/563db79a550346aa9a8c98d8/html5/thumbnails/18.jpg)
18
Scope Management
Traditional
Scope Definition
Create WBS
Scope Verification
Scope Change Control
AgileBacklog and Planning
Meetings
Release and Iteration Plans (FBS)
Feature Acceptance
Constant Feedback and the Ranked
Backlog≈
≈
≈
≈
![Page 19: Agileindiapresentation2!18!2012 120223023147 Phpapp01](https://reader035.fdocuments.net/reader035/viewer/2022062515/563db79a550346aa9a8c98d8/html5/thumbnails/19.jpg)
19
Scope ManagementAcceptance criteria for the feature is written on the back of the card. This is the basis for the test cases.
Passing test cases aren’t enough to indicate acceptance – the Product Owner must accept each story.
![Page 20: Agileindiapresentation2!18!2012 120223023147 Phpapp01](https://reader035.fdocuments.net/reader035/viewer/2022062515/563db79a550346aa9a8c98d8/html5/thumbnails/20.jpg)
20
Scope Management
![Page 21: Agileindiapresentation2!18!2012 120223023147 Phpapp01](https://reader035.fdocuments.net/reader035/viewer/2022062515/563db79a550346aa9a8c98d8/html5/thumbnails/21.jpg)
21
Quality Management Traditiona
lQuality Planning
Quality Assurance
Quality Control
Agile
Definition of “Done”
QA involved from the beginning,
and…
Reviews and Retrospectives
Test early and often; feature acceptance
≈
≈
≈
![Page 22: Agileindiapresentation2!18!2012 120223023147 Phpapp01](https://reader035.fdocuments.net/reader035/viewer/2022062515/563db79a550346aa9a8c98d8/html5/thumbnails/22.jpg)
22
Risk Management
Traditional
Risk Identification, Qualitative & Quantitative
Analysis, Response Planning
Monitoring & Controlling
Agile
Iteration Planning, Daily Stand-ups,
Metrics, and Retrospectives
Daily Stand-ups and Highly Visible Information Radiators
≈
≈
![Page 23: Agileindiapresentation2!18!2012 120223023147 Phpapp01](https://reader035.fdocuments.net/reader035/viewer/2022062515/563db79a550346aa9a8c98d8/html5/thumbnails/23.jpg)
23
Agile Framework Addresses Core Risks• Intrinsic schedule flaw (estimates that are wrong and undoable
from day one, often based on wishful thinking) Detailed estimation is done at the beginning of each iteration
• Specification breakdown (failure to achieve stakeholder consensus on what to build) Assignment of a product owner who owns the backlog of work
• Scope creep (additional requirements that inflate the initially accepted set) Change is expected and welcome, at the beginning of each iteration
• Personnel loss Self-organizing teams experience greater job satisfaction
• Productivity variation (difference between assumed and actual performance) Demos of working code every iteration
![Page 24: Agileindiapresentation2!18!2012 120223023147 Phpapp01](https://reader035.fdocuments.net/reader035/viewer/2022062515/563db79a550346aa9a8c98d8/html5/thumbnails/24.jpg)
24
Summary• Scope is defined at a granularity that is
appropriate for the time horizon
• Scope is verified by the acceptance of each
feature by the customer
• Work Breakdown Structures become Feature
Breakdown Structures
• Gantt charts are not typically used; instead
progress charts help us to track progress
![Page 25: Agileindiapresentation2!18!2012 120223023147 Phpapp01](https://reader035.fdocuments.net/reader035/viewer/2022062515/563db79a550346aa9a8c98d8/html5/thumbnails/25.jpg)
25
Summary• Test-driven development and cross-functional
teams help to bring quality assurance and
planning activities forward to the beginning of the
project, and continue throughout the project
• Bugs are found and fixed in the iteration; features
are then accepted by the customer
• The nature of agile framework allows core risks to
be addressed by the team throughout the project
![Page 26: Agileindiapresentation2!18!2012 120223023147 Phpapp01](https://reader035.fdocuments.net/reader035/viewer/2022062515/563db79a550346aa9a8c98d8/html5/thumbnails/26.jpg)
26
Questions?
www.pmi.org/agile