Scribd
Upload
26 views2 pages

ONE 7. Fail To of Find Poor To It's To To For: Process

The document discusses best practices for requirements engineering in agile software development. It suggests actively involving stakeholders, using simple models, adopting stakeholder terminology, taking a breadth-first approach, allowing requirements to be refined over time, and developing prototypes for stakeholder review.

Uploaded by

K
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
26 views2 pages

ONE 7. Fail To of Find Poor To It's To To For: Process

The document discusses best practices for requirements engineering in agile software development. It suggests actively involving stakeholders, using simple models, adopting stakeholder terminology, taking a breadth-first approach, allowing requirements to be refined over time, and developing prototypes for stakeholder review.

Uploaded by

K
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

PART ONE THE SOFTWARE PROCESS

more detail in Chapter 7. Teams that fail to spend a reasonable amount of time on
this task will find that their project contains expensive rework, cost overruns, poor
product quality, late delivery times, dissatisfied customefs, and poor team morale'
Requirements engineering cannot be neglected, nor can it be allowed to iterate end-
lessly before proceeding to product construction.
It's reasonable to ask what best practices should be followed to achieve thorough
and agile requirements engineering. Scott Ambler [Amb12] suggests several best prac-
tices for agile requirements definition:
L. Encourage active stakeholder participation by matching their availability and
valuing their input.
2. Use simple models (e.g., Post-it notes, fast sketches, user stories) to reduce
barriers to participation.
3. Take time to explain your requirement representation techniques before using
, them.
4. Adopt stakeholder terminology, and avoid technical jargon whenever possible.
5. Use a breadth-first approach to get the big picture of the project done before , ,r{

getting bogged down in details. *l

6. Allow the development team to refine (with stakeholder input) requirement


.,.]
details 'Just in time" as user stories are scheduled to be implemented' ,
7. Treat the list of features to be implemented like a prioritized list, and imple- l,: i ' ':rl
ment the most important user stories first.
8. Collaborate closely with your stakeholders and only document requirements at
a level that is useful to all when creating the next prototype.
9. Question the need to maintaip models and documents that will not be referred
to in the future.
10. Make sure you have management support to ensure stakeholder and resource
availability during requirements definition.
It is important to recognize two realities: (1) it is impossible for stakeholders to
describe an entire system before seeing the working software, and (2) it is difficult for
stakeholders to describe quality requirements needed for the software before seeing it
in action. Developers must recognizethat requirements will be added and refined as
the software increments are created. Capturing stakeholders' descriptions about what
the system needs to do in their own words in a user story is a good place to begin.
If you can get stakeholders to define acceptance criteria for each user story, your
team is off to a great start. It is likely that stakeholders will need to see a user story
coded and running to know whether it has been implemented correctly or not. There-
fore, requirements definition needs to be done iteratively and include the development
of prototypes for stakeholder review.
Prototypes are tangible realizations of project plans that can be easily referenced
by stakeholders when trying to describe desired changes. Stakeholders are motivated
to discuss requirements changes in more concrete terms, which improves communica-
tion. It's important to recognize that prototypes allow developers to focus on short-
KeY
u.\dentrtY 'ssues

ts
/ ."t"
o 6
eA
ol
\o
\o
bt
@t \+
\J
UI \(D

lq
I

o_l
,s
cu\
o\
o\
O\
o\ li s
,t- I
'qouYeuoc
S r{a y AllrraQ\t

luatudoya,rap
ad.{1o1o.rd
senllca[q6 ro; u8gsap
ornllolr r..{f,rV {11uep1'L IBrnlral!qrrY

'slcnpord eJE^uJos xeldruoc ro e8rel ;o lueudole,rep


eql Sur8uuutu o1fe1 sr socroqc errucelrqcre pue sluerueJrnbe; go Supuulsrepun .(pue
'[ftteS] sen8eeyloc rerl pue oruolleg o1 Suproccy 'sluerueJcur lcnpord 01 polecolle
eq 01 peeu IIr,^a suorsroep IeJnlcelqcJe 'euJrl ur lurod eruos le 'g'7 e-rn8rg ur u1(oqs
sV 'peugep eru slueruernbeJ se operu oq uogo 1sruu suorsrcep uBISep ,ftuup41erd 1nq
'91 ;e1duq3 ur pessncsrp ere u8rsep Iern]Jelrqcre pr1os e dole,rep o1 pennber suorsrcep erLL

'[EtduX] serrnosel pue erurl Surtse,tr 'peprecsrp aq lsnru 1eq1 sed.{to1


-ord ur llnser,(eru poolsJepun l[e^\ eJB slueule;rnber lpJnloelrqcJt eJBAuJos eql eJo.+eq
sed,(1o1ord Surleer leql )sr.r eqt oslu sr areqJ 'erurl lsrrJ eqt lq8r.r s8urql Sur11e8 uo
pesnco.+ tou ere sreploqolels ;r slueruelnber eqt Jo {l}lpelo,t eqt eseercur ,{eur sed.,(l
e,,,an <.'^,-I.r,ara-.r.,,--h a.- nr .^rIf,rnrn.rl

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy