• Like
Traditional to Agile conceptual
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Traditional to Agile conceptual

  • 458 views
Published

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

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

Published in Business , Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
458
On SlideShare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
2
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Burndown, Burn Up, Velocity, Health, and Status

Transcript

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