Page 291 - Software and Systems Requirements Engineering in Practice

E
T
A
P
R

2
ç

N
S
H
I
E
#
H
U
Q
M
E
O
P
N
4
E
T
ç
L
I
D
A
P
ç
V
E
$
E
C
ç ç # H A P T E R ç ç ç 2 A P I D ç $ E V E L O P M E N T ç 4E C H N I Q U E S ç ç
EXTENSIVE DOCUMENTATION ABOUT HOW A PROTOTYPE IS
IMPLEMENTED IS UNNECESSARY $EVELOPMENT OF EXECUTABLE
PROTOTYPES IS WASTED EFFORT IF SIMPLE STORYBOARDS WILL SUFFICE
!NIMATED WEB OR SCRIPTING APPLICATIONS ARE OFTEN EASIER
MEANS THAN THE TARGET TECHNOLOGIES TO DEVELOP THE PROTOTYPES
#REATION OF REUSABLE STRUCTURES IS WASTED EFFORT IF LIMITED
REPLICATION IS SUFFICIENT #ONVERSELY WHEN PROTOTYPING IS
COMBINED WITH FEASIBILITY STUDIES OR PRODUCT DEVELOPMENT
ACTIVITIES REUSING SOME PROTOTYPING ARTIFACTS FOR DEVELOPMENT
MAY BE APPROPRIATE
v !CCELERATE LEARNING 1UICK PROTOTYPE TURNAROUND AND
TRANSPARENCY HELPS THE STAKEHOLDERS 2%S AND DEVELOPERS
LEARN ABOUT THE PRODUCT AND ITS IMPLEMENTATION .EW
TECHNOLOGIES AND TOOLS CAN ALSO BE LEARNED AS NEEDED TO
IMPLEMENT THE PROTOTYPES
v $ECIDE AS EARLY AS POSSIBLE -AKE CERTAIN THAT PROTOTYPING
IS CONCENTRATED ON A CONCRETE EXAMPLE $ECISIONS THAT FOCUS
THE PROTOTYPING PROGRESS CAN THUS BE MADE INCREMENTALLY
POSSIBLY ON ONE IMPORTANT FEATURE AT A TIME )F THE
IMPLEMENTATION OF A PARTICULAR FEATURE SOLUTION FAILS BACKTRACK
AS QUICKLY AS POSSIBLE 7HEN PROTOTYPING WE HAVE THE
OPPORTUNITY TO IMPLEMENT FEATURES IN MULTIPLE WAYS IN ORDER
TO VERIFY WHICH IS BETTER
v $ELIVER AS FAST AS POSSIBLE $ON T WAIT FOR CUSTOMERS OR
USERS TO ASK FOR RESULTS BUT PROACTIVELY ELICIT THEIR FEEDBACK
BASED ON ONE OR MULTIPLE PROTOTYPE VERSIONS $ELIVER
INTERMEDIATE RESULTS AS SOON AS A SUFFICIENT DIFFERENCE IS VISIBLE
AND DON T WAIT TO IMPLEMENT A COMPLETE SOLUTION 0ROTOTYPE
DEVELOPMENT ITERATIONS SHOULD BE VERY SHORT E G MUCH
SHORTER THAN THE ONE MONTH ITERATIONS TYPICALLY USED FOR
PRODUCT DEVELOPMENT WITH 3CRUM
v %MPOWER THE TEAM $ON T SPEND TIME DEFINING FORMAL ROLES
OR PROCESSES PREDEFINED REPRESENTATIONS OR DOCUMENT
FORMATS +EEP THE PROTOTYPING TEAM AND KEY STAKEHOLDERS
SMALL IN NUMBER AND COLLOCATE EVERYONE IN ONE WORK AREA IF
POSSIBLE !LLOW THE TEAM TO CUSTOMIZE THE INTERACTIONS AND
ARTIFACTS OR REUSE STANDARD MODELS OR SOLUTIONS FOR THE PROBLEM
AT HAND 3TAKEHOLDERS HAVE VERY LITTLE DIRECT CONTROL OVER THE
PROTOTYPING PROCESS AND PROGRESS "UT IF THEY HAVE CLEAR AND
FREQUENT TRANSPARENCY INTO THE PROTOTYPING PROGRESS THEY
CAN EVALUATE WHETHER PROGRESS IS BEING MADE 3TAKEHOLDERS
CAN ALSO DETERMINE IF PROTOTYPING SPECIFIC ASPECTS OF THE
SYSTEM REQUIREMENTS IS VALUABLE OR WHETHER THE EFFORTS
SHOULD BE DIRECTED ELSEWHERE TO OTHER FEATURES 3TAFF THE TEAM
WITH EXPERIENCED CROSS FUNCTIONAL EXPERTS AND ENCOURAGE
COLLABORATION AT THE LOWEST GRANULARITY LEVEL