lecture 5 & 6 step wise

8/17/2019 Lecture 5 & 6 Step Wise

1/24

Step Wise: An

approach to plansoftware projectsLecture 5 & 6


2/24

‘Step Wise’ - an overview0.Select project

. !"entif#

project o$jectives

%. !"entif# project

infrastructure

. Anal#seproject

characteristics

'. !"entif# pro"ucts

an" activities

5. (sti)ate e*ort

for activit#

+. ,eview pu$licie

plan

6. !"entif# activit#

ris/s

. Allocate

resources

1. (2ecute plan

0. Lower level

plannin3

,eview

Lowerlevel"etail

4or each activit#


3/24

A project scenario: ri3ht)outholle3e 7a#roll

• olle3e currentl# has pa#roll processin3 carrie"out $# a services co)pan#

• 8his is ver# e2pensive an" "oes not allow "etaile"anal#sis of personnel "ata to $e carrie" out

• 9ecision )a"e to $rin3 pa#roll‘in-house’$#acuirin3 an‘o*-the-shelf’ application

• 8he use of the o*-the-shelf s#ste) will reuire anew; internal; pa#roll o


4/24

Step esta$lish projectscope an" o$jectives

• !"entif# o$jectives an" )easures of e*ectiveness

• ‘how "o we /now if we have succee"e"=’

• (sta$lish a project authorit#

• ‘who is the $oss=’

• !"entif# all sta/ehol"ers in the project an" theirinterests

• ‘who will $e a*ecte"involve" in the project=’

• >o"if# o$jectives in the li3ht of sta/ehol"er

anal#sis• ‘"o we nee" to "o thin3s to win over sta/ehol"ers=’

• (sta$lish )etho"s of co))unication with allparties

• ‘how "o we /eep in contact=’


5/24

5

ac/ to the scenario

• ?$jectives

• 8o i)ple)ent the new application on ti)e an" within$u"3et

• 8o i)ple)ent the new software application with the

fewest possi$le software errors that )i3ht lea" tooperational failures

• 8o "esi3n a user frien"l# s#ste)

• 8o pro"uce full "ocu)entation of the new s#ste)

• Sta/ehol"ers

• 4or e2a)ple; personnel o


6/24

Step 2 Establish project

infrastructure• Establish link between project and any strategic plan

• ‘why did they want the project?’

• Hardware Software standards

• Prograe !anageent

• How will different systes integrate?

• "dentify installation standards and procedures

• ‘what standards do we ha#e to follow?’

• "dentify project tea organi$ation

• %ho does what?• How teas will work?


7/24

Step Anal#sis of projectcharacteristics• 9istin3uish the project as either o$jective or pro"uct-

$ase".

• !s there )ore than one wa# of achievin3 success=

• Anal#se other project characteristics @inclu"in3 ualit#

$ase" ones• what is "i*erent a$out this project=

• !"entif# hi3h level project ris/s

• ‘what coul" 3o wron3=’

• ‘what can we "o to stop it=’

• 8a/e into account user reuire)ents concernin3i)ple)entation

• Select 3eneral life c#cle approach

• waterfall= !ncre)ents= 7rotot#pes=

• ,eview overall resource esti)ates

• ‘"oes all this increase the cost=’


8/24

ac/ to the scenario• ?$jectives vs. pro"ucts

• An o$jective-$ase" approach has $een a"opte"

• So)e ris/s

• 8here )a# not $e an o*-the-shelf pac/a3e that caters forthe wa# pa#roll is processe" at ri3ht)outh olle3e

• Answer=

• ri3ette "eci"es to o$tain "etails of how )ain can"i"atepac/a3es wor/ as soon as possi$leB also a3ree)ent that ifnecessar# processes will $e chan3e" to Ct in with news#ste).


9/24

Step & "dentify project

products and acti#ities• &'( "dentify and describe project products ) ‘what do we ha#e to

produce?’


10/24

Step & "dentify project

products and acti#ities• *rightouth


11/24

Products

• +he result of an acti#ity

• ,ould be -aong other things.

• physical thing -‘installed pc’./

• a docuent -‘logical data structure’.

• a person -‘trained user’.

• a new #ersion of an old product -‘updated software’.

• +he following are 01+ norally products

• acti#ities -e'g' ‘training’.

• e#ents -e'g' ‘inter#iews copleted’.• resources and actors -e'g' ‘software de#eloper’. ) ay be

e3ceptions to this

• Products ,40 *E deliverable or intermediate


12/24

Step & continued• &'2 docuent generic product flows


13/24

1 3

Step & continued• *rightouth 5 "n#itation to +ender


14/24

Step &'6 7ecogni$e product instances

• +he P*S and P89 will probably ha#e identified generic

products e'g' ‘software odules’

• "t ight be possible to identify specific instances e'g'

‘odule 4’/ ‘odule *’ :

• *ut in any cases this will ha#e to be left to later/ oredetailed/ planning


15/24

&'&' Produce ideal acti#ity

network• "dentify the acti#ities needed to create each product in

the P89

• !ore than one acti#ity ight be needed to create a

single product

• Hint "dentify acti#ities by #erb ; noun but a#oid‘produce:’ -too #ague.

• 9raw up acti#ity network


16/24

4n ‘ideal’ acti#ity


17/24

4n ‘ideal’ acti#ity


18/24

Step &'< 4dd check)points if needed9esi3n

)o"ule A

9esi3n)o"ule

9esi3ns#ste)

9esi3n

)o"ule

o"e)o"ule A

o"e)o"ule

o"e

)o"ule

8ests#ste)

9esi3n)o"ule A

9esi3n)o"ule

9esi3ns#ste)

9esi3n

)o"ule

o"e)o"ule A

o"e)o"ule

o"e

)o"ule

8ests#ste)

hec/-point

put in a

chec/point


19/24

Step


20/24

Step = "dentify acti#ity risks• ='('"dentify and >uantify risks for acti#ities

• daage if risk occurs -easure in tie lost or oney.

• likelihood if risk occurring

• ='2' Plan risk reduction and contingency easures

• risk reduction acti#ity to stop risk occurring

• contingency action if risk does occur • ='6 4djust o#erall plans and estiates to take account of

risks

• e'g' add new acti#ities which reduce risks associated with

other acti#ities e'g' training/ pilot trials/ inforation gathering


21/24

Step 4llocate resources

• '( "dentify and allocate resources to acti#ities

• '2 7e#ise plans and estiates to take into account

resource constraints

• e'g' staff not being a#ailable until a later date

• non)project acti#ities


22/24

Dantt hart


23/24

Step @ 7e#iewApublicise plan

• @'( 7e#iew >uality aspects of project plan

• @'2 9ocuent plan and obtain agreeent


24/24

Bey points

• Establish your objecti#es• +hink about the characteristics of the project

• 9isco#erAset up the infrastructure to support the project-including standards.

• "dentify products to be created and the activities that will

create the• 4llocate resources

• Set up >uality processes

lecture 5 & 6 step wise

Documents