“Use a picture. It’s worth a thousand words.” That was the advice of Arthur Brisbane, Editor The Syracuse Post Standard March 28, 1911. Despite originally referring to newsprint, the adage still holds true in the digital age.
“Sketching for understanding” is an efficient and effective way to gather tons of ideas in a short period of time while cultivating shared understanding across agile teams.With the right structure and active participation, sketching with Scrum teams can really pay dividends throughout the release life cycle.
Use the following guide to help plan and facilitate your next agile sketching session.
Define Inputs (5 minutes)
Before you get started you’ll need to identify some inputs. Inputs are data that inform the sketching process. They can include a product vision, assumption personas of intended users, and specific scenarios where they might use the product or feature.
Start with the vision
Insert vision summary and goals for the product or feature here…
- Using individual sticky notes, write as many possible scenarios where a person would experience product or feature.
- Using separate sticky notes, write down possible functionality the product or feature should have to enhance the experience of your scenarios.
- Now imagine the person in your scenario – using a separate your sticky note, write a brief description; age, gender, job title and interests.
Sketch (5 minutes)
Focus on the ideas. It’s not about bad or good, it’s about Can you see it? Can you understand it?
Using boxes, arrows, callouts, and common metaphors, anyone can communicate an idea with pen and paper.
- Using blank paper, explore as many ideas as possible. This phase is about ideas and exploration so try to force your self to come up with as many ideas as possible. Don’t stop at the first one.
- If you get stuck, list ideas as words, then try different combinations of words to inspire different ideas. Sketch those ideas on new paper.
- Another technique is to explore opposites. If one idea is a richly animated experience, explore static two-dimensional options.
- We want fast not perfect
- If you mess up – don’t start over
- If things really go wrong – grab a new sheet of paper
- Thin/Regular Sharpie
- Sticky notes
- 6up & 1up templates
Get Organized (10 minutes)
Now that you have created lots of ideas, explore how those ideas work together.
- First you’ll need to put your inputs on the wall. It’s handy to have them available when talking about different ideas
- Next, using scissors and drafting dots you’ll cut up and add your ideas to the wall.
- Once all your ideas are posted, review them as a group to better understand the thinking behind them
- With a shared understanding of what you’re looking at, group similar ideas. The team should move things around as necessary.
- Next, label the groupings. It’s good to use sticky notes here so we can move them around as needed.
Critique is about critical thinking. Effective critique is selfless. The goal of critique is to gather initial thoughts and reactions, to better understand the thinking behind an idea.
- Provide time, sticky notes and markers for people to review ideas and add notes as needed next to the related ideas
- Ask open questions that include HOW, WHERE, WHO – not closed questions with DOES, SHOULD, or COULD (critique nor judgment)
- Refer to inputs like requirements, user descriptions when appropriate
- The goal is to collect and display as much of the feedback, notes, questions, comments, as possible within the context of the design.
- Working individually, use the red sticky notes to document as many holes or concerns you can think of. The goal is to be thorough and inclusive
- Add each sticky to the wall next to the thing they are referring to
- After comments and notes have been added to the board, review as a team
Wrap Up (5 minutes)
Now that you have collected and organized notes, comments, and sketches, the results need to be captured.
- Review overall comments.
- Take photo(s) of the wall. Be sure to capture clear photos of the work for future reference
- Thank everyone for their participation and remind the team the results of the exercise will be used to inform the design process in upcoming iterations