Upload
pieter-jongerius
View
9.563
Download
0
Embed Size (px)
DESCRIPTION
Agile or Lean UX requires teamwork, and lots of it. One of the hardest parts of doing Agile UX in a multidisciplinary environment is, well, staying alive. Scrumming in one room with a product owner, UX- and visual designers, editors, and front- and back-end developers, is challenging to say the least. We have respectfully come to call this form of scrum ÜberScrum. In this talk, Pieter Jongerius has shared his best-kept scrumming secrets with experienced Scrum practitioners. What tools, what deliverables and what rhythms should you use to actually succeed in designing & developing at the same time? What are known pitfalls and key success factors? Fabrique has been using scrum since 2008. Some 60 team members have scrummed well over 30,000 hours for national and international clients.
Citation preview
GET AGILE Überscrum for UX, design & development
Pieter Jongerius
@pieterj
FOUR YEARS SCRUM EXPERIENCE
2 #TWAB2012 @PIETERJ
GET AGILE – PUBLISHED FALL 2012
3 #TWAB2012 @PIETERJ
Check http://fabrique.nl/getagile for details
WE LEARNT THE HARD WAY (1)
4 #TWAB2012 @PIETERJ
We’ve done waterfall for a decade and a half, and still use it regularly
DESIGNERS WITH FOAM BOARDS
5 #TWAB2012 @PIETERJ
We found out in 2008 that waterfall presentations & iterations are not always the way to go.
WE LEARNT THE HARD WAY (2)
6 #TWAB2012 @PIETERJ
Also in 2008, we found out that Scrum is no bed of roses.
Today is about sharing.
What is Uberscrum?
Secrets & lessons
on the way
The process of scrum
WHAT IS ÜBERSCRUM ANYWAY?
TYPES OF SCRUM WE DO
9 #TWAB2012 @PIETERJ
Design only Überscrum Staggered sprints
Interaction
Visual DESIGN
development
We do design only scrum (yes really), but only if third party developers can’t scrum with us. We do staggered sprints where some of the parties involved will profit from a more rigid structure
And then there’s what we have come to call ÜberScrum…
ÜBERSCRUM Brings together · Strategists · Designers · Developers · Copywriters · Business specialists · Marketing &
communication · ..and more And has them working in parallel To create interactive products such as websites and apps.
10 #TWAB2012 @PIETERJ
PRETTY CLOSE TO ROCKET SCIENCE
11 #TWAB2012 @PIETERJ
Bring on the secrets!
TEAM SETUP What will the team look like?
13
SMALLER TEAMS WORK BETTER Ask not how big you can make your team, ask how small you can make it! · 2 designers,
3 developers, a copywriter, product owner
But here’s for the persistent: · Max team size around
10-15
14 #TWAB2012 @PIETERJ
Requirements for team members?
NOTHING SHORT OF SUPERHEROES
· Speak their minds · Actively seek feedback · Invest in group success
· Empathic · Ambitious · Skilled · Smart
· Motivated to do Scrum
16 #TWAB2012 @PIETERJ
NOTHING SHORT OF SUPERHEROES
· Speak their minds · Actively seek feedback · Invest in group success
· Empathic · Ambitious · Skilled · Smart
· Motivated to do Scrym
17 #TWAB2012 @PIETERJ
"Be like water" -- Bruce Lee
Product Owner The toughest job in Scrum.
PRODUCT OWNER · Strong-willed
yet open · Political sense
yet independent · Demanding
yet understanding
· Have the mandate & be honest about limitations
· Needs to be well trained
19 #TWAB2012 @PIETERJ
DEALING WITH THE PO We deal with 4 types. Here’s one. The Hypercritic · Generally enjoys the
process · Discusses all details at
length · 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.
20 #TWAB2012 @PIETERJ
Ceci n’est pas ce PO
Look your client in the eye and say: I will always deliver value for money
Flexible scope also doesn't protect you from the occasional team pizza.
SECRET: QUALITY IS FLEXIBLE · Great designers hate this · But it’s true
· Better is the enemy of done
· Takes a lot of skill to embrace that succesfully
· Discuss story scores: 7 stories scoring an A or 9 stories scoring a B?
· Decide which stories should be top notch
22 #TWAB2012 @PIETERJ
But how to become a team?
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.
WARMING UP GAMES
24 #TWAB2012 @PIETERJ
The Marshmallow Challenge Check http://marshmallowchallenge.com/
WARMING UP GAMES
25 #TWAB2012 @PIETERJ
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.
LET’S KICK ASS!
26 #TWAB2012 @PIETERJ
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.
SPRINT 0
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.
SUPER SPRINT 0
· Parallel definition tracks
· Define strategy
28 #TWAB2012 @PIETERJ
SUPER SPRINT 0
· Parallel definition tracks
· Define strategy · Define architecture
29 #TWAB2012 @PIETERJ
SUPER SPRINT 0
· Parallel definition tracks
· Define strategy · Define architecture · Do research
30 #TWAB2012 @PIETERJ
SUPER SPRINT 0
· Parallel definition tracks
· Define strategy · Define architecture · Do research
· Get creative! · Design a concept…
31 #TWAB2012 @PIETERJ
SUPER SPRINT 0
· Parallel definition tracks
· Define strategy · Define architecture · Do research
· Get creative! · Design a concept but
don’t do a BDUF*. No wireframes in sprint 0!
* = Big Design Up Front
#TWAB2012 @PIETERJ 32
✘
SUPER SPRINT 0
33 #TWAB2012 @PIETERJ
Rule of thumb
Size Sprint 0 to have as many workdays per team member
as there will be sprints.
design is valuable
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!)
design is valuable a waste! It's just a very expensive way of communicating
Often necessary, but not always!
SECRET: STORY TYPES Not all stories are alike. · überstories
36 #TWAB2012 @PIETERJ
SECRET: STORY TYPES Not all stories are alike. · überstories · development only · design only · white page
We specify this during sprint 0 or backlog grooming
37 #TWAB2012 @PIETERJ
Here you see a product owner and a developer doing a development-only story.
STORY TEMPLATE
38 #TWAB2012 @PIETERJ
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.
SECRET: SPECIAL OPS STORIES
· backend · documentation · generic functionality
· rework after demo · polishing
39 #TWAB2012 @PIETERJ
Anything to bundle additional work, other than for specific end user benefits, into convenient chunks. Don’t let Scrum dogmas prevent you from tweaking the way you define your stories.
I SHOULDN’T BE SHOWING YOU THIS
40 #TWAB2012 @PIETERJ
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!
Again, the lesson here is that you have to change the rules to accommodate teams and projects.
Team ready, sprint setup ready, backlog ready, …
LET’S SPRINT!
SECRET: LET’S GET PHYSICAL
43 #TWAB2012 @PIETERJ
We are REALLY religious about making & keeping stuff physical and not letting it sink onto networked hard drives.
DRAW YOUR PROJECT GOALS
44 #TWAB2012 @PIETERJ
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.
KEYWORDS ON THE WALL
45 #TWAB2012 @PIETERJ
Discuss your work. Point at keywords on the wall. It keeps you on track.
WHO & WHEN
46 #TWAB2012 @PIETERJ
Oh, don’t use Excel either :) (and gDocs is no better, really avoid hiding stuff in computers)
TASK PERSONALIZATION
47 #TWAB2012 @PIETERJ
Physical task claiming tags help team members maintain that sense of responsibility. My task! I’ll finish it!
MORE FUN USING FACES
48 #TWAB2012 @PIETERJ
TOO MESSY?
49 #TWAB2012 @PIETERJ
So can Scrum rooms get too messy? Maybe. But we’re fine with it as long as it works for the team!
TOO TIDY
50 #TWAB2012 @PIETERJ
They can be too tidy though. This sitemap is so beautifully crafted that no-one will dare altering it. Not really agile, is it?
POLE OF QUOTES
51 #TWAB2012 @PIETERJ
The weirdest things get said during sprints. It’s a lot of fun writing the best quotes down.
#DUBSTEPFRIDAY
52 #TWAB2012 @PIETERJ
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.
OWN THE PLACE
53 #TWAB2012 @PIETERJ
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!
Mayhem? Really?
55 #TWAB2012 @PIETERJ
SPRINT FOCUS FOR MAIN DISCIPLINES
time > No, it’s 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.
56 #TWAB2012 @PIETERJ
Sketch & discuss
Test & spikes
interaction design
SPRINT FOCUS FOR MAIN DISCIPLINES
Flows & states
time >
Please keep in mind while I build this up,
57 #TWAB2012 @PIETERJ
Sketch & discuss
Test & spikes
Templates
Test & Des-only stories
interaction design
visual design
SPRINT FOCUS FOR MAIN DISCIPLINES
Modules & states
Flows & states
time >
…that it’s just A way of providing some structure in überscrum. Providing it WITH the team. Not TO the team.
58 #TWAB2012 @PIETERJ
Sketch & discuss
Test & spikes
Templates
Test & Des-only stories
interaction design
visual design
front-end development
Dev-only stories
Test & spikes
SPRINT FOCUS FOR MAIN DISCIPLINES
Implement design
Modules & states
Flows & states
time >
You might see this chart as a mere starting point.
59 #TWAB2012 @PIETERJ
Sketch & discuss
Test & spikes
Templates
Test & Des-only stories
interaction design
visual design
front-end development
back-end development
Dev-only stories
Test & spikes
Objects & data Admin section
Test & spikes
SPRINT FOCUS FOR MAIN DISCIPLINES
Controllers, flows
Implement design
Modules & states
Flows & states
time > © FABRIQUE
Sketch & discuss
Test & spikes
Templates
Test & Des-only stories
interaction design
visual design
front-end development
back-end development
Dev-only stories
Test & spikes
Objects & data Admin section
Test & spikes
SPRINT FOCUS FOR MAIN DISCIPLINES
Controllers, flows
Implement design
Modules & states
Flows & states
time >
60 #TWAB2012 @PIETERJ
Challenge: Moving on in time
Challenge: Starting quickly
Scrum: agile but fragile
ADVANCED DELIVERABLES Preventing us from cutting corners
CODE OF CONDUCT
63 #TWAB2012 @PIETERJ
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.
DOUBLE DEFINITION OF DONE
64 #TWAB2012 @PIETERJ
The consequence of differentiating into story types, is that you’ll have to have a differentiated, or double DOD, with split requirements for instance for design, development and customer acceptance.
DEFINITION OF READY
In some Scrums, stories often yield unexpected impediments
· Business rules · Required content · Technical complexity
DOR is a set of requirements that helps making stories ready before you sprint. Use only when you really need it.
65 #TWAB2012 @PIETERJ
FINALLY Demo & retrospective
DEMO: THE STAKEHOLDER TEST
67 #TWAB2012 @PIETERJ
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!
RETROSPECTIVE · Address human to human
issues! · When all fails, no
worries, fall back to staggered sprints. Try again next time!
68 #TWAB2012 @PIETERJ
SO HERE’S HOPING…
69 #TWAB2012 @PIETERJ
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!
70 #TWAB2012 @PIETERJ
Pieter Jongerius
@pieterj
All images copyright of their respective owners
Get Agile, the book
Published fall 2012
Follow @getagilebook or check http://fabrique.nl/getagile
Scrum Academy by Fabrique & GIFT
Training for Scrum Masters & PO’s
TWAB €100 discount, use code “TWAB” Offer ends November 12, 2012
scrumacademy.nl