Part 1: "Making Agile Work" Webinar Series: Inception

1,293 views
1,157 views

Published on

David Draper, Head of Enablement at Valtech discusses why inception is important to set up your Agile project for success.

Published in: Technology, Business
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,293
On SlideShare
0
From Embeds
0
Number of Embeds
120
Actions
Shares
0
Downloads
33
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Part 1: "Making Agile Work" Webinar Series: Inception

  1. 1. Setting an Agile Project up for Success David Draper, Head of Enablement, Valtech UK
  2. 2.  What is Inception Our Approach What do you get
  3. 3. inception takesan idea andelaborates it justenough
  4. 4. Just enough for what?Rough project “shape” Who benefits? Who is impacted?Rough costs
  5. 5. resistinganalysisparalysis
  6. 6. up-front analysis causesincreased cost and unusedfeatures
  7. 7. our fixed pricecontracts drivebehaviour throughfear of change
  8. 8. the problem with requirements … … most of them aren’t
  9. 9. Collaborative or Contractual?“Let’s figure out together thebest way to meet your goals” “Tell us precisely what you want us to build”
  10. 10. Agile requirements principles Focus on the goals of the stakeholders Bring multiple perspectives together Do not commit to details until necessary
  11. 11. What do our customers want? Reduced time-to-market Outcomes reached Revenue protection Revenue generation Cost saving Financial diligence
  12. 12. Our Approach
  13. 13. follow the value
  14. 14. incrementaldelivery
  15. 15. THE INCEPTION FRAMEWORK KICK-OFF PROBLEM ANALYSIS SOLUTION DESIGN SOLUTION DELIVERY PLANNING CONCLUSION
  16. 16. MINIMUM MARKETABLE FEATURES SYSTEM CONTEXTBUSINESS PROCESS ANALYSIS PRAGMATIC PERSONAS LIKES & DISLIKESUI DESIGN USER STORY MAPPING RELEASE THEMES STAKEHOLDER ANALYSISCRITICAL SUCCESS FACTORS VISION STATEMENTPAIN POINTS UI WIREFRAMES NON-FUNCTIONAL REQUIREMENTS TRADE-OFF SLIDERS USER STORIES MINIMUM VIABLE PRODUCT
  17. 17. VISION For (target customer) Who (statement of the need or opportunity) The (product name) is a (product category) That (key benefit, compelling reason to buy) Unlike (primary competitive alternative) Our product (statement of primary differentiation) taken from Geoffrey Moore’s book Crossing the Chasm
  18. 18. PersonasMarket segmentation for dummies
  19. 19. MMFS MINIMUM How small can a product be and still deliver benefit to someone? Benefit can be in the form of new information, a marketing demo or a new feature for end users MARKETABLE Each increment should deliver recognisable value FEATURES Some features cannot stand alone Others can be split
  20. 20. VISION CRITICAL SUCCESS FACTORS STAKEHOLDERS / ACTORS CANDIDATE ARCHITECTURE / UI WIRE FRAMES MMF 1 MMF 2 MMF 3 HIGH LEVELELABORATED STORIES STORIES
  21. 21. What do you get?
  22. 22. Deliverables for you Shared vision Persona & stakeholder analysis Roadmap Release strategy Product backlog Technical architecture UX / UI mock-ups
  23. 23. … and the option to have Valtech deliver it Resource profile Delivery approach Adrid Assumptions, decisions, risks, issues, dependencies Engagement model Indicative pricing by stage
  24. 24. At what cost 2-3 weeks Multi-skilled team Engagement manager Busness analyst Technical architect User experience consultant
  25. 25. Thank you

×