Your SlideShare is downloading. ×
Valtech - Agile inception : how to start an agile project ?
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Valtech - Agile inception : how to start an agile project ?

1,237
views

Published on

Agile inception : how to start an agile project ? …

Agile inception : how to start an agile project ?

David Draper, Agile Coach, Valtech UK
David.Draper@valtech.co.uk

Agile Day 2012
Valtech

Published in: Technology, Business

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,237
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
56
Comments
0
Likes
2
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. OBJECTIVES!By attending this Webinar you will learn:•  Why do we need Inception for Agile projects?•  How to understand stakeholder and user needs•  How to work breadth first•  How to satisfy your organisations needs for budget andscope certainty without sacrificing Agility
  • 2. SETTING AN AGILE PROJECT UP FOR SUCCESS! DAVID DRAPER // HEAD OF ENABLEMENT // VALTECH UK
  • 3. How do you embark on a newproject?
  • 4. Ò  WHAT IS INCEPTION?Ò  OUR APPROACHÒ  TOOLBOXÒ  OUTPUTS
  • 5. INCEPTION TAKESAN IDEA ANDELABORATES ITJUST ENOUGH!
  • 6. JUST ENOUGH FOR WHAT?!Ò Rough project “shape” Who benefits? Who is impacted?Ò Rough costs
  • 7. RESISTINGANALYSISPARALYSIS!
  • 8. UP-FRONT ANALYSIS CAUSESINCREASED COST ANDUNUSED FEATURES
  • 9. FIXED PRICECONTRACTS DRIVEBEHAVIOURTHROUGH FEAR OFCHANGE!
  • 10. COLLABORATIVE OR CONTRACTUAL?!“LET’S FIGURE OUT TOGETHER THEBEST WAY TO MEET YOUR GOALS” “TELL US PRECISELY WHAT YOU WANT US TO BUILD”
  • 11. THE PROBLEM WITH REQUIREMENTS …
 
 … MOST OF THEM AREN’T!
  • 12. AGILE REQUIREMENTS PRINCIPLES!Ò  FOCUS ON THE GOALS OF THE STAKEHOLDERSÒ  BRING MULTIPLE PERSPECTIVES TOGETHERÒ  DO NOT COMMIT TO DETAILS UNTIL NECESSARY
  • 13. WHAT DO OUR CUSTOMERS WANT?!Ò REDUCED TIME-TO-MARKETÒ OUTCOMES REACHED REVENUE PROTECTION REVENUE GENERATION COST SAVINGÒ FINANCIAL DILIGENCE
  • 14. OUR APPROACH
  • 15. FOLLOW THE VALUE!
  • 16. INCREMENTALDELIVERY!
  • 17. EVERY PROJECT IS DIFFERENT!Ò UsabilityÒ Technology Up-liftÒ Social platformÒ CommerceÒ Integration 17
  • 18. THE INCEPTION FRAMEWORK! KICK-OFF PROBLEM ANALYSIS SOLUTION DESIGN SOLUTION DELIVERY PLANNING CONCLUSION
  • 19. 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
  • 20. TOOLBOX
  • 21. 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 primarydifferentiation) taken from Geoffrey Moore’s book Crossing the Chasm
  • 22. STAKEHOLDERS!Ò  Who cares?Ò  Permission giverÒ  Interested partyÒ  Information sourceÒ  What makes them tick? 23
  • 23. PERSONAS!Ò  MARKET SEGMENTATION FOR DUMMIES
  • 24. 25!
  • 25. 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
  • 26. WIREFRAMES! Ò  Engage stakeholders with interactive mock ups Ò  Long term and short term view
  • 27. VISION CRITICAL SUCCESS FACTORS STAKEHOLDERS / ACTORS CANDIDATE ARCHITECTURE / UI WIRE FRAMES MMF 1 MMF 2 MMF 3 HIGH LEVELELABORATED STORIES STORIES
  • 28. WHAT DO YOU GET?
  • 29. OUTPUTS!Ò SHARED VISIONÒ ENGAGED STAKEHOLDERSÒ PERSONA ANALYSISÒ ROADMAP & RELEASE STRATEGYÒ PRODUCT BACKLOGÒ TECHNICAL ARCHITECTUREÒ UX / UI MOCK-UPS
  • 30. … AND THE OPTION TO HAVE VALTECH DELIVER IT!Ò  RESOURCE PROFILEÒ  DELIVERY APPROACHÒ  ADRID Assumptions, decisions, risks, issues, dependenciesÒ  ENGAGEMENT MODELÒ  INDICATIVE PRICING BY STAGE
  • 31. AT WHAT COST!Ò  2-3 WEEKSÒ  MULTI-SKILLED TEAM ENGAGEMENT MANAGER BUSNESS ANALYST TECHNICAL ARCHITECT USER EXPERIENCE CONSULTANT
  • 32. Thank you

×