Methodsa Ia woulda usea toa gathera requirementsa fora writinga aa salesa softwarea wherea thea twoa
partnersa coulda nota agreea ona whata exactlya thea softwarea shoulda do:a
1. Ia woulda doa researcha ona thea currenta systema anda business.a a Thea firsta thinga Ia woulda doa
isa understanda thea businessa missiona statementa toa understanda thea businessa goala anda
whata isa importanta toa thea business.a Next,a Ia woulda researcha toa seea whata salesa softwarea
theya area using.a Ina doinga thisa Ia woulda looka toa understanda thea prosa anda consa ofa thea
currenta systema anda whya ana upgradea isa needed.
2. Ia woulda conducta ana interviewa witha botha partnersa together.a Ia woulda starta thea interviewa
offa witha verifyinga thea businessa missiona statementa toa helpa aligna thea twoa partnersa ina
whata theya wanta thea newa softwarea toa be.a Ia woulda thena reviewa thea currenta systema witha
thema anda understanda whata theya like,a don’ta likea anda whya theya wanta aa newa program.a Ia
woulda aska eacha partnera toa takea turnsa ona whata theya wanta thea newa softwarea programa
usinga thea Moscowa method.a Thisa woulda helpa mea understanda wherea thea commona
grounda isa anda builda offa that.a Ina thea interviewa Ia woulda usea thea 5a Wsa anda thea 1H.
Projectsa facea risksa ofa failurea quitea often.a Therea area manya reasonsa toa classifya aa projecta asa
risky.a Thea twoa Ia willa highlighta area thea lacka ofa appropriatea fundinga anda stakeholdersa nota
givinga thea projecta propera support.a First,a fundinga aa projecta cana sometimesa bea extremelya
complicated.a Evena ifa aa businessa believesa theya havea fundeda aa projecta fully,a therea area manya
costsa thata cana creepa upa unexpectedly.a Onea ofa thea majora onesa area changea orders.a Fora
example,a aa companya hasa severala integrations,a buta lefta ana obscurea yeta importanta onea outa ofa
thea scopea ofa work.a Usuallya addinga thea integrationa asa aa changea ordera isa nota ana issue,a buta
mosta changea ordersa comea witha ana additionala cost.a Ina additiona toa changea orders,a anothera
situationa thata cana unexpectedlya arisea isa thea needa fora updateda hardwarea ora software.a Perhapsa
theira currenta systema runsa ona Windowsa 7,a buta thea newa builda requiresa ana upgradea toa Windowsa
10.a Generallya thata woulda bea ana easya upgrade,a buta sometimesa aa newa computera terminala willa
alsoa bea neededa toa accommodatea thea operatinga systema upgrade.a Sincea lacka ofa propera fundinga
cana deraila aa projecta Ita isa alwaysa wisea toa seta asidea additionala funding.a Ifa thea moneya isa nota
spenta duringa thea initiala stagesa ofa thea projecta ita cana bea useda fora annuala maintenancea ora
desireda upgrades.a Thea nexta riska isa thea lacka ofa propera projecta supporta bya stakeholders.a
Stakeholdersa holda aa greata deala ofa powera whena ita comesa toa thea successa ofa aa project.a Aa lota ofa
stakeholdersa area informala leadersa anda holda swaya overa others.a Ifa theya choosea nota toa supporta
thea project,a othersa willa follow.a thisa cana impacta everya parta ofa thea projecta froma buildinga toa
traininga toa implementation.a Eacha ofa thosea piecesa needa toa bea appropriatelya supporteda ina ordera
toa bea successful.a
Thea methodsa Ia woulda usea toa gathera requirementsa woulda bea interviewinga stakeholdersa anda
observation.a Makinga surea alla stakeholdersa havea somea involvementa ina thea projecta willa goa aa
longa waya toa earninga theira support.a Eacha stakeholdera shoulda havea aa voice,a sincea ana
administratora maya havea noa ideaa whata aa fronta linea usera needsa anda vicea versa.a Ina ordera toa geta
aa balanceda viewa eacha positiona shoulda bea interviewed.a Observationa isa necessarya sincea seeinga
howa someonea doesa theira joba cana capturea informationa thata wasa overlookeda ina interviews.a
Sometimesa aa usera maya doa thingsa outa ofa habita ora musclea memorya anda nota realizea therea isa aa
functionala requirementa behinda it.a Thisa isa alsoa aa helpfula waya toa verifya thea informationa
receiveda ina thea interviewsa makesa sensea anda clarifya anya gapsa ina thea information.a Softwarea
engineeringa projectsa area drivena bya businessa needs.a Therea area manya differenta risksa thata cana
arisea ina aa softwarea engineeringa project.a Thea commona risksa includea projecta scopea changes,a
technicala challenges,a schedulea anda budgeta overruns.a Ina thisa scenario,a thea scopea ofa thea
projecta posesa aa riska toa thea entirea projecta becausea thea partnersa area nota ina agreementa ofa whata
thea scopea ofa thea projecta shoulda be.a Witha thea undefineda /a fluctuatea scope,a thea projecta willa
takea longera toa completea thusa increasea ina costa fora thea projecta willa occur.a
Toa gathera informationa fora thisa retaila storea salea software,a interviewinga anda requirementa
workshopsa woulda bea appropriatea fora thisa situation.a Interviewinga stakeholdersa (storea partners,a
storea managera anda salea associates)a toa gathera informationa abouta theira needsa anda expectationsa
fora thea softwarea application.a Thisa methoda isa usefula becausea thea projecta teama cana obtaina
valuablea insightsa thata cana bea useda toa builda thea featuresa anda functionalitya thata area mosta
importanta toa thea storea fora thea application.a a Requirementa workshopsa woulda bringa thea
stakeholdersa togethera alonga witha thea projecta teama toa discussa anda identifya thea requirementsa
fora thea softwarea applicationa anda workinga towarda aa detaila information/scopea ofa thea projecta
thata woulda bea aligneda witha thea needsa ofa thea storea anda itsa customers.a Ia woulda havea toa saya thata
projecta riska managementa isa aa processa ofa managinga risksa associateda witha projects.a Ita involvesa
identifying,a assessing,a anda mitigatinga risks.a Somea ofa thea commona typesa ofa projecta riska area
projecta scopea change,a budgeta changea ora resourcea availabilitya change.a Riska managementa isa
ana importanta parta ofa projecta planninga anda executiona toa ensurea thata risksa area minimizeda asa
mucha asa possible.a Whena ita comesa toa scopea changea thea stakeholdersa maya havea differenta ideasa
comparinga toa whata youa havea fora thea project.a Ifa youa anda thea stakeholdersa can’ta comea toa ana
agreement,a thena thea projecta thata youa plana toa worka witha woulda nota bea completed.a Therefore,a
youa needa toa bea ablea toa figurea outa whata toa discussa anda howa youa anda thea stakeholdersa cana
comea toa ana agreement.a It’sa mucha easiera toa defenda decisionsa anda keepa scopea ina checka whena
you’vea documenteda anda agreeda upona projecta deliverablesa beforea worka beginsa saysa
.Knowinga whata risksa toa watcha outa fora anda howa you’lla addressa thema cana goa aa longa waya ina
easinga anxietya fora everyonea involveda ina thea project.a Twoa waysa thata Ia woulda usea toa gathera
requirementsa area documenta analysisa anda observation.a Frequentlya overlooked,a documenta
analysisa isa anothera highlya effectivea techniquea fora gatheringa requirements.a Onea ofa thea besta
waysa toa understanda whata usersa trulya needa isa toa observea thema performinga theira dailya tasks.a
Bya observinga enda usersa ina thea reala contexta ina whicha theya performa theira tasks,a you’lla gaina aa
truea understandinga ofa whata theya area upa againsta anda whata improvementsa theya needa soa theya
cana performa better.a You’lla thena bea bettera ablea toa specifya aa systema thata successfullya reinventsa
users’a processesa anda grantsa thema fara greatera productivitya anda usability,a rathera thana simplya
providinga thema ana incrementala improvement.a Handlinga requirementsa isa anothera waya ofa
categorizinga models.a Aa Predictivea Developmenta modela isa ana advancementa ofa thoughta ona thea
needsa beforea ita isa done.a Thea designa isa baseda ona thea requirementsa ofa thea systema anda isa useda
asa aa blueprinta fora thea codea toa bea written.a Sometimesa it'sa harda toa knowa whata ita needsa anda thea
materialsa toa builda it.a Moreover,a ifa thea developersa aren'ta familiara witha aa techniquea toa use,a ita isa
incompatiblea witha thea programa toa work.Ana Adaptivea Developmenta modela isa aa waya toa
changea thea goalsa ofa thea projecta duringa developmenta ifa ita isa necessary.a Thisa willa reevaluatea
thea changesa ina thea design'sa directiona whena thea outseta isa nota relevanta enough.a Ana examplea ofa
thisa isa watchinga aa detectivea show.a Ita hasa aa detectivea tryinga toa finda thea killer,a he/shea hasa thea
necessarya tools,a anda eacha timea he/shea findsa aa clue,a thea directiona becomesa updated.
Aa Sashimia Developmenta modela alsoa knowna asa thea SashimIa Waterfalla phasea isa justa likea thea
Waterfalla modela buta ita cana overlapa thea steps.a Therea area threea typesa ofa prototypes;a
throwaway,a evolutionary,a anda incrementala type.a Aa throwawaya isa aa studya ofa thea systema beinga
tosseda outa oncea ita isa gathereda anda thena thea developera writesa thea codea froma thea beginninga
baseda ona thata system.a Ana evolutionarya prototypea isa aa typea thata describesa thea application'sa
features.a Duringa thea process,a refinementa ofa thea featuresa isa established,a newa additionsa area
replaced,a anda thea finisheda appa isa baseda offa ofa thosea newa features.a Ana incrementala isa creatinga
aa collectiona ofa othera typesa froma thea characteristicsa ofa theira finisheda version,a aa combinationa
ofa thea applications.a Ita isa easiera fora developersa toa worka ona individuala piecesa froma separatea
prototypes.a Feature-Drivena Developmenta isa botha ana iterativea anda incrementala modela wherea
largea teamsa usea risk,a thea valuea ofa customers,a ora thea wastea toa guidea theira developmenta
processa ata aa highera level.a Thea featuresa listeda ina thisa builda area popularizeda anda becomea
added.a Ita goesa througha fivea phases;a developa aa model,a builda aa featurea list,a plana bya feature,a
designa bya feature,a anda thena builda bya feature.a Twoa partnersa whicha area unaligneda willa deraila
thea project,a disappointa thea customer,a anda ruina theira reputations.a Thea partnersa shoulda bea ablea
toa communicatea anda collaboratea effectively.a Thesea risksa cana bea unavoidablea whena thea twoa
partnersa havea differenta visions,a levelsa ofa experience,a expertise,a anda technicala skills.a Onea ofa
thea partnersa willa dominatea thea othera partnera anda willa hindera collaborationa becausea theya willa
havea aa differenta understandinga ofa thea systema requirements,a tasks,a anda processes.a Unaligneda
goalsa willa bea anothera riska fora thea project.a Botha partnersa shoulda havea cleara objectivesa fora thea
projecta anda thea deliverablesa ata thea enda ofa thea project.
Onea partnera maya havea highera technicala knowledgea thana thea othera partner.a Thea morea
experienceda partnera willa leada ina thea developmenta process,a anda thisa mighta inhibita thea learninga
experiencea ofa thea othera partner.a Toa avoida thesea typesa ofa risks,a botha partnersa shoulda havea
similara levelsa ofa skillsa anda experiencea soa theya cana collaboratea effectivelya ona thea project.Aa
lacka ofa resourcesa cana causea significanta problemsa fora thea softwarea project.a Resourcesa includea
thea time,a budget,a anda resourcesa thata area requireda toa completea thea project.a Ifa onea ora botha
partnersa lacka thea requireda resourcesa toa completea thea project,a theya willa havea toa makea difficulta
sacrificesa ina ordera toa completea thea projecta ona time.Twoa methodsa I'da usea toa gathera
requirementsa fora thisa projecta woulda bea interviewsa ora surveys.a Interviewsa coulda bea donea witha
keya stakeholdersa toa geta thea requirementsa froma differenta perspectives.a Aa surveya coulda bea senta
toa customersa toa learna morea abouta thea requirementsa fora thisa project.a Ia woulda usea aa
combinationa ofa botha methodsa toa collecta informationa fora mya softwarea project.a Ia woulda alsoa
usea workshopsa toa gathera morea informationa froma thesea keya stakeholdersa anda customers.a Ina
thisa situationa therea area twoa partnersa thata wanta thisa salesa software,a buta theya area unablea toa
agreea ona whata ita shoulda do.a Thata ina itselfa isa aa riska fora thea project.a Onea ofa thea biggesta risksa toa
softwarea developmenta isa thea purposea anda needa nota beinga wella defined.a Bea ablea toa agreea ona
whata thea programa shoulda doa fallsa undera thea purposea anda needa categorya anda thea stakeholdera
risk.a Witha thesea partnersa nota agreeinga theya won'ta bea ablea toa executea thea projecta wisely.a Theya
becomea stakeholdersa ina thea projecta becausea theya havea thea mosta interesta ina thea projecta
succeedinga anda witha thema disagreeinga ita succeedinga willa becomea difficult.a Ia woulda starta bya
doinga stakeholdera engagementa becausea gettinga thea partnersa toa agreea ona whata thea softwarea
shoulda isa importanta beforea anya planninga ora developmenta cana bea started.a Even,a ifa it'sa justa aa
verya basica anda simplea ideaa toa starta with.Thisa cana bea achieveda ina manya differenta waysa bya
brainstorming,a questionnaires,a surveys,a ora presentationsa ofa variousa waysa thata thea softwarea
coulda work.a Oncea wea geta thema toa agreea thena whena cana starta documentinga requirements.a Thea
requirea area importanta becausea theya cana definea thea variousa featuresa thata willa bea necessary,a
howa manya usersa willa ita needa toa supporta ata aa givena time,a anda evena wherea anda howa theya wanta
toa storea customera information.a Ia woulda generallya doa morea thana whata isa describeda here,a buta Ia
thinka thisa isa aa gooda placea toa start.a Fora thisa weeksa discussiona topica ofa twoa smalla sportsa
equipmenta storea partnersa nota agreeinga ona whata thea proposeda salesa softwarea shoulda looka likea
ora do,a I'da runa awaya froma thisa project!a Justa kidding,a buta whata aa mess.a Ia wondera howa theira
bricka anda mortara storea isa functioning,a ora nota functioning.a Onea partnera musta bea carryinga thea
loada toa avoida conflict.a Anyway,a backa toa thea question.a Onea reasona thisa projecta ifa classifieda asa
aa riskya projecta woulda bea bya definitiona ofa aa Waterfalla modela havinga cleara anda wella defineda
objectives.a Ifa thea modela needsa toa completea onea stepa beforea movinga toa thea nexta step,a theya
woulda nevera geta pasta thea firsta stepa ofa gatheringa whata thea softwarea shoulda looka likea anda do.a
Higha levela designa willa nevera happena ifa thea twoa partnersa cana nota givea youa aa cleara picturea ofa
whata theya want.a Ina thea reala worlda woulda ita bea possiblea toa givea thema aa examplea ofa pasta
workinga software'sa toa agreea upon?a Anothera reasona thisa woulda bea aa riskya projecta woulda bea
thea possiblea conflicta asa thea projecta continuesa ora nearsa completiona anda thea partnersa seea ana
examplea ofa theira newa salesa softwarea anda nota likinga whata theya see.So,a twoa methodsa Ia woulda
usea toa pusha thisa projecta alonga woulda bea onea ona one,a ora facea toa facea interactionsa likea
brainstorminga ora groupa discussion.a Thisa woulda givea alla partiesa somea sencea ofa urgencya toa geta
ona thea samea page.
