PMBOK Guide Grid Crossover to Agile

Transcription

1 PMBOK Guide Grid Crossover to Agile Seeing Agile Practices Hidden in Traditional Standards Copyright, GR8PM, Inc, 2013, all rights reserved. No part of this presentation may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except as permitted under Section 107 or 108 of the 1976 United States Copyright Act, without prior written permission.

2 Scope Time Cost Process Groups Develop Develop Plan Develop Plan the overall project good. Plan Develop Execution Work Direct Perform and Integrated Manage Execution Fact Perform Perform Close or Work Perform Integrated Close or, in the context of managing a project, is making choices about where to concentrate resources and effort on any given day, anticipating potential issues, dealing with these issues before they become critical, and coordinating work for PMBOK Guide, Third Edition management is a juggling act of trade-offs and coordination as part of balancing the project execution and the expectations of the stakeholders. 23 Develop Scope Scope Time Cost Process Groups Develop Plan Execution Define Scope Create WBS Fact Scope Close or Work Verify Scope Scope Scope includes the processes required to ensure that the project includes all the work required, and only the work required, to complete the project Estimate successfully. Cost PMBOK Guide, Third Edition Plan Perform Perform Which is riskier, 2 critical paths or 1? Traditional fixes scope and tries to control 2 variables - time and cost. Agile fixes those two and controls 1 variable - scope

3 Time Scope Time Process Groups Develop Develop Plan Execution Define Estimate Activity Fact Time Close or Work Schedule Time management includes the processes required to accomplish timely completion of the project. PMBOK Guide, Third Edition Cost Using high-precision low-accuracy information to predict dates or plan sets a project up for failure. Manage time by Plan Perform Perform forecasting instead of prediction. 25 Cost Scope Cost Process Groups Develop Develop Plan Execution Define Scope Create WBS Fact Cost Close or Work Verify Scope Scope cost management includes the processes Time involved Estimate in Activity planning, estimating, budgeting and controlling costs so that the project can be completed within the approved budget. PMBOK Guide, Third Edition We cannot maximize business or customer value without Plan Perform Perform working closely with the customer. The goal of estimating and budgeting cost management is to help the customer select the best cost/performance trade-off

4 Develop Scope Cost Process Groups Develop Close or Plan Execution Work Plan Perform Perform Fact processes include all the Time activities of the performing organization that determine quality policies, objectives, and responsibilities so that the project will satisfy the needs for which it was undertaken. PMBOK Guide, Third Edition is what the customer gets out and is willing to pay Plan Perform Perform for. Customers pay only for what is of use to them and gives them value. Nothing else constitutes quality'. Peter Drucker. 27 Scope Time Cost Process Groups Develop Develop Plan Plan Execution Work Close or Inputs Statement of Work (Light version) Contract (Agile version) Vision Statement Feature Descriptions All projects Traditional and Agile use a kick-off ceremony to describe the engagement and manage expectations. It usually Determine includes Budget reviewing the that describes Why, What, When, Where, and for Whom the project is being done. The key difference lies in the approach to the question, How will it Perform Perform be done? Agile uses iterative development to increased business involvement, team commitment, and process improvement

5 Scope Time Cost Process Groups Develop Develop Plan Inputs Execution Work Vision Statement Feature Descriptions Roadmap and Release Plans Epic-level Stories Close or The PMBOK Guide recommends Progressive Elaboration as the process to update and refine project plans which matches Agile s use of Stories to develop a Roadmap Costs that is composed of Release Plans. Release Plans are equivalent to a project management plan. Plan Perform Perform 29 Scope Process Groups Develop Develop Plan Execution Work Inputs Release Plan Epic and User Stories Close or Time Cost Plan Product Backlog (Initial) Prioritization The PMBOK Guide identifies Define Scope and many PMs interpret that as a one-time activity even though it conflicts with Progressive Elaboration. Agile embraces Progressive Elaboration by establishing a framework the Product Backlog for scope management. The Backlog is prioritized and frequently reviewed and revised to manage project scope. Given the high uncertainty about requirements and/or high Perform technological risks facing most projects it is a wise approach. Perform 30 15

6 Scope Time Process Groups Develop Develop Plan Execution Work Close or Inputs Prioritized Product Backlog Tools Prioritization techniques Sizing and Estimating techniques Iteration Planning techniques Prioritized Iteration Backlog User Stories Cost Plan Traditional project management uses a hierarchy of Program, and sub- plans to sequence work and measure progress. Agile uses a hierarchy of Roadmap, Release, and Iteration plans to do the same thing. Perform Agile project sequencing is more dynamic because of its Leandriven focus to eliminate the waste of non-value-added work. Perform 31 Scope Time Cost Process Groups Develop Develop Direct Inputs and Manage Close or Plan Execution Work Roadmap and Release Plans Product Backlog Iteration Backlog Tools Sizing and Estimating techniques Velocity Analysis Cost Baseline EVM Baseline Plan Key concept Estimates are wrong by design! Knowing this truth, Agile avoids false precision in order to eliminate waste and focuses on producing useful, reasonable cost estimates and schedules to support needed and required planning. Over time project metrics such as velocity, quality, and change Perform rates stabilize and Agile cost estimates become more reliable than traditional ones. Perform 32 16

7 Scope Time Process Groups Develop Develop Plan Execution Work Inputs Product Backlog User Stories Tools Modeling techniques Close or Models (Multiple, small, interlocking models) Agile s approach to is Organic, and Overt if needed. Cost Plan s include more frequent quality review steps because the Team includes QA. Smaller, more frequent reviews reduce waste by reducing how far off-track any work can actually go. Organic means Perform that the Customer/Proxy must be involved with defining story specifics, among other things. Overt means specific data capture and reporting can be called out if needed or required by regulators, for example. 33 Perform 34 17

8 Our seminar... YoUR Facility! In-HoUse PRoGRaMs tailored to your specific needs and programmed to move at your pace deliberate or fast and always in-depth! When you have a group of associates who can leverage a shortened learning curve to produce more value, more quickly, GR8PM comes through. You choose the topic, the dates (including weekends), and the specific content from our library of learning modules. We provide the Instructor, Student Materials, and PDUs from PMI! Join GR8PM s online family to get the most important, most up-todate information about the profession. A gift you can share and keep to help your friends and yourself save money at GR8PM.com Use this coupon code GR8PM-10 to get MINUS 10% OFF any purchase! Thank YOU for being part of the GR8PM family! Help Your PMI Chapter Excel! More PMI Chapters partner with GR8PM for PMIACP Exam Prep (and other Agile and Traditional PM training courses) than any other REP! GR8PM has enjoyed a 50% increase in the number of PMI Chapters using GR8PM in each of the last 3 years! Is it because we provide remarkable Member value, or is it because we make it super easy for (overburdened) Chapter leaders, or is it because everything we do is offered 100% Risk-free for the Chapter and produces income to the Chapter? The answer is... all of those things! Please ask your Chapter to invite us out, or better yet, provide an introduction suggesting we work together!