Your SlideShare is downloading. ×
  • Like
  • Save
Workshop the business side of agile
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Workshop the business side of agile

  • 83 views
Published

Why businesses need to be agile.

Why businesses need to be agile.

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
83
On SlideShare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
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

Transcript

  • 1. The Business Side Of Agile
  • 2. The Business Side Of Agile Increasing Speed To Market
  • 3. Large and Well Established Organizations Have More Inertia
  • 4. Even If You Are Moving Fast, Heading In The Wrong Direction Will Lead To Failure
  • 5. Negative Inertia Requires A Great Deal Of Energy, Time and Force To Redirect
  • 6. Changes In Market Require Swift Changes In Direction
  • 7. Changes In Market Require Swift Changes In Direction What Changes Are Affecting Genworth?
  • 8. Changes In Market Require Swift Changes In Direction What Is Imperative To Stay Afloat?
  • 9. Changes In Market Require Swift Changes In Direction Speed Alone Can Be Detrimental
  • 10. Changes In Market Require Swift Changes In Direction Changes In Direction Are More Difficult When Moving Fast
  • 11. Changes In Market Require Swift Changes In Direction Being Nimble Requires Focus, Constant Inspection, and Quick Adaptation
  • 12. Agility and Scrum Are About Empirical Process Control Inspection, Adaption and Transparency
  • 13. Feature Decay When Does Feature Decay Begin?
  • 14. Feature Decay When Does Feature Decay Begin?
  • 15. Feature Decay When Does Feature Decay Begin?
  • 16. Feature Decay When Does Feature Decay End?
  • 17. Feature Decay
  • 18. Feature Decay
  • 19. Feature Decay
  • 20. Managing Cost Of Delay
  • 21. Real Cost Of Delay Increases With Time
  • 22. Cost Of Delay May Eliminate ALL ROI
  • 23. Cost Of Delay May Eliminate ALL ROI Is It Really Better Late Than Never? Increased WIP Costs
  • 24. Cost Of Delay May Eliminate ALL ROI Is It Really Better Late Than Never? COD2 Increased WIP Costs + Reduced ROI COD2 =
  • 25. Scaled Agile Implements Continuous Product Development Flow
  • 26. Scaled Agile Implements Continuous Product Development Flow
  • 27. Establishing Predictable Processes
  • 28. Establishing Predictable Processes
  • 29. Sustaining Quality Cost Of Defects Increases Over Time
  • 30. Sustaining Quality 1) Validate Requirements
  • 31. Sustaining Quality1) Validate Requirements 2) Create A Design Consistent With Requirements
  • 32. Sustaining Quality1) Validate Requirements 2) Create A Design Consistent With Requirements 3) Develop A System Consistent With Design
  • 33. Sustaining Quality1) Validate Requirements 2) Create A Design Consistent With Requirements 3) Develop A System Consistent With Design Get Many People Working Independently To Do Specifically What Is Expected
  • 34. Sustaining Quality1) Validate Requirements 2) Create A Design Consistent With Requirements 3) Develop A System Consistent With Design 4) Independently Test The System And Remedy Defects
  • 35. Sustaining Quality1) Validate Requirements 2) Create A Design Consistent With Requirements 3) Develop A System Consistent With Design 4) Independently Test The System And Remedy Defects 5) Establish Operating Procedures To Ensure The System Is Used Correctly
  • 36. Sustaining Quality 6) Revise The System To Accommodate Changes In Requirements
  • 37. Sustaining Quality 7) Do All Of These Steps FAST!
  • 38. Maintaining Customer-Driven Innovation and Delivery Collaborative Ongoing Interaction With The Customer Is Necessary
  • 39. Maintaining Customer-Driven Innovation and Delivery Collaborative - Empirical Inspection Of Working Software Is The Best Means Of Knowing Progress
  • 40. Maintaining Customer-Driven Innovation and Delivery Collaborative - Empirical - Iterative Frequency Of Inspection and Adaption Ensures Ongoing Accommodation Of Change
  • 41. Maintaining Customer-Driven Innovation and Delivery Collaborative - Empirical - Iterative - Dynamic
  • 42. Maintaining Customer-Driven Innovation and Delivery Collaborative - Empirical - Iterative - Dynamic Dynamic Processes Require Effective Action and Force, Power Over Time
  • 43. Maintaining Customer-Driven Innovation and Delivery Customer Delight Is Agile’s Greatest Aim And Can Only Be Achieved And Sustained Through Ongoing Collaboration, Innovation and Adaptation With The Customer or Their Proxy.
  • 44. Maintaining Customer-Driven Innovation and Delivery Scrum Allows Cross Functional Teams To Maintain Customer Proximity Through Iterative Reviews With Subject Matter Experts and Customer Teams
  • 45. Maintaining Customer-Driven Innovation and Delivery The Scaled Agile Framework Facilitates The Alignment Of Multiple Scrum Teams Operating In Parallel And Grounds Them In Program-Level Planning And Review Done Iteratively With Customer Stakeholder Involvement