Scrum secrets for integrating UX, design & development

Download Scrum secrets for integrating UX, design & development

Post on 21-Apr-2017

17.203 views

Category:

Design

2 download

Embed Size (px)

TRANSCRIPT

<ul><li><p>GET AGILE berscrum for UX, design &amp; development </p><p>Pieter Jongerius </p><p>@pieterj </p></li><li><p>FOUR YEARS SCRUM EXPERIENCE </p><p>2 #TWAB2012 @PIETERJ </p></li><li><p>GET AGILE PUBLISHED FALL 2012 </p><p>3 #TWAB2012 @PIETERJ </p><p>Check http://fabrique.nl/getagile for details </p></li><li><p>WE LEARNT THE HARD WAY (1) </p><p>4 #TWAB2012 @PIETERJ </p><p>Weve done waterfall for a decade and a half, and still use it regularly </p></li><li><p>DESIGNERS WITH FOAM BOARDS </p><p>5 #TWAB2012 @PIETERJ </p><p>We found out in 2008 that waterfall presentations &amp; iterations are not always the way to go. </p></li><li><p>WE LEARNT THE HARD WAY (2) </p><p>6 #TWAB2012 @PIETERJ </p><p>Also in 2008, we found out that Scrum is no bed of roses. </p></li><li><p>Today is about sharing. </p><p>What is Uberscrum? </p><p>Secrets &amp; lessons </p><p>on the way </p><p>The process of scrum </p></li><li><p>WHAT IS BERSCRUM ANYWAY? </p></li><li><p>TYPES OF SCRUM WE DO </p><p>9 #TWAB2012 @PIETERJ </p><p>Design only berscrum Staggered sprints </p><p>Interaction </p><p>Visual DESIGN </p><p>development </p><p>We do design only scrum (yes really), but only if third party developers cant scrum with us. We do staggered sprints where some of the parties involved will profit from a more rigid structure </p><p>And then theres what we have come to call berScrum </p></li><li><p>BERSCRUM Brings together Strategists Designers Developers Copywriters Business specialists Marketing &amp; </p><p>communication ..and more And has them working in parallel To create interactive products such as websites and apps. </p><p>10 #TWAB2012 @PIETERJ </p></li><li><p>PRETTY CLOSE TO ROCKET SCIENCE </p><p>11 #TWAB2012 @PIETERJ </p></li><li><p>Bring on the secrets! </p></li><li><p>TEAM SETUP What will the team look like? </p><p>13 </p></li><li><p>SMALLER TEAMS WORK BETTER Ask not how big you can make your team, ask how small you can make it! 2 designers, </p><p>3 developers, a copywriter, product owner </p><p> But heres for the persistent: Max team size around </p><p>10-15 </p><p>14 #TWAB2012 @PIETERJ </p></li><li><p>Requirements for team members? </p></li><li><p>NOTHING SHORT OF SUPERHEROES </p><p> Speak their minds Actively seek feedback Invest in group success </p><p> Empathic Ambitious Skilled Smart </p><p> Motivated to do Scrum </p><p>16 #TWAB2012 @PIETERJ </p></li><li><p>NOTHING SHORT OF SUPERHEROES </p><p> Speak their minds Actively seek feedback Invest in group success </p><p> Empathic Ambitious Skilled Smart </p><p> Motivated to do Scrym </p><p>17 #TWAB2012 @PIETERJ </p><p>"Be like water" -- Bruce Lee </p></li><li><p>Product Owner The toughest job in Scrum. </p></li><li><p>PRODUCT OWNER Strong-willed </p><p>yet open Political sense </p><p>yet independent Demanding </p><p>yet understanding </p><p> Have the mandate &amp; be honest about limitations </p><p> Needs to be well trained </p><p>19 #TWAB2012 @PIETERJ </p></li><li><p>DEALING WITH THE PO We deal with 4 types. Heres one. The Hypercritic Generally enjoys the </p><p>process Discusses all details at </p><p>length Will not move on </p><p>on good enough It all has to be perfect. </p><p> Warning: using flexible scope in your defence will get back at you later on. </p><p>20 #TWAB2012 @PIETERJ </p><p>Ceci nest pas ce PO </p></li><li><p>Look your client in the eye and say: I will always deliver value for money </p><p>Flexible scope also doesn't protect you from the occasional team pizza. </p></li><li><p>SECRET: QUALITY IS FLEXIBLE Great designers hate this But its true </p><p> Better is the enemy of done </p><p> Takes a lot of skill to embrace that succesfully </p><p> Discuss story scores: 7 stories scoring an A or 9 stories scoring a B? </p><p> Decide which stories should be top notch </p><p>22 #TWAB2012 @PIETERJ </p></li><li><p>But how to become a team? </p><p>Team building is a very delicate process. Scrum is not. This needs attention. It really takes one or two sprints for a team to become really tight and well-oiled. </p></li><li><p>WARMING UP GAMES </p><p>24 #TWAB2012 @PIETERJ </p><p>The Marshmallow Challenge Check http://marshmallowchallenge.com/ </p></li><li><p>WARMING UP GAMES </p><p>25 #TWAB2012 @PIETERJ </p><p>Draw the box </p><p>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 USPs and get an immediate grasp of individual team members goals &amp; dreams. </p></li><li><p>LETS KICK ASS! </p><p>26 #TWAB2012 @PIETERJ </p><p>The result is a team that kicks ass on a daily basis and just as easily has a couple of beers at the end of the day as performing a planning poker session on a Monday morning. </p></li><li><p>SPRINT 0 </p><p>Also in Scrum youll 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 were trying to achieve. </p><p>But thats all in the past. </p></li><li><p>SUPER SPRINT 0 </p><p> Parallel definition tracks </p><p> Define strategy </p><p>28 #TWAB2012 @PIETERJ </p></li><li><p>SUPER SPRINT 0 </p><p> Parallel definition tracks </p><p> Define strategy Define architecture </p><p>29 #TWAB2012 @PIETERJ </p></li><li><p>SUPER SPRINT 0 </p><p> Parallel definition tracks </p><p> Define strategy Define architecture Do research </p><p>30 #TWAB2012 @PIETERJ </p></li><li><p>SUPER SPRINT 0 </p><p> Parallel definition tracks </p><p> Define strategy Define architecture Do research </p><p> Get creative! Design a concept </p><p>31 #TWAB2012 @PIETERJ </p></li><li><p>SUPER SPRINT 0 </p><p> Parallel definition tracks </p><p> Define strategy Define architecture Do research </p><p> Get creative! Design a concept but </p><p>dont do a BDUF*. No wireframes in sprint 0! </p><p>* = Big Design Up Front </p><p>#TWAB2012 @PIETERJ 32 </p></li><li><p>SUPER SPRINT 0 </p><p>33 #TWAB2012 @PIETERJ </p><p>Rule of thumb </p><p>Size Sprint 0 to have as many workdays per team member </p><p>as there will be sprints. </p></li><li><p>design is valuable </p><p>The most important thing we create in Sprint 0 is the product backlog. And for this we would like to share an insight. While design is valuable (next slide!) </p></li><li><p>design is valuable a waste! It's just a very expensive way of communicating </p><p>Often necessary, but not always! </p></li><li><p>SECRET: STORY TYPES Not all stories are alike. berstories </p><p>36 #TWAB2012 @PIETERJ </p></li><li><p>SECRET: STORY TYPES Not all stories are alike. berstories development only design only white page </p><p>We specify this during sprint 0 or backlog grooming </p><p>37 #TWAB2012 @PIETERJ </p><p>Here you see a product owner and a developer doing a development-only story. </p></li><li><p>STORY TEMPLATE </p><p>38 #TWAB2012 @PIETERJ </p><p>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. </p></li><li><p>SECRET: SPECIAL OPS STORIES </p><p> backend documentation generic functionality </p><p> rework after demo polishing </p><p>39 #TWAB2012 @PIETERJ </p><p>Anything to bundle additional work, other than for specific end user benefits, into convenient chunks. Dont let Scrum dogmas prevent you from tweaking the way you define your stories. </p></li><li><p>I SHOULDNT BE SHOWING YOU THIS </p><p>40 #TWAB2012 @PIETERJ </p><p>Some teams even prefer to use simple functionality stories. It saves them from the semantic layering of traditional user story syntaxes. Big alert: stay user centered and and keep an eye on the total solution space! </p><p> Again, the lesson here is that you have to change the rules to accommodate teams and projects. </p></li><li><p>Team ready, sprint setup ready, backlog ready, </p></li><li><p>LETS SPRINT! </p></li><li><p>SECRET: LETS GET PHYSICAL </p><p>43 #TWAB2012 @PIETERJ </p><p>We are REALLY religious about making &amp; keeping stuff physical and not letting it sink onto networked hard drives. </p></li><li><p>DRAW YOUR PROJECT GOALS </p><p>44 #TWAB2012 @PIETERJ </p><p>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. </p></li><li><p>KEYWORDS ON THE WALL </p><p>45 #TWAB2012 @PIETERJ </p><p>Discuss your work. Point at keywords on the wall. It keeps you on track. </p></li><li><p>WHO &amp; WHEN </p><p>46 #TWAB2012 @PIETERJ </p><p>Oh, dont use Excel either :) (and gDocs is no better, really avoid hiding stuff in computers) </p></li><li><p>TASK PERSONALIZATION </p><p>47 #TWAB2012 @PIETERJ </p><p>Physical task claiming tags help team members maintain that sense of responsibility. My task! Ill finish it! </p></li><li><p>MORE FUN USING FACES </p><p>48 #TWAB2012 @PIETERJ </p></li><li><p>TOO MESSY? </p><p>49 #TWAB2012 @PIETERJ </p><p>So can Scrum rooms get too messy? Maybe. But were fine with it as long as it works for the team! </p></li><li><p>TOO TIDY </p><p>50 #TWAB2012 @PIETERJ </p><p>They can be too tidy though. This sitemap is so beautifully crafted that no-one will dare altering it. Not really agile, is it? </p></li><li><p>POLE OF QUOTES </p><p>51 #TWAB2012 @PIETERJ </p><p>The weirdest things get said during sprints. Its a lot of fun writing the best quotes down. </p></li><li><p>#DUBSTEPFRIDAY </p><p>52 #TWAB2012 @PIETERJ </p><p>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. </p></li><li><p>OWN THE PLACE </p><p>53 #TWAB2012 @PIETERJ </p><p>Its 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. </p><p>It makes things even more fun, and it keeps the product personality on brand! </p></li><li><p>Mayhem? Really? </p></li><li><p>55 #TWAB2012 @PIETERJ </p><p>SPRINT FOCUS FOR MAIN DISCIPLINES </p><p>time &gt; No, its not just mayhem. While one of the agile principles is that the team should be self-organizing, we can provide a little structure. Especially for beginner teams. </p></li><li><p>56 #TWAB2012 @PIETERJ </p><p>Sketch &amp; discuss </p><p>Test &amp; spikes </p><p>interaction design </p><p>SPRINT FOCUS FOR MAIN DISCIPLINES </p><p>Flows &amp; states </p><p>time &gt; </p><p>Please keep in mind while I build this up, </p></li><li><p>57 #TWAB2012 @PIETERJ </p><p>Sketch &amp; discuss </p><p>Test &amp; spikes </p><p>Templates </p><p>Test &amp; Des-only stories </p><p>interaction design </p><p>visual design </p><p>SPRINT FOCUS FOR MAIN DISCIPLINES </p><p>Modules &amp; states </p><p>Flows &amp; states </p><p>time &gt; </p><p>that its just A way of providing some structure in berscrum. Providing it WITH the team. Not TO the team. </p></li><li><p>58 #TWAB2012 @PIETERJ </p><p>Sketch &amp; discuss </p><p>Test &amp; spikes </p><p>Templates </p><p>Test &amp; Des-only stories </p><p>interaction design </p><p>visual design </p><p>front-end development </p><p>Dev-only stories </p><p>Test &amp; spikes </p><p>SPRINT FOCUS FOR MAIN DISCIPLINES </p><p>Implement design </p><p>Modules &amp; states </p><p>Flows &amp; states </p><p>time &gt; </p><p>You might see this chart as a mere starting point. </p></li><li><p>59 #TWAB2012 @PIETERJ </p><p>Sketch &amp; discuss </p><p>Test &amp; spikes </p><p>Templates </p><p>Test &amp; Des-only stories </p><p>interaction design </p><p>visual design </p><p>front-end development </p><p>back-end development </p><p>Dev-only stories </p><p>Test &amp; spikes </p><p>Objects &amp; data Admin section </p><p>Test &amp; spikes </p><p>SPRINT FOCUS FOR MAIN DISCIPLINES </p><p>Controllers, flows </p><p>Implement design </p><p>Modules &amp; states </p><p>Flows &amp; states </p><p>time &gt; FABRIQUE </p></li><li><p>Sketch &amp; discuss </p><p>Test &amp; spikes </p><p>Templates </p><p>Test &amp; Des-only stories </p><p>interaction design </p><p>visual design </p><p>front-end development </p><p>back-end development </p><p>Dev-only stories </p><p>Test &amp; spikes </p><p>Objects &amp; data Admin section </p><p>Test &amp; spikes </p><p>SPRINT FOCUS FOR MAIN DISCIPLINES </p><p>Controllers, flows </p><p>Implement design </p><p>Modules &amp; states </p><p>Flows &amp; states </p><p>time &gt; </p><p>60 #TWAB2012 @PIETERJ </p><p>Challenge: Moving on in time </p><p>Challenge: Starting quickly </p></li><li><p>Scrum: agile but fragile </p></li><li><p>ADVANCED DELIVERABLES Preventing us from cutting corners </p></li><li><p>CODE OF CONDUCT </p><p>63 #TWAB2012 @PIETERJ </p><p>The code of conduct is a set of rules, created and used by developers. It can be about all types of behavior, such as using dedicated refactoring time, testing including unit tests, environment use, commits and more. </p></li><li><p>DOUBLE DEFINITION OF DONE </p><p>64 #TWAB2012 @PIETERJ </p><p>The consequence of differentiating into story types, is that youll have to have a differentiated, or double DOD, with split requirements for instance for design, development and customer acceptance. </p></li><li><p>DEFINITION OF READY </p><p>In some Scrums, stories often yield unexpected impediments </p><p> Business rules Required content Technical complexity </p><p>DOR is a set of requirements that helps making stories ready before you sprint. Use only when you really need it. </p><p>65 #TWAB2012 @PIETERJ </p></li><li><p>FINALLY Demo &amp; retrospective </p></li><li><p>DEMO: THE STAKEHOLDER TEST </p><p>67 #TWAB2012 @PIETERJ </p><p>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. Theyll love it! </p></li><li><p>RETROSPECTIVE Address human to human </p><p>issues! When all fails, no </p><p>worries, fall back to staggered sprints. Try again next time! </p><p>68 #TWAB2012 @PIETERJ </p></li><li><p>SO HERES HOPING </p><p>69 #TWAB2012 @PIETERJ </p><p>If theres 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. </p><p>If you put them first, I promise, youll have a great time! </p></li><li><p>70 #TWAB2012 @PIETERJ </p><p>Pieter Jongerius </p><p>@pieterj </p><p>All images copyright of their respective owners </p></li><li><p>Get Agile, the book </p><p>Published fall 2012 </p><p>Follow @getagilebook or check http://fabrique.nl/getagile </p><p>Scrum Academy by Fabrique &amp; GIFT </p><p>Training for Scrum Masters &amp; POs </p><p>TWAB 100 discount, use code TWAB Offer ends November 12, 2012 </p><p> scrumacademy.nl </p></li></ul>