Not Signed-In
Which clippings match 'User Stories' keyword pg.1 of 1
19 JULY 2014

Using OneNote for gathering design project requirements

"Having a laptop open in a research interview puts a barrier between you and the person you're interviewing, and the typing can be quite distracting and intimidating for the interviewee. But typed notes are searchable, making for very useful reference when you're synthesizing your notes. OneNote is a nice compromise. With a Tablet in slate mode, we remove the physical barrier of the laptop, and as long as you have the pen in a 'Create Handwriting' mode, you can later go back and search your notes as if they were typed. (The handwriting recognition is pretty amazing.)

We sometimes have interviews by phone, and in these cases we often type notes. OneNote can go back and forth pretty seamlessly between handwriting and text, so it keeps all notes in one place. Also I find the quick–keys for adding tags to notes to be very useful when typing. You can tag questions you have, comments for follow–up, and ideas you generate, all with the quick stroke of a key.

For really important meetings, we can also use the audio recording features, which gives the ability to later go back and click on a piece of handwriting to hear what was being said at the time. Unfortunately you have to be using an external microphone for this, or all you hear is the tap–tap–tapping of the stylus hitting the slate surface instead of insightful interview conversation.

And I should note that research is not where OneNote shines the most. There are a few competing tools, like the LiveScribe Echo SmartPen and even pen and paper and that are giving it a run for its money. But as long as we're outfitting our designers with the Tablet, OneNote is a fine tool to use during research."

(Chris Noessel, 7 March 2013, Cooper Journal)

1

TAGS

audio recording • client interview • client liaisoncontent integration • content integration tool • design businessdesign objectivesdesign plandesign projectgeneral grounding document • handwriting • handwriting recognition • interaction design • Livescribe Echo Smartpen • managing design • Microsoft OneNote • multimedia toolnotebooknotesnotetakingpen and paperpersonas (UCD) • project reference • project requirements • requirements capture • requirements elicitationrequirements gatheringresearch interviewscope of practicesearchable content • slate mode • synthesising information • Tablet PCtext recognition • typed notes • user storiesvideo documentationworkflow toolworking practices

CONTRIBUTOR

Simon Perkins
14 APRIL 2011

Scrum and Extreme Programming: User Stories

"User stories are one of the primary development artifacts for Scrum and Extreme Programming (XP) project teams. A user story is a very high–level definition of a requirement, containing just enough information so that the developers can produce a reasonable estimate of the effort to implement it."

(Scott W. Ambler, 2009)

Fig.1 User story card (informal, high level).

Fig.2 User story card (formal, high level).

1

2

CONTRIBUTOR

Simon Perkins
Sign-In

Sign-In to Folksonomy

Can't access your account?

New to Folksonomy?

Sign-Up or learn more.