An introduction to UX in Scrum

23,334 views

Published on

Published in: Design, Technology
2 Comments
90 Likes
Statistics
Notes
No Downloads
Views
Total views
23,334
On SlideShare
0
From Embeds
0
Number of Embeds
566
Actions
Shares
0
Downloads
692
Comments
2
Likes
90
Embeds 0
No embeds

No notes for slide

An introduction to UX in Scrum

  1. Scrum and UX Presented by Morten Just April 2009 1 Presentation title in footer Scrum and UX April 01, 2009
  2. IA Visual designer • Wireframes • Visual style guide • flow diagrams • Visual design • brief specs • Choreography 2 Scrum and UX
  3. Product owner Tester • Backlog • Test cases • Priorities • Issue reports • Business insight • Vision Scrum master • Planning • Coaching • Resources • Tasking Scrum and UX 3
  4. Developer • Design • Strategy • Usability • IA • Interaction design • Planning • Feasibility studies • Code 4 Scrum and UX
  5. All Rule Scrum and UX
  6. All, 10 Visual, 3 months years IA, 2 months IA/Visual, 8 months IA/product product owner, owner, 8 months 3 months Scrum and UX
  7. 7 Scrum and UX
  8. How we do UX in Scrum 8 Scrum and UX
  9. How we do ams me te So UX in Scrum 8 Scrum and UX
  10. Business conducts user research and defines a set of high-level features Parking meter D park etect Pay with ed c coins ar Pay by phone Ch oose period ry Show histo Send SMS Choose warnings language 9 Scrum and UX
  11. The product owner collects features in a backlog (in Mingle) - and prioritise them Choose period Can’t launch without it Pay with coins Get ticket Product backlog Choose Would make a better parking meter language Pay by phone Send SMS warnings Would delight users Detect parked ca r ry Show histo 10 Scrum and UX
  12. If necessary he writes detailed stories for each feature Choose period As a user I want the As a user I want to be As a user I want a As a user I want to clear system to suggest a able to pick a predefined different period in the selected period so I reasonable period for me weekends and evenings period so I don’t have to won’t be stuck with an so I don’t have to press press buttons too much so I dont have to press error buttons too much and and reduce errors buttons too much reduce errors 11 Scrum and UX
  13. 12 Scrum and UX
  14. Sprint zero begins Scrum and UX
  15. Always at least a sprint ahead As a user I want to As a user I want to create an account log in As a user I want to As a user I want to create an account log in Sprint 0 Sprint 1 Sprint 2 1 Presentation title in footer Scrum and UX April 01, 2009
  16. The product owner, IAs and designers discuss the overall user experience Choo se period Pay with Business blah coins Simplicity, Branding objectives, blah- blah usability, blah, visual blah strategy, overall Get ticket identity blahmarketing experience Choose language Pay by phone Send SMS warnings Detect parked ca r ry Show histo 15 Scrum and UX
  17. They ask developers about feasibility and tradeoffs Choo peri How big a Pay w job is it to make coi it glow in the Can we dark? make it talk? Get ti Massive, Not with but we can Choo genuine speech make it light synthesis, but if langu enough so that it samples can do, appears to be no problem glowing Pay pho Send S warnin Detec parked c Show h Scrum and UX 16
  18. 2 days 4 hours 17 Scrum and UX
  19. 1,5 days 18 Scrum and UX
  20. 2 hours 19 Scrum and UX
  21. The IA creates a wiki page Pay wit coins Choose period Get tick Choose Background languag Parking is boring. If we can’t get rid of it, one of our strongest design drivers should be making it quick and easy. Pay by phone Send SM warnings Detect parked ca r 20 Show histo Scrum and UX
  22. The visual designer applies his work to the wiki page Pay wit coins Choose Get tick period Choose Background languag Parking is boring. If we can’t get rid of it, one of our strongest design drivers should be Pay by making it quick and easy. phone Send SM warnings Detect parked ca r Show histo 20ms Scrum and UX 21
  23. The tester adds test cases Pay wit coins Choose Get tick period Choose Background languag Parking is boring. If we can’t get rid of it, one of our strongest design drivers should be Pay by making it quick and easy. phone Send SM warnings Detect parked ca r Show histo 20ms Check that the Scrum and UX ticket is written 22 Check that the
  24. 23 Scrum and UX
  25. Sprint 1 begins Scrum and UX
  26. Sprint planning Pay with ? coins ? et ticket Choose language Pay by phone Send SMS etect arked Show history Beginning from the top of the backlog, the product ...developers listen owner presents the and ask questions stories one by one 25 Scrum and UX
  27. Planning poker Pay with coins 5 7 5 1 et ticket days 37 Choose days days days language days 1 days Pay by phone days Send SMS etect arked Show history Secretly, they ... reveal it, all at ... and discuss choose an estimate the same time 26 Scrum and UX
  28. Scrum master Pay with coins The scrum master et ticket notes all estimates Choose language and lets the team Enough is Pay by know when the phone enough. sprint is fully loaded Send SMS etect arked Show history 27 Scrum and UX
  29. 28 Scrum and UX
  30. The product owner now knows the estimates... Choose 5 days period Can’t launch without it Pay with 2 days coins Get ticket 1 days Product backlog Would make a Choose better parking 3 days language meter Pay by phone 6 days Send SMS 7 days warnings Would delight users Detect 70 days parked ca r ry Show histo 3 days 29 Scrum and UX
  31. ... and what goes into the first sprint Sprint 1 backlog Choose 5 days period Can’t launch without it Pay with 2 days coins Get ticket 1 days Product backlog Would make a Choose better parking 3 days language meter Pay by phone 6 days Send SMS 7 days warnings Would delight users Detect 70 days parked ca r ry Show histo 3 days 30 Scrum and UX
  32. The developer looks at the wiki page .. and talks to the IA about ... and to the visual designer details and edge cases about which assets are needed, fonts and colors Scrum and UX
  33. Everyone is engaged in conversations every day A A A? 32 Scrum and UX
  34. During the sprint Removes obstacles Works on upcoming sprint Protects the team from Supports developers with the business assets and guiding Monitors the team’s velocity and progress Guides team in the business’ Works on upcoming sprint priorities and strategy Guides developers in edge Decides on workarounds, reduced cases, clarifies wireframes and scope and reshuffling of sprint flow diagrams items Writes new code Improves old code Scrum and UX
  35. 10 Daily stand-ups are a great chance for the UX min team to find out what’s being worked on A A F A D 34 Scrum and UX
  36. During the sprint, visual designers have feedback to what’s being coded Scrum and UX
  37. Let’s be honest... 90% of all design feedback is CRAP 36 Scrum and UX
  38. C Contrast Text that can’t be read RRepetition Inconsistent form fields AAlignment Form fields don’t align with the headline PProximity Form labels too far away from their elements Scrum and UX
  39. The visual design feedback is aggregated on the wall behind the product owner g left change left 6px paddin font should be arial 6px padding left Developers pick tasks if they have change left time to spare 6px padding left font should be change left arial 6px padding left 6px padding left ld be t shou fon arial 38 Scrum and UX
  40. 39 Scrum and UX
  41. Tasks still open at the end of a sprint are prioritised, bundled up and put into the backlog 6px padding Sprint 1 backlog 6px Choose padding 5 days period Can’t launch without it Pay with 2 days coins change left font should 6px Get ticket 1 days Sprint 2 backlog be arial padding Would make a Choose 3 days better parking language meter change left font should Design 6px be arial padding bundle 3 Design 6px padding bundle 1 ould change left font sh al 19 40 i be ar Design bundle 2 Scrum and UX
  42. Demo at the end of the sprint Choose backlog Sprint 1 period Pay with coins Get ticket Choose language Po Pay by sh ten phone ip tia pa ll bl y e The team shows the stakeholders what they’ve completed during the sprint Scrum and UX
  43. Reality tends to not stick to the plan Things are left out The developer Sometimes, the IA The developer discusses this with forgets an comes up with a the IA and the important part of a new estimate product owner and feature the scrum master The product owner The developer updates the goes back to work backlog and revisit his priorities Scrum and UX
  44. Reality tends to not stick to the plan Visual design was not delivered The visual designer ... and informs his The developer forgot or is too decisions to the finds similar busy to design a product owner and elements in the certain feature the visual designer design Scrum and UX
  45. Reality tends to not stick to the plan A stakeholder is unavailable The product owner The developer is takes a decision blocked because a He informs his and informs the stakeholder is not scrum master stakeholder of that available for a decision clarification The stakeholder may not agree with the decision and the product owner may need to create new stories in the backlog Scrum and UX
  46. When in a sprint, the team cannot be stopped Scrum and UX Before the sprint started everyone said they were ready, so the team will wait for no one
  47. Thank you 46 Scrum and UX

×