1 / 31

Deciding “What” to Build

Deciding “What” to Build. The Agile Enterprise Strategically Aligned, Throughput Focused, Human Powered. “Dennis Stevens helped us develop a structured approach that connected customer value to execution. He helped us deliver over $200 million in value to our customers.”

stella
Download Presentation

Deciding “What” to Build

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Deciding “What” to Build

  2. The Agile EnterpriseStrategically Aligned, Throughput Focused, Human Powered “Dennis Stevens helped us develop a structured approach that connected customer value to execution. He helped us deliver over $200 million in value to our customers.” -- Ric Merrifield, Microsoft Corporation • PMI Agile LIG • PMI Agile CoP • New PMI Agile offering Feb 24 “Dennis Stevens helped us align business analysis, architecture, development, QA, support and implementation. He was an advocate for the success of our business" -- Rob Andes, CTO, John Deere Connecting the Strategy and ExecutionHBR: The Next Revolution in Productivity Agile in the Enterprise Core Team Member “In a time growth and change, Dennis Stevens helped us identify and develop the capabilities needed to deliver technology that was critical to our success."  -- Mike Rouse, COO, Security First Network Bank Exploiting Agile Development Cutter: Rethinking the Agile Enterprise Agile Business Analysis Agile Extension to the BABOK

  3. Do you see it?

  4. Now you see it!

  5. The “How” TrapA human condition • The Fosbury Flop • Sending a fax isn’t ever “what” someone is doing

  6. With a How FocusEffort Expands Faster then Value #1. Undifferentiated Scope #2. Over analyze and over design #3. Delivery is over engineered

  7. #1 Undifferentiated Scope

  8. Increase or protect revenue, decrease or prevent costs, increase service, maintain compliance or prepare for the future in alignment with the business strategy What is Business Value?

  9. Business Value Goal Model Example Tire Manufacturer Survive by re-establishing credibility Business Value Goal Fix the tires Improve PR Repair distributor relationships Address morale Settle lawsuits Focusing Objectives Revenue Expenses Production levels Market share Customer Satisfaction Standard Objectives

  10. What the customer perceives as important and is willing to pay for. What is Customer Value?

  11. high Starbucks Emphasis low quality speed convenience fashion selection ambiance price location serviceexpertise factors of customer experience Customer Value Map Example Explicit performance gap We are here

  12. Describe the product as a set of outcomes – or capabilities. Jump Over Bar Notify Customer Verb - Noun

  13. Explicit Performance Gaps Business Value Customer Value AnotherOutcome Risk Risk Business Risk Technology Risk Organizational Risk Market Risk KEY Low Performing Medium Performing High Performing High Value Medium Value Low Value High Risk Moderate Risk Low Risk

  14. Have a road map

  15. Specific Initiative To Achieve a Specific Outcome At the end of the effort – that outcome should be recognizable AnotherOutcome KEY High Value Medium Value Low Value Low Performing Medium Performing High Performing High Risk Moderate Risk Low Risk

  16. When the performance goal is achieved We don’t need to invest here anymore AnotherOutcome KEY High Value Medium Value Low Value Low Performing Medium Performing High Performing High Risk Moderate Risk Low Risk

  17. Revisit the road map frequently • If the outcome isn’t realized – either your understanding of the model is wrong – or you didn’t do a good job with the initiative • When lost it the forest, if the map doesn’t agree with the terrain, in all cases believe the terrain

  18. #1 Undifferentiated Scope Tips • Articulate business value • Articulate customer value • Make value explicit • Have a road map • Revisit the road map frequently

  19. #2 Over Analyze and Over Design

  20. Start with the simplest thing that might possibly work

  21. Reduce risk early – focus on next highest increment of value Trim the tail 2,500 Knowledge Growing (risk reduction) Value 2,000 1,500 $ in k 1,000 500 Value Cost

  22. Reduce risk early – focus on next highest increment of value Discovery • An increment whose purpose is to prove a technology or gather feedback. May be a technology proof or a prototype. • Prove it before investing more then needed

  23. Reduce risk early – focus on next highest increment of value Goat Path • A story that defines the absolute minimum required to walk a happy path of an activity from one end to the other. Can include supporting technical stories. When we need rapid feedback to address business risk

  24. Reduce risk early – focus on next highest increment of value Gravel Road • A story that is robust enough to cover multiple options and paths but whose implementation can be broken by extraordinary uses. Paved Road • A story that is solid and can withstand high capacity and resilient to frequent use. Super Highway • A story with lots of bells and whistles that is tightly integrated into other uses, intuitive and robustly functional. Allows trimming the tail Do we always need the Super Highway?

  25. #2 Over analyze and over design Tips • Start with the simplest thing that might possibly work • Reduce risk early with as little investment as possible • Be focused on a small specific objectives

  26. Over Engineered

  27. #3 Over Engineered • Until something is delivered it is all untested assumptions • Strategic decisions become concrete at the implementation level – make sure delivery is focused on value

  28. #3 Over Engineered • The runway is more important than the road map • Make sure the right context (architecture, value, schedule, costs) exists for delivery • Make work ready so the next most important thing can be worked on

  29. #3. Solutions are over engineered Tips • Establish context and deliver early and frequently • Make work ready so the next most important thing can be worked on

  30. Tips #1. Undifferentiated Scope • Articulate business value • Articulate customer value • Make value explicit • Have a road-map and test your assumptions #2. Over analyze and over design • Start with the simplest thing that might possibly work • Reduce risk early with as little investment as possible • Be focused on a small specific objectives #3. Solutions are over engineered • Establish context and deliver early and frequently • Make work ready so the next most important thing can be worked on

  31. Questions Dennis Stevens President, Synaptus Enabling the Agile Enterprise @dennisstevens www.synaptus.com www.dennisstevens.com

More Related