Scrum and User Experience Design: Bringing Great Design into the Agile Process<br />Patrick Neeman, Usability Counts<br />...
Scrum<br />A process for managing complex projects.<br />Stay small: Focus on smaller, measurable increments<br />Staying ...
Scrum…<br />Works Well<br />Existing products<br />Smaller teams<br />Projects with no existing methodology<br />Projects ...
Scrum Sprint Process<br />Daily: Talk about yesterday, today, tomorrow(15 minutes)<br />Take longer conversations offline<...
Product Owner<br />Defines the features of the product<br />Agency: Client is Product Owner<br />Company: Product Manager/...
Scrum Master<br />Ensures that the team is fully functional, productive and improves quality<br />Enables close cooperatio...
Roles and Responsibilities<br />Team<br />Cross-functional, seven plus/minus two members<br />Example: 1 UX Designer, 3 De...
Definition of Done<br /><ul><li>Team together with product owner defines what “done” means.
Done defines the current technical capability of the team.
Typically, Done should include everything needed before deployment.
Done may be a stub page or a process that requires human intervention.
Not done backlog items should be pushed to the next Sprint.</li></li></ul><li>How to measure Done<br />Development team mu...
Documentation Plan<br />Just enough – it’s what you have to say and what you don’t have to say<br />Overall style guide<br...
Corporate Espionage Sprint Plan<br />Where User Experience / QA fits in<br />Work one sprint ahead<br />Wireframes<br />Te...
Product Backlog<br />User Research – Sprint 1 UX<br />Scoring Architecture – Sprint 2<br />Claim Card – Sprint 2 UX<br />P...
Example Product Development<br />Team agreed to…<br />Two week sprints<br />Daily 15 minute meetings<br />Retrospective, n...
Example Product Development<br />
Sprint Backlog 1<br />Developers<br />Set up development environment<br />Set up testing environment<br />User Experience ...
Sprint Backlog 2<br />Developers<br />Scoring Architecture<br />Build Of Pages/Stubs<br />Claim Card<br />User Experience ...
Sprint Backlog 3<br />Developers<br />Create Pages/Stubs<br />Play Card<br />User Experience / QA<br />Pick Card<br />Scor...
Upcoming SlideShare
Loading in …5
×

Agile and UX, July 8 - Scrum Club, Los Angeles, CA

2,395 views

Published on

A presentation that breaks down User Experience within Agile and Scrum Methodologies

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

No Downloads
Views
Total views
2,395
On SlideShare
0
From Embeds
0
Number of Embeds
204
Actions
Shares
0
Downloads
53
Comments
0
Likes
6
Embeds 0
No embeds

No notes for slide

Agile and UX, July 8 - Scrum Club, Los Angeles, CA

  1. 1. Scrum and User Experience Design: Bringing Great Design into the Agile Process<br />Patrick Neeman, Usability Counts<br />Mike Vincent, MVA Software<br />
  2. 2. Scrum<br />A process for managing complex projects.<br />Stay small: Focus on smaller, measurable increments<br />Staying in communication: Short meetings to encourage more short meetings between fewer team members<br />Stay transparent:Inspection is dependent on transparency.<br />
  3. 3. Scrum…<br />Works Well<br />Existing products<br />Smaller teams<br />Projects with no existing methodology<br />Projects with existing technology but a failed approach<br />Dedicated teams<br />Jack of all trade team members<br />Doesn’t Work So Well<br />Undefined, new products<br />Larger teams and projects<br />Teams with members on several projects<br />Without a strong team in place<br />Specialists<br />
  4. 4. Scrum Sprint Process<br />Daily: Talk about yesterday, today, tomorrow(15 minutes)<br />Take longer conversations offline<br />Retrospective: Change the process to make it better(1 hour)<br />Don’t change Product Backlog (list of features) once sprint has started<br />Week 1<br />Week 2<br />Daily Meeting<br />Daily Meeting<br />Daily Meeting<br />Daily Meeting<br />Daily Meeting<br />Daily Meeting<br />Daily Meeting<br />Daily Meeting<br />Daily Meeting<br />Daily Meeting<br />Retrospective Meeting<br />Sprint 1<br />Sprint 2<br />Sprint 3<br />Sprint 4<br />Sprint 5<br />
  5. 5. Product Owner<br />Defines the features of the product<br />Agency: Client is Product Owner<br />Company: Product Manager/UX Lead is Product Owner<br />Manages project features and releases to optimize return on investment (ROI)<br />Inspects increment and makes adaptations to project after end of sprints<br />Can change features and priority every X days, but not in the middle of a Sprint<br />
  6. 6. Scrum Master<br />Ensures that the team is fully functional, productive and improves quality<br />Enables close cooperation across all roles and functions and removes barriers<br />Shields the team from external interferences<br />Ensures that the process is followed<br />Teaches Product Owner and Team how to fulfill their roles<br />Not a dedicated role, but it’s nice if this it the UX team member<br />
  7. 7. Roles and Responsibilities<br />Team<br />Cross-functional, seven plus/minus two members<br />Example: 1 UX Designer, 3 Developers, 2 QA <br />Self organizing<br />Manages itself, its work and its process<br />Commits to what it feels it can accomplish<br />Limit team to 45 hour work weeks for measurable results<br />Collaborates with Product Owner to optimize value<br />Demos work results to the Product Owner as much as possible<br />Hallway usability testing<br />
  8. 8. Definition of Done<br /><ul><li>Team together with product owner defines what “done” means.
  9. 9. Done defines the current technical capability of the team.
  10. 10. Typically, Done should include everything needed before deployment.
  11. 11. Done may be a stub page or a process that requires human intervention.
  12. 12. Not done backlog items should be pushed to the next Sprint.</li></li></ul><li>How to measure Done<br />Development team must be able to produce a completely “done” piece every Sprint<br />Product Owner must inspect and adapt to optimize ROI every Sprint<br />“Undone” work must be identified<br />WaterfallDone at end of project<br />Development Process<br />Done<br />Agile/ScrumDone at end every iteration<br />Done<br />Done<br />Done<br />Done<br />Done<br />
  13. 13. Documentation Plan<br />Just enough – it’s what you have to say and what you don’t have to say<br />Overall style guide<br />High level use cases / user stories<br />Light wireframes, 3 by 5 cards, hand written notes<br />Don’t update what you don’t need<br />Detailed test plans (definition of done)<br />Pass / Fail<br />The only deliverable that counts is the final product<br />
  14. 14. Corporate Espionage Sprint Plan<br />Where User Experience / QA fits in<br />Work one sprint ahead<br />Wireframes<br />Test Plans<br />Test driven development<br />Unit tests defined by requirements<br />Test plans are written to define completing requirements<br />Schedule a sprint or two for user research<br />
  15. 15. Product Backlog<br />User Research – Sprint 1 UX<br />Scoring Architecture – Sprint 2<br />Claim Card – Sprint 2 UX<br />Play Card – Sprint 2 UX<br />Sign In – Sprint 2 UX<br />Sign Up – Sprint 3 UX<br />Pick Card – Sprint 4 UX<br />Score Card – Sprint 4 UX<br />
  16. 16. Example Product Development<br />Team agreed to…<br />Two week sprints<br />Daily 15 minute meetings<br />Retrospective, no more than one hour, talk about process<br />One sprint on user research<br />Everyone gives estimates, fill 80 percent of their schedule (8 of 10 days)<br />Developers need breathing room<br />UX’ers need drinking, research time<br />With further sprints, estimates will become more refined<br />
  17. 17. Example Product Development<br />
  18. 18. Sprint Backlog 1<br />Developers<br />Set up development environment<br />Set up testing environment<br />User Experience / QA<br />User Research<br />What is the game<br />Who is the target audience<br />Plan with product owner the first few sprints<br />Plan a design pattern<br />Claim Card<br />
  19. 19. Sprint Backlog 2<br />Developers<br />Scoring Architecture<br />Build Of Pages/Stubs<br />Claim Card<br />User Experience / QA<br />High level use cases<br />High level site map -- Establish Pages/Stubs<br />Play Card<br />
  20. 20. Sprint Backlog 3<br />Developers<br />Create Pages/Stubs<br />Play Card<br />User Experience / QA<br />Pick Card<br />Score Card<br />A/B Testing of Claim Card<br />
  21. 21. Sprint Backlog 4<br />Developers<br />Play Card<br />Score Card<br />User Experience<br />Claim Card Refactor<br />
  22. 22. Retrospective<br />What did we do well<br />What didn’t we do well<br />Is our Product Owner Happy?<br />Produce working fully tested software<br />Did not produce unnecessary stuff<br />Metrics<br />Look at key reports<br />
  23. 23. Example Burndown Charts<br />

×