Your SlideShare is downloading. ×
0
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
Agile's Secret Step: Discovery
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

Agile's Secret Step: Discovery

8,094

Published on

Lightening talk presentation given at MidwestUX on April 11, 2011 and Big Redux DC April 30, 2011

Lightening talk presentation given at MidwestUX on April 11, 2011 and Big Redux DC April 30, 2011

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

No Downloads
Views
Total Views
8,094
On Slideshare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
85
Comments
0
Likes
13
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
  • \n
  • There are really 2 secret steps to Agile. Discovery and Planning. They go hand and hand.\n
  • When I say Agile I mean a project execution methodology that is in opposition to something like waterfall.\n
  • Waterfall we had a phase we knew where we “fit”\n
  • But where do we fit in in Agile??\n
  • \n
  • \n
  • I learned Agile in a large corporation.... nickname the Titanic\n
  • By decreasing risk to the code and releases the IT team on the “Titanic” promised to increase speed and efficiency\n
  • Nobody could say where UX fit into Agile\n
  • Currently it’s all about increasing speed and getting to market faster.\n
  • What everyone forgets is that agile was created as a development methodology.\n
  • but what are we building? What is the product? Who are the users? What is the context of use?\n
  • On the flip side, companies think that “agile” is their golden goose, promising them lower overhead and more speed. They still don’t know where we fit in or what we do.\n
  • Two main problems.\n1. UX/Design slows agile down. That is because we have no idea who are users are, what the context is for our designs and what content goes into things. Not having this background causes the “churn” discussions.\n2. IT release bugs/errors because they don’t have complete use cases. Thus spending the next several iterations fixing problems instead of extending the product.\n
  • We blame the methodology, but it’s not Agile’s fault we are implementing it incorrectly.\n
  • Let’s start by looking at what makes agile successful then add in the UX pieces.\n
  • Have a beer backlog and knowing the order that the backlog is being bottled allows this bottling assembly line to move fast. Think of agile like an assembly line. When we do that we realize we need to have a feature backlog that is prioritized.\n
  • Discovery gives us our feature backlog.\n
  • Planning with our biz and tech partners gets us the prioritized backlog.\n
  • The outcome of having this 2 things gets all of us on the same page as to what is being created, why, and in what order. \n
  • Skillset wise we end up with a strategy group that is constantly researching and prioritizing outside of agile. They are determining what features should be built next and queueing them up for the project teams.\n
  • At the same time the project teams are doing their own research and design on a specific set of features. They should be providing feedback to the strategy team and vice versa. This is NOT modified waterfall process, but instead these teams work in tandem. \n
  • The project is what Agile was created to speed up. By taking all the churn causing decisions and discussion out of the project we are able to increase speed. \n
  • These are the places where UX fits in. Keep in mind there are awesome design problems to solve within the project, but having a focused set of features gives us our design constraints to design within.\n
  • Thus our product consists of an overall strategy that is being built by 1 - many projects.\n
  • Remember Agile is like an assembly line. We need a prioritized backlog to keep the line moving.\n
  • Discovery gets us our back log\n
  • Planning with our Biz & Tech teams prioritizes this backlog\n
  • Thus we get increased speed by removing churn and focusing design and development. Decrease user risk by not developing features the user doesn’t want and decreased tech risk\n
  • \n
  • \n
  • Transcript

    • 1. April 11, 2011Agile’s Secret Step: Discovery MidwestUX
    • 2. April 11, 2011 Agile’s Secret StepsDiscovery & Planning MidwestUX
    • 3. Waterfall Agile • Distinct project “phases” • Overlapping phases • Handoffs • IterationsLis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 4. Waterfall Agile Requirements Design Development UXLis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 5. Waterfall Agile Requirements ? Design Development UXLis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 6. Lis Hubert UX Consultant @lishubert www.elisabethhubert.comLis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 7. So What?Lis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 8. Lis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 9. Lis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 10. Lis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 11. Lis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 12. Agile is a DEVELOPMENT methodology...Lis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 13. Agile is a DEVELOPMENT methodology... but WHAT are we developing?Lis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 14. Lis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 15. Lis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 16. Agile... is NOT the enemyLis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 17. How do we get here? Agile UXLis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 18. Lis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 19. Discovery = the “What” • User Research • Business Research • Competitive AnalysisLis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 20. Product Roadmap • The “What” prioritizedLis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 21. Same Page Business Technology/IT User ExperienceLis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 22. “Hey guys here is what to build next.” StrategyLis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 23. “Hey guys here is “Roger that. Oh what to build and by the way...” next.” Strategy ProjectLis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 24. Agile Strategy ProjectLis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 25. Agile Strategy Project UX UXLis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 26. Product Strategy Project x nLis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 27. Review ProjectLis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 28. ReviewLis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 29. ReviewLis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 30. Review What do we get? • Increased Speed • Decreased User Risk • Decreased Technical RiskLis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 31. Discovery & Planning... Just Do ItLis Hubert Agile’s Secret Step: Discovery April 10, 2011
    • 32. Thanks! @lishubert www.elisabethhubert.comLis Hubert Agile’s Secret Step: Discovery April 10, 2011

    ×