1 / 11

Features/requirements analysis using design studio

Requirement’s studio. Features/requirements analysis using design studio. Irina Radu Product Development Manager @ Cint 2012-03-09. Feature request. As a user of the software I want some tips/ help in the software Because I don’t understand how some things work / what they do.

ingrid
Télécharger la présentation

Features/requirements analysis using design studio

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Requirement’sstudio Features/requirements analysis using design studio Irina Radu Product Development Manager @Cint 2012-03-09

  2. Feature request As a userof the software I wantsome tips/help in the software Because I don’tunderstandhowsomethingswork/whatthey do

  3. Older requirements analysis vs. new Older analysis Requirement’s studio Design studio for requirementsanalysis Devs, business owner, customer, UX, sales etc. • One person analysis

  4. Requirement’s studio • Steps • Explainwhatneedssolving • Optional : focus • Repeatuntilyoufound a solution: • Sketch / writeideas • Present • Critique

  5. Step 1 Explain what needs solving • Givecontext • Present software & people • Present goal: • Software willhelp the userunderstandwhat features do

  6. Step2. Focus session • 2-3 minutes for peopleto: • Saywhatcomes in mind whenthinkingof the topic

  7. Step 3 Sketch / write ideas • 6 minutes to put as many ideas on paper • Sketch / write on a 6up

  8. Step 4 Present ideas • 2 min/person to present ideas • Show sketches and explain • Present just in words etc. • Who, how, what, why

  9. Step 5 Critique • 3 minutes/person’sideas • Everybodydiscusswhat’sgood/bad • Does it solve the problem ? • Is it a possible solution? • Canwe do it? • Shouldwe do it? • Mark what is good

  10. Problem solved • Agree on whatto be implemented • Dotvoting • Decide on a flow/new behaviorof the software • Cardsorting • Test withothercustomerstoo • Implement

  11. Recap Olderrequirementsanalysis VS. requirement’sstudio Old analysis Requirement’s studio Learning experience Morebrains = moreideas Different ppl = different views Team knowswhat’snexttoimplement Involvedcustomer • Onesidedview • Pressure on one person • Uninvolvedcustomer

More Related