Diese Präsentation wurde erfolgreich gemeldet.
Die SlideShare-Präsentation wird heruntergeladen. ×

How a Top Retailer Brought Together UX Design and Agile Development (and got it right!)

Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
How a Top Retailer Brought
Together UX Design and Agile
Development
(and got it right!)

YouTube-Videos werden auf SlideShare nicht mehr unterstützt.

Original auf YouTube ansehen

Meet The Presenters
Bryan Lipson
EVP of Product Management, iRise
Maury Cupitt
Sr. Director of Pre-Sales, Tasktop
Doug Bro...

Hier ansehen

1 von 33 Anzeige

How a Top Retailer Brought Together UX Design and Agile Development (and got it right!)

Herunterladen, um offline zu lesen

In this slide deck from our co-hosted on-demand webinar with iRise, Doug Brown, former VP Senior User Experience Designer at JPMorgan Chase and Manager of UI Engineering for eCommerce at DSW, discusses how he’s using and integrating best of breed tools to bring together requirements, Lean UX design, and the Agile development processes.

In this slide deck from our co-hosted on-demand webinar with iRise, Doug Brown, former VP Senior User Experience Designer at JPMorgan Chase and Manager of UI Engineering for eCommerce at DSW, discusses how he’s using and integrating best of breed tools to bring together requirements, Lean UX design, and the Agile development processes.

Anzeige
Anzeige

Weitere Verwandte Inhalte

Diashows für Sie (20)

Andere mochten auch (19)

Anzeige

Ähnlich wie How a Top Retailer Brought Together UX Design and Agile Development (and got it right!) (20)

Weitere von Tasktop (20)

Anzeige

Aktuellste (20)

How a Top Retailer Brought Together UX Design and Agile Development (and got it right!)

  1. 1. How a Top Retailer Brought Together UX Design and Agile Development (and got it right!)
  2. 2. Meet The Presenters Bryan Lipson EVP of Product Management, iRise Maury Cupitt Sr. Director of Pre-Sales, Tasktop Doug Brown Former VP Senior User Experience Designer, JPMorgan Chase and Manager of UI Engineering for eCommerce, DSW
  3. 3. Done cheaper Improved Production Value We All Want… Done sooner With fewer errors Better User Experience Higher Conversions Better Documentation Less wasted work Better project visibility Fewer Roadblocks Improved Collaboration Clearer Role Responsibility
  4. 4. First Identify the Real Problem • Make sure you know what the question is before you try to implement an answer • Understanding what we’re trying to solve • Defining how the solution to our problem will be built
  5. 5. We’re Similar But Different • Real problem is bridging gaps between teams • Managing requirements • Handoff • Communicating changes • Lean and Agile are similar, but the people are different • Different personality types • Different objectives • Different ways of thinking
  6. 6. Differences In Focus Design / Business Pressures • Market windows • User triggers • Changing trends • Advertising schedules • Impromptu marketing opportunities Technology Pressures • Technology constraints • Existing work in pipeline / bandwidth • Enterprise strategies • Timelines • Cost of implementation
  7. 7. What is Design? • Researcher • Taxonomist • Consultant • Designer • Technologist • Negotiator Infographic by Jonathan Lupo Available for review online
  8. 8. What is Development? • Implementation of a specific set of requirements • Integration of technologies • Presentation of user experiences • Validation of product readiness (QA) • Numerous technologies • Back end (databases, fulfillment, etc) • Middle tier (business logic, services) • Presentation layer (user experience / data presentation)
  9. 9. Design Process Strategy Launch
  10. 10. Design Process User Evaluate Beta Production Design Analysis Research Strategy Launch Think Make Check
  11. 11. Design - Benefits • Deep understanding of user motivation / intent • Interactions matching user needs • Detailed map of user journey • Functional alignment to business objectives • Complete requirements before development
  12. 12. Traditional Design - Challenges • Little involvement from dev teams, creating unintended technical decisions • Delays dev start for considerable time
  13. 13. Lean Design - Benefits • Faster dev start • Iterative with developers • More transparent • More immediate user feedback
  14. 14. Lean Design - Challenges • Trees vs Forest • Turning requirements into work • Versioning
  15. 15. The Development Process Initiate (Requirements) Launch
  16. 16. Client Develop Integrate Test Record Changes Prioritize The Development Process Initiate (Requirements) Launch
  17. 17. Agile Development • Even Waterfall development happens iteratively • Waterfall vs Agile is really a matter of how soon results are seen outside development • Plan for execution from most important to least important • Short cycles, typically two to four weeks Agile development brings FOCUS
  18. 18. Agile Dev Process - Benefits • Tighter management of timelines and budgets • Sponsors see progress in tighter cycles and more accurate spend rates • Better information when introducing changes • Includes all disciplines (Dev, UX, QA, Business, etc.) when properly done
  19. 19. Agile Dev Process - Challenges • Requirements authority / business communication • Email • Excel • JIRA • Word Documents • Which version is current? • Translating requirements to work
  20. 20. The Problem We Want To Solve User Evaluate Beta Production Design Analysis Research Strategy Launch
  21. 21. It’s A Complicated Relationship • Design and Development have complex processes • Each impact the other • When done well allows for proper feedback throughout • User input • Technical decisions • Business value • Production readiness
  22. 22. Using Rapid Prototyping • Dovetails perfectly with Lean Design • Fast user feedback • Transparency to business stakeholders • Quick for review with developers • Allows for high-level view of forest before designing trees • Iterative, working in sections • A visual and experiential way to communicate requirements
  23. 23. Requirements – The Big Ah-Ha! • Relating requirements directly to visual artifacts • 1,000 words are mostly adjectives • Shorten time / reduce waste by thinking deeper about • Flows • Wireframes • Visuals • Functional Requirements
  24. 24. iRise for Design • High-level flow diagrams • Ability to start very low fidelity • High-fidelity interactions • Sample data capabilities • Requirements connected directly to visuals • Full collaboration
  25. 25. JIRA for Development • Manageable Agile sprints • Work estimation • Full requirement details • Process management and transition • Burn-down reporting • Code repository integration
  26. 26. User Evaluate Beta Production Design Analysis Research Process Pain Point Launch Strategy
  27. 27. Bridging the Process Gap TT-ID Title Description Acceptance Criteria Requirement iRise Link Author Last Update Comments Ready for JIRA (trigger) TT-ID Title Description Acceptance Criteria Requirement iRise Link Author Last Update Comments All custom mappings!
  28. 28. Multiple Benefits Realized • Improved traceability of requirements • Better definition of responsibilities / accountability • Developers could easily find prototype screens for reference • Easy to review decision histories • No additional work to get requirements into backlog • Rapid transition from design to development
  29. 29. Lessons Learned • Culture – Whole is greater than the sum of the parts • Any team can make or break the process, regardless of the tools used • Don’t stray from agreed processes. Work together to get past any learning curves. • Your requirements are not as good as you think they are • And they are not an element in isolation • Agile is not a magic bullet that allows for endless change • Have common understanding of “what does success
  30. 30. It’s All About Connectedness • Don’t Panic! • Remember to define your real problem • Understand your processes and identify their integration pains • Use methods like prototyping to bridge gaps • Use tools that fit your processes and can fit each other
  31. 31. Demo / Q&A

Hinweis der Redaktion

  • Call out that the pieces are the individual project teams and their outputs that combine in the process to create the final product
  • Consider the wording on these headers / better title?
  • Call out toward the design challenges that will come up later
  • Need to update to reflect more of the development space/ Call out toward the development challenges that will come up later
  • Use visuals rather than bullets for problem spaces
  • Use visuals rather than bullets for problem spaces
  • Different colors
  • Give more lead-in to the Agile process
  • Experiences are BOPIS, Readiness, Site Redesign (Search / Browse, Cart, Checkout, User Management)
  • How to tie sub-bullets in point three directly to the visual?
  • Using prototyping with requirements is a great way to help bridge the disciplines – why and how we got there
  • How prototyping can be instrumental in the process / what it brings to the table, including the expansion of requirements. Tighten up a bit.
  • Get some visuals for each bullet
  • Slide to bring it all home. Tighten up the summary.

×