Traditional to Agile conceptual


Published on

A presentation for initial questions to ask when considering rapid release deployment and PDCA methods of delivery

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Burndown, Burn Up, Velocity, Health, and Status
  • Traditional to Agile conceptual

    1. 1. AGILE ADOPTION<br />Guiding Your Agile Journey<br />
    2. 2. Our Position<br />Industry Leadership, Unified Philosophy, One Brand<br />© 2011 Bevill Edge® <br />3<br />
    3. 3. Build the Pilot Team<br />Who are they?<br />Cross-Functional<br />Self-Organized<br />Persistent<br />Co-located<br />Committed to the Success<br />What do they need?<br />Dedicated Team Room<br />Flip Charts<br />Persistent Task Boards<br />Post-It Notes<br />Markers<br />Pens<br />© 2011 Bevill Edge® <br />4<br />
    4. 4. Scrum or not to scrum<br />Roles, Ceremonies, Artifacts<br />© 2011 Bevill Edge® <br />5<br />
    5. 5. Release planning<br />Vision, Requirements, Prioritization, & Planning<br />© 2011 Bevill Edge® <br />6<br />
    6. 6. Release Planning<br />Questions<br />Who does product visioning today?<br />How often do you meet now?<br />How do you get feedback from the customer today?<br />What documents to do you deliver to the stakeholders today?<br />Tomorrow<br />Visual Collaboration<br />Stakeholder Engagement<br />Epic Story Documentation<br />Continual Improvement<br />Documents<br />Velocity<br />Release Plan<br />Release Burndown<br />© 2011 Bevill Edge® <br />7<br />
    7. 7. Release Planning<br />What’ll Change<br />Expectations<br />Durations<br />Affinity Groups<br />Feature Documentation<br />Value Driven Development<br />Prioritization Techniques<br />Planned Projects<br />Personal Goals for Change<br />© 2011 Bevill Edge® <br />8<br />
    8. 8. Sprint planning<br />Planning, Scheduling, Estimating, Dependencies, Conflict Management<br />© 2011 Bevill Edge® <br />9<br />
    9. 9. Sprint Planning<br />Questions<br />How do you track project progress today?<br />How do you provide status updates to the business?<br />How do you manage dependencies?<br />How do you measure duration?<br />How do you sequence activities today?<br />Tomorrow<br />Pulled work by the team<br />Value/Customer based prioritization<br />Daily Standups (water cooler conversations)<br />Frequent Feedback through Intentional Interaction<br />Osmotic Planning<br />© 2011 Bevill Edge® <br />10<br />
    10. 10. Sprint Planning<br />What’ll Change<br />Documentation provided to business partners and stakeholders<br />Timelines will become incremental<br />Delivery will become incremental & value based<br />Self organization will emerge in the team<br />Managers own the end, not the means<br />Personal Goals for Change<br />© 2011 Bevill Edge® <br />11<br />
    11. 11. monitoring<br />Earned Value, Status Reports, Dashboards, Schedule Updates<br />© 2011 Bevill Edge® <br />12<br />
    12. 12. Monitoring<br />Questions<br />How do you track project progress today?<br />Do you track earned value metrics?<br />What metrics track project health today?<br />How do you provide status to the business partner today?<br />Tomorrow<br />Velocity Metrics<br />Complexity Burn Rate Charts<br />Expected Path Analysis<br />© 2011 Bevill Edge® <br />13<br />
    13. 13. Monitoring<br />What’ll Change<br />Earned Value Reports will be replaced with Earned Value<br />Performance thresholds and metrics will be created as a byproduct of work<br />Information Radiators makes metrics visible<br />Charts result in visual indicators of performance<br />Personal Goals for Change<br />© 2011 Bevill Edge® <br />14<br />
    14. 14. testing<br />Acceptance Criteria, Automated Unit Testing, Quality <br />© 2011 Bevill Edge® <br />15<br />
    15. 15. Testing<br />Questions<br />What tests structures are in place today?<br />Who are your testers?<br />How often do you test?<br />How do you maintain quality assurance today?<br />What is the procedure for documenting tests and quality today?<br />Tomorrow<br />Acceptance Criteria and Testing<br />Automation<br />Test Driven Development<br />MMF Planning & Delivery<br />Fail Fast, Refactor, Deliver<br />© 2011 Bevill Edge® <br />16<br />
    16. 16. Testing<br />What’ll Change<br />Unit Tests are automated, always on<br />Systems Testing is automated<br />Time Boxes allow for early fails and big wins<br />Shippable Features will be tested in increments and accepted to production per a release schedule<br />Personal Goals for Change<br />© 2011 Bevill Edge® <br />17<br />
    17. 17. retrospectives<br />Lessons Learned, Historical Actuals<br />© 2011 Bevill Edge® <br />18<br />
    18. 18. Retrospectives<br />Questions<br />Do lessons learned get used on project planning?<br />Are historical actuals and previous schedules used to start new projects?<br />How are processes improved upon?<br />Who has the authority to approve a process change?<br />Tomorrow<br />Teams will self-organize to ensure conflicts are escalated immediately<br />Teams will work as groups using visual techniques to provide clear actionable feedback to the product ownership<br />Stakeholder feedback will become part of the iteration<br />© 2011 Bevill Edge® <br />19<br />
    19. 19. Retrospectives<br />What’ll Change<br />Issues and Risks will be handled immediately by the entire team until resolved<br />Communications will allow for frequent feedback and prevent unknown issues from emerging<br />Personal Goals for Change<br />© 2011 Bevill Edge® <br />20<br />
    20. 20. Product demo<br />Delivery, Functional Increments, Stakeholder Engagement<br />© 2011 Bevill Edge® <br />21<br />