Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

SXSW2013: Get agile! Scrum insights for UX, design and development

4.196 visualizaciones

Publicado el

Insights from our new Scrum manual, updated for SXSW Interactive. --
Applying Scrum changes the day-to-day reality of agencies dramatically. If done well, it improves output and profitability like crazy.
However, for agencies, Scrum dynamics are radically different from in-house design and development teams. Our leading Dutch design agency, Fabrique, has built up over 35,000 hours of Scrum experience since 2008, designing and developing interactive products such as websites and mobile apps for national and international customers.
In this presentation we share our best-kept secrets. This talk features tons of photos from our scrum rooms.

Publicado en: Tecnología
  • Sé el primero en comentar

SXSW2013: Get agile! Scrum insights for UX, design and development

  1. 1. erius et al.Pieter Jong GET AGILE! Amazon: Scrum for UX, design & development get-agile 1
  2. 2. GET AGILE! Over 4 years o f 35,000+ Scrum experience hours#GETAGILE @PIETERJ 2
  3. 3. SHARING WHAT WE’VE LEARNT Our agile Agency Des / dev ambition challenges Integration#GETAGILE @PIETERJ 3
  4. 4. OUR AGILE AMBITION Speed, quality, risk management 4
  5. 5. OUR AGENCY Dutch We are a full service agency, we design & develop all things digital, 100 peoples such as apps & web sites. We have around 6 scrum rooms running at any time 3 office rms#GETAGILE @PIETERJ 6 scrum 5
  6. 6. WE LEARNT THE HARD WAY However, when we adopted scrum, we quickly found out that it’s no bed of roses. We did learn the hard way: sprints ending up in chaos, team members feeling left out, facing massive rework, etc.#GETAGILE @PIETERJ 6
  7. 7. AMBITION: FULL INTEGRATIONBuilding great productsrequires·  Strategists·  Designers·  Developers·  Copywriters·  Business specialists·  Marketing & communication·  ..and moreOur way of Scrum·  working in parallel·  deliver shippable product·  every single sprint.#GETAGILE @PIETERJ 7
  8. 8. ÜBERSCRUM Out of sheer respect for the agility it takes to do this well, we’ve come to call this Überscrum.#GETAGILE @PIETERJ 8
  10. 10. BUILDING A TEAM What will the team look like? 10
  11. 11. SCRUM DEPENDS ON THE TEAM Most of what I’ll share concerns human skills and people management. Bringing the team together, not only physically, but mentally also. It’s no secret that this works best with smaller teams, of around 5-7 people. Although you can scale it up to 15 if you have to.#GETAGILE @PIETERJ 11
  12. 12. NOTHING SHORT OF SUPERHEROES·  Speak their minds·  Actively seek feedback·  Invest in group success·  Empathic·  Ambitious·  Skilled·  Inventive·  Motivated to Scrum#GETAGILE @PIETERJ 12
  13. 13. AGENCY CHALLENGES First Team composition varies. Team building is daunting in any Scrum environment. But for an agency, team composition varies a lot, based on capacity, specific skills, and 3rd party cooperation.#GETAGILE @PIETERJ 13
  14. 14. TEAM BUILDING: GAMES Draw the box All team members draw a packaging as if the product was on sale on a shelf in a store. You are forced to think in USP’s and get an immediate grasp of individual team members goals & dreams.#GETAGILE @PIETERJ 14
  15. 15. TEAM BUILDING: GAMES The Marshmallow Challenge Check @PIETERJ 15
  16. 16. TEAM BUILDINGINSPECT & ADAPT GIVE TIMEIn daily standups and Minimum of 3 sprintsreviews, we address per project.personal and team issues.#GETAGILE @PIETERJ 16
  17. 17. AGENCY CHALLENGES First Team composition varies. Second Team members can’t be 100% dedicated to the project. You will have agency- and other stuff. Meetings, phone calls, other projects. This can be a big disappointment and frustration for the team.#GETAGILE @PIETERJ 17
  18. 18. SCRUM FOCUS SOLUTIONS1.Agree on a% focus, f.i. 80-90%2.Don’t necessarily do afulltime scrum.Use a minimum of 3 days/wk3.Scrum days may vary perdiscipline.But keep the team together!#GETAGILE @PIETERJ 18
  19. 19. SCRUM MASTER PARADOX·  Team builder, yet be able to confront·  Authority in their craft, yet have an eye for all disciplines·  Switch easily between Scrum Rules and Agile PrinciplesIn our agency·  Mostly senior UX designers#GETAGILE @PIETERJ 19
  20. 20. CLIENT IN THE HOUSE! Embrace the Product OwnerThe most profound impact Scrum has on the way of working in an agency, is having the client around all the time. No more big briefing or presentation meetings: the client is there to provide input continuously.
  21. 21. Product OwnerThe toughest job in Scrum.
  22. 22. PRODUCT OWNER PARADOX·  Strong-willed yet open·  Political sense yet independent·  Demanding yet understanding·  Have the mandate & be honest about limitations#GETAGILE @PIETERJ 22
  23. 23. PART OF THE TEAM?As much as possible.·  Tasks·  Creativity·  Really open upPresent in the team, fromfulltime to a minimal2 mornings /wk#GETAGILE @PIETERJ 23
  25. 25. BEWARE OF THE… OPPORTUNIST WORRIER MEDDLER HYPERCRITIC Let’s pick one: The Hypercritic generally enjoys the process, discusses all details at length and will not move on on “good enough”. It all has to be perfect. Warning: using flexible scope in your defence will get back at you later on.#GETAGILE @PIETERJ 25
  26. 26. ÜBERSCRUMDesign hearts development – and the other way around. 26
  27. 27. STOP ATTACHING UX TO ‘SCRUM’ If you want to remain agile, design cannot be a prerequisite. It cannot be on a definition of ready. If you want design to have impact, UX design cannot be some advisory group to the PO, who’ll decide what to turn into stories, and what not. Eliminate this waste.#GETAGILE @PIETERJ 27
  28. 28. Step up as a single teamBe creative and solve problems Create shippable products Together.
  29. 29. STOP ACTING LIKE A SPOILED PRINCESS You will have to make compromises. Designers must for instance face the truth that some things are unaffordable to build Developers must invest in going the extra mile to create better UX.#GETAGILE @PIETERJ 29
  30. 30. STOP SEARCHING FOR THE BEST RULES ✘ - OR - Staggered sprints Shared stories Interaction Visual DESIGN development There is not one strategy of interdisciplinary cooperation that will work for all of your stories.#GETAGILE @PIETERJ 30
  31. 31. STAY AGILE!"Be like water" -- Bruce Lee#GETAGILE @PIETERJ 31
  32. 32. a design is valuable! waste Its just a very expensive way of communicating Often necessary, ! but not always
  33. 33. SECRET: STORY TYPESNot all stories are alike.·  überstories·  development only·  design onlyWe specify this duringsprint 0 or backlog grooming#GETAGILE @PIETERJ 33
  34. 34. STORY TEMPLATE We use a custom made story template to accommodate for documenting the type of the story: the disciplines involved are checked. Again: we decide on this BEFORE we start the sprint.#GETAGILE @PIETERJ 34
  35. 35. SECRET: QUALITY IS FLEXIBLE·  Skilled professionals hate this·  But it’s true·  Better is the enemy of done·  Takes a lot of skill·  Story scores: 7 times an A or 9 times a B?·  Which stories should be top notch?#GETAGILE @PIETERJ 35
  36. 36. FLEXIBLE EVERYTHING? No. Look your client in the eye and say: I will always deliver value for money Flexible scope doesnt protect you from the a. occasional pizz
  37. 37. SUPER SPRINT 0 Balancing preparation and BDUF Also in Scrum you’ll need a solid start before actual sprints, or everyone will sprint in a different direction. Too often, we made the mistake of starting on just a hunch of what we we’re trying to achieve. But that’s all in the past.#GETAGILE @PIETERJ 37
  38. 38. SUPER SPRINT 0Parallel definition tracks·  Define strategy#GETAGILE @PIETERJ 38
  39. 39. SUPER SPRINT 0Parallel definition tracks·  Define strategy·  Define architecture#GETAGILE @PIETERJ 39
  40. 40. SUPER SPRINT 0Parallel definition tracks·  Define strategy·  Define architecture·  Do research#GETAGILE @PIETERJ 40
  41. 41. SUPER SPRINT 0Parallel definition tracks·  Define strategy·  Define architecture·  Do research·  Get creative!·  Design a concept…#GETAGILE @PIETERJ 41
  42. 42. SUPER SPRINT 0Parallel definition tracks·  Define strategy·  Define architecture·  Do research·  Get creative! ✘·  Design a concept but don’t do a BDUF** = Big Design Up Front#GETAGILE @PIETERJ 42
  43. 43. SUPER SPRINT 0·  Takes 3-6 weeks·  Consumes some 20% of project budget·  Has a slower pace·  Involves all team members#GETAGILE @PIETERJ 43
  44. 44. Team ready, PO ready, backlog ready, LET’S SPRINT!
  46. 46. SECRET: LET’S GET PHYSICAL The room is the one ultimate thing the whole team shares. It’s an opportunity to create a real visceral project reality. We’re really religious about this. And not just the scrum board.#GETAGILE @PIETERJ 46
  47. 47. DRAW YOUR PROJECT GOALS Strategic PowerPoint presentations in project folders will NOT be looked at. Word documents will not even be remembered to have been made at all. Seriously.#GETAGILE @PIETERJ 47
  48. 48. KEYWORDS ON THE WALL Discuss your work. Point at keywords on the wall. It keeps you on track.#GETAGILE @PIETERJ 48
  49. 49. WHO & WHEN Oh, also use Excel and Outlook as little as possible :) (and gDocs is no better, really avoid hiding stuff in computers)#GETAGILE @PIETERJ 49
  50. 50. TASK PERSONALIZATION Physical task claiming tags help team members maintain that sense of responsibility. My task! I’ll finish it!#GETAGILE @PIETERJ 50
  52. 52. CODE OF CONDUCT Another example: put up a Code of Conduct. Created and used by developers. States when to do refactoring, how to handle unit tests. In fact put up anything on the wall that will keep the team on track.#GETAGILE @PIETERJ 52
  53. 53. DEFINITION OF READYIn some Scrums, storiesoften yield unexpectedimpediments·  Business rules·  Required content·  Technical complexityDOR is a set of requirementsthat helps making storiesready before you sprint.Use only when you reallyneed it.#TWAB2012 @PIETERJ 53
  54. 54. DOUBLE DEFINITION OF DONE The introduction of Story types leads to the need for a more differentiated, in our case often Double Definition of Done, splitting design and tech requirements.#GETAGILE @PIETERJ 54
  55. 55. TOO MESSY? So can Scrum rooms get too messy? Maybe. But we’re fine with it as long as it works for the team!#GETAGILE @PIETERJ 55
  56. 56. TOO TIDY They can be too tidy though. This sitemap is so beautifully crafted that no-one will dare altering it. Not really agile, is it?#GETAGILE @PIETERJ 56
  57. 57. POLE OF QUOTES The weirdest things get said during sprints. It’s a lot of fun writing the best quotes down.#GETAGILE @PIETERJ 57
  58. 58. #DUBSTEPFRIDAY All work no play makes Jack a dull boy. To lighten things up a little, some teams use theme days. Like Dubstep Friday! Formal Thursday has also been spotted, as is a regular wakeboard training on the rug.#GETAGILE @PIETERJ 58
  59. 59. OWN THE PLACE It’s basically a matter of owning the place, feeling almost at home. Here you see Danny and Nils in their little SuperTrash shrine, being all feminine and independent. It makes things even more fun, and it keeps the product personality on brand!#GETAGILE @PIETERJ 59
  61. 61. SPRINT FOCUS FOR MAIN DISCIPLINES No, it’s not just mayhem. While one of the agiletime > principles is that the team should be self-organizing, we can provide a little structure. Especially for beginner teams.#TWAB2012 @PIETERJ 61
  62. 62. SPRINT FOCUS FOR MAIN DISCIPLINES Please keep in mind while I build this up, Sketch & interaction discuss Flows & states design Test & spikes time >#TWAB2012 @PIETERJ 62
  63. 63. SPRINT FOCUS FOR MAIN DISCIPLINES …that it’s just A way of providing some structure in überscrum. Providing it WITH the team. Not TO the team. Templates visual Modules & states design Test & Des-only stories Sketch & interaction discuss Flows & states design Test & spikes time >#TWAB2012 @PIETERJ 63
  64. 64. SPRINT FOCUS FOR MAIN DISCIPLINES Dev-only front-end stories Implement design development Test & spikes You might see this chart as a mere starting point. Templates visual Modules & states design Test & Des-only stories Sketch & interaction discuss Flows & states design Test & spikes time >#TWAB2012 @PIETERJ 64
  65. 65. Startlyng iSPRINT FOCUS FOR MAIN DISCIPLINES quick back-end development Objects & data Admin section Controllers, flows Test & spikes Dev-only front-end stories Implement design development Test & spikes Templates visual Modules & states design Test & Des-only stories Sketch & interaction discuss Flows & states Movingmon in ti e design Test & spikes time >#GETAGILE @PIETERJ 65
  66. 66. Scrum: agile but fragile
  67. 67. FINALLY…Demo & retrospective 67
  68. 68. DEMO: THE STAKEHOLDER TEST When the product permits, you might NOT demo it, but have it user tested by the stake holders at demo time. Give them assignments, have them use it. They’ll love it!#GETAGILE @PIETERJ 68
  69. 69. RETROSPECTIVE·  Address H2H issues.·  When all fails, fall back to strict staggered sprints. Try again next time!#GETAGILE @PIETERJ 69
  70. 70. SO HERE’S HOPING… If there’s one thing I would like you to take with you, its that Scrum is about people, their skills, wishes and dreams. It is about end users; about the customer and their stakeholders; it is about the team. If you put them first, I promise, you’ll have a great time!#GETAGILE @PIETERJ 70
  71. 71. Amazon And right now in the SX Bookstore, outside this room in the foyer. Pieter Jongerius et al. @pieterjbrands, design & interaction @getagilebook