SofLware ro[ecL ManagemenL

Software project management is the art and

science of planning and leading software projects.
It is a sub-discipline of project management in
which software projects are planned, monitored
and controlled.
ro[ecL
W A Lask or scheme LhaL requlres a large amounL of
Llme efforL and plannlng Lo compleLe ocotto
A planned underLaklng
A speclflc plan or deslgn
W A ptoject ls o tempototy eoJeovot ooJettokeo to
cteote o oolpoe ptoJoct ot setvlce
W rogresslvely elaboraLed
WlLh repeLlLlve elemenLs
obs versus ro[ecLs
'Iobs' repet|t|on of very we||def|ned and we|| understood
tasks w|th very ||tt|e uncerta|nty
'Lxp|orat|on' eg f|nd|ng a cure for cancer the outcome |s
very uncerta|n
'ro[ects' |n the m|dd|e!
haracter|st|cs of pro[ects
A Lask ls more 'pro[ecLllke' lf lL ls
W -onrouLlne
W lanned
W Almlng aL a speclflc LargeL
W ro[ecL has predeLermlned Llme span
W Work carrled ouL for a cusLomer
W lnvolvlng several speclallsms
W Made up of several dlfferenL phases
W ConsLralned by Llme and resources
W Large and/or complex
lf we apply Lhese facLors Lo a Lask lL wlll become more
dlfflculL
SofLware pro[ecLs versus CLher
pro[ecLs
W lnvlslblllLy
W ComplexlLy
W ConformlLy
W llexlblllLy
make sofLware more problemaLlc Lo bulld Lhan oLher englneered arLefacLs
AcLlvlLles 8y SM
1hese are Lhree successlve process LhaL brlng a new sysLem lnLo belng
W leaslblllLy sLudy ls pro[ecL Lechnlcally feaslble
and worLhwhlle from a buslness polnL of vlew?
W lannlng Cnly done lf pro[ecL ls feaslble
W LxecuLlon lmplemenL plan buL plan may be
changed as we go along
1hese are Lhree successlve process LhaL brlng a new
sysLem lnLo belng
lSC 12207 SuLC ulagram showlng AcLlvlLles
equ|rements ana|ys|s
equlremenLs ellclLaLlon whaL does Lhe cllenL
need?
Analysls converLlng 'cusLomerfaclng'
requlremenLs lnLo equlvalenLs LhaL developers
can undersLand
equlremenLs wlll cover
W luncLlons
W CuallLy
W esource consLralnLs le cosLs
9
lSC 12207 llfecycle
W ArchlLecLure deslgn
8ased on system tepoltemeots
ueflnes componenLs of sysLem hardware
sofLware organlzaLlonal
oftwote tepoltemeots wlll come ouL of Lhls
W Code and LesL
Cf lndlvldual componenLs
W lnLegraLlon
uLLlng Lhe componenLs LogeLher
10
lSC 12207 llfecycle
W CuallflcaLlon LesLlng
1esLlng Lhe system %noL [usL Lhe softwote)
W lnsLallaLlon
1he process of maklng Lhe sysLem operaLlonal
lncludes seLLlng up sLandlng daLa seLLlng
sysLem parameLers lnsLalllng on operaLlonal
hardware plaLforms user Lralnlng eLc
W AccepLance supporL
lncludlng malnLenance and enhancemenL
11
lSC12207 conLlnued
ManagemenL AcLlvlLles
W lannlng decldlng whaL ls Lo be done
W Crganlzlng maklng arrangemenLs
W SLafflng selecLlng rlghL people for Lhe [ob
W ulrecLlng glvlng lnsLrucLlons
W MonlLorlng checklng on progress
W ConLrolllng Laklng acLlon Lo remedy holdups
W lnnovaLlng comlng up wlLh new soluLlons
W epresenLlng llalslng wlLh cllenLs developers
suppllers sLake holders
SeLLlng ob[ecLlves
W Answerlng Lhe quesLlon 'Jot Jo we ove to
Jo to ove o soccess?
W -eed for a ptoject oototlty
SeLs Lhe pro[ecL scope
AllocaLes/approves cosLs
W Could be one person or a group
ro[ecL 8oard
ro[ecL ManagemenL 8oard
Cb[ecLlves should be SMA1
speclflc LhaL ls concreLe and welldeflned
, measurable LhaL ls saLlsfacLlon of Lhe
ob[ecLlve can be ob[ecLlvely [udged
achlevable LhaL ls lL ls wlLhln Lhe power of Lhe
lndlvldual or group concerned Lo meeL Lhe LargeL
relevanL Lhe ob[ecLlve musL relevanL Lo Lrue
purpose of Lhe pro[ecL
@ Llme consLralned Lhere ls deflned polnL ln Llme by
whlch Lhe ob[ecLlve should be achleved
oals/subob[ecLlves
1hese are sLeps along Lhe way Lo achlevlng Lhe
ob[ecLlve lnformally Lhese can be deflned by
compleLlng Lhe senLence
b[ect|ve k w||| be ach|eved
II the fo||ow|ng goa|s are a|| ach|eved

etc
conLlnued
CfLen a goal can be allocaLed Lo an lndlvldual
lndlvldual may have Lhe capablllLy of achlevlng goal
buL noL Lhe ob[ecLlve on Lhelr own eg
jectlve user saLlsfacLlon wlLh sofLware producL
Aoolyst qool accuraLe requlremenLs
uevelopet qool sofLware LhaL ls rellable
Measures of effecLlveness
Pow do we know LhaL Lhe goal or ob[ecLlve has been
achleved?
8y a pracLlcal LesL LhaL can be ob[ecLlvely assessed
eg for user saLlsfacLlon wlLh sofLware producL
W epeaL buslness Lhey buy furLher producLs from us
W -umber of complalnLs lf low eLc
lan MeLhods
W A Method relates to a type oI activity in general.
W A plan Ior an activity must be based on some idea oI a method
oI work. Plan takes that and converts it to real activities so that
Ior each activity we identiIy:
W start and end dates
W What tools and materials will be used
Example: II you are given some soItware to test , even though you
don`t know anything about soItware but you do:
W Analysis
W Devise and write test cases
W Create test script and expected results Ior each test case
W Compare actual and expected results Ior each test case
MeLhodologles
W roups of meLhods or Lechnlques are ofLen
referred Lo as meLhodologles
W 1he ouLpuL from one meLhod mlghL be lnpuL
Lo anoLher
W Lxample Cb[ecL orlenLed deslgn ls a
meLhodology as lL ls made up of several
componenL meLhods
roblems wlLh sofLware pro[ecLs
lrom Managers olnL of vlew
W oor esLlmaLes and plans
W Lack of quallLy sLandards and measures
W Lack of guldance abouL maklng organlzaLlonal
declslons
W Lack of Lechnlques Lo make progress vlslble
W oor role deflnlLlon
W lncorrecL success crlLerla
Case sLudy
SLaff olnL of vlew
1hls shows a llsL of Lhe problems ldenLlfled by a
number of compuLlng and lS sLudenLs who
[usL compleLed years lndusLrlal Lralnlng
W lnadequaLe speclflcaLlon of work
W ManagemenL lgnorance of lC1
W Lack of knowledge of appllcaLlon area
W Lack of sLandards
W Lack of up Lo daLe documenLaLlon
W recedlng acLlvlLles noL compleLed on Llme
W Lack of communlcaLlon beLween users and
Lechnlclans
W Lack of communlcaLlon leadlng Lo dupllcaLlon
of work
W Lack of commlLmenL
W -arrow scope of Lechnlcal experLlse
W Changlng sofLware envlronmenL
W uead llne pressure
W Lack of quallLy conLrol
W emoLe managemenL
W Lack of Lralnlng
W lsk reducLlon or opLlmlzaLlon lnvolves
reduclng Lhe severlLy of Lhe loss or Lhe llkellhood
of Lhe loss from occurrlng
lor example sprlnklers are deslgned Lo puL ouL
a flre Lo reduce Lhe rlsk of loss by flre 1hls
meLhod may cause a greaLer loss by waLer
damage and Lherefore may noL be sulLable
W 8y an offshore drllllng conLracLor effecLlvely
applylng PSL ManagemenL ln lLs organlzaLlon lL
can opLlmlze rlsk Lo achleve levels of resldual rlsk
LhaL are Lolerable
#isk #eduction
W Modern sofLware developmenL
meLhodologles reduce rlsk by developlng and
dellverlng sofLware lncremenLally Larly
meLhodologles suffered from Lhe facL LhaL
Lhey only dellvered sofLware ln Lhe flnal phase
of developmenL any problems encounLered ln
earller phases meanL cosLly rework and ofLen
[eopardlzed Lhe whole pro[ecL 8y developlng
ln lLeraLlons sofLware pro[ecLs can llmlL efforL
wasLed Lo a slngle lLeraLlon
W CuLsourclng could be an example of rlsk
reducLlon lf Lhe ouLsourcer can demonsLraLe
hlgher capablllLy aL managlng or reduclng rlsks
lor example a company may ouLsource only lLs
sofLware developmenL Lhe manufacLurlng of
hard goods or cusLomer supporL needs Lo
anoLher company whlle handllng Lhe buslness
managemenL lLself 1hls way Lhe company can
concenLraLe more on buslness developmenL
wlLhouL havlng Lo worry as much abouL Lhe
manufacLurlng process managlng Lhe
developmenL Leam or flndlng a physlcal locaLlon
for a call cenLer
1hese are people who have a sLake or lnLeresL ln
Lhe pro[ecL
ln general Lhey could be osets/clleots or
Jevelopets/lmplemeotets
1hey could be
< WlLhln Lhe pro[ecL Leam
< CuLslde Lhe pro[ecL Leam buL wlLhln Lhe same
organlzaLlon
< CuLslde boLh Lhe pro[ecL Leam and Lhe
organlzaLlon
27
SLakeholders
ManagemenL conLrol
28
uaLa Lhe raw deLalls
eg # Jocomeots ptocesseJ ot locotloo \
lnformaLlon Lhe daLa ls processed Lo produce
someLhlng LhaL ls meanlngful and useful
eq #ptoJoctlvlty ls 1 Jocomeots o Joy
Comparlson wlLh ob[ecLlves/goals
eq we wlll oot meet totqet of ptocessloq oll Jocomeots y J1
st
Motc
conLlnued
29
ManagemenL conLrol
Modelllng worklng ouL Lhe probable
ouLcomes of varlous declslons
eg lf we employ Lwo more sLaff aL locaLlon x how
qulckly can we geL Lhe documenLs processed?
lmplemenLaLlon carrylng ouL Lhe remedlal
acLlons LhaL have been declded upon
30
ManagemenL conLrol conLlnued
SLep wlse ro[ecL lannlng
SLepwlse meLhod ls a framework for pro[ecL
plannlng noL for monlLorlng and conLrol
Ma[or prlnclple of pro[ecL plannlng ls Lo plan ln
ouLllne flrsL and Lhen ln more deLall as Lhe Llme
Lo carry ouL an acLlvlLy approaches
W racLlcallLy
Lrles Lo answer Lhe quesLlon 'whaL do l do
now?'
W ScalablllLy
useful for small pro[ecL as well as large
W ange of appllcaLlon
32
'SLep Wlse' asplraLlons
AcLlvlLles wlLhln sLep
W SelecL pro[ecL
W ldenLlfy pro[ecL scope and ob[ecLlves
W ldenLlfy pro[ecL lnfrasLrucLure
W Analyse pro[ecL characLerlsLlcs
W ldenLlfy pro[ecL producLs and acLlvlLles
W LsLlmaLe efforL for each acLlvlLy
W ldenLlfy acLlvlLy rlsks
W AllocaLe resources
W evlew plan
W LxecuLe plan
34
'SLep Wlse' an overvlew
0SelecL
pro[ecL
1 ldenLlfy
pro[ecL ob[ecLlves
2 ldenLlfy pro[ecL
lnfrasLrucLure
3 Analyse
pro[ecL
characLerlsLlcs
4 ldenLlfy producLs
and acLlvlLles
3 LsLlmaLe efforL
for acLlvlLy
8 evlew/ publlclze
plan
6 ldenLlfy acLlvlLy
rlsks
7 AllocaLe
resources
9 LxecuLe plan
10 Lower level
plannlng
evlew
Lower
level
deLall
acLlvlLy
lor each
W lL ls called 0 sLep
lL ls ouLslde maln pro[ecL plannlng process
W Pere we do feaslblllLy sLudy
W rlorlLy of pro[ecLs
W MerlLs of pro[ecL
SLep 0SelecL ro[ecL
33
W ro[ecL Scope
W ldenLlfy Lhe ob[ecLlves
W ueflnlng goals
SLep 1
36
< 11 ldenLlfy ob[ecLlves and measures of effecLlveness
'how do we know lf we have succeeded?'
< 12 LsLabllsh a pro[ecL auLhorlLy
'who ls Lhe boss?'
ro[ecL sLeerlng commlLLee
SeLLlng monlLorlng and modlfylng ob[ecLlve
< 13 ldenLlfy all sLakeholders ln Lhe pro[ecL and Lhelr
lnLeresLs
'who wlll be affecLed/lnvolved ln Lhe pro[ecL?'
37
SLep 1 esLabllsh pro[ecL scope and
ob[ecLlves
W 14 Modlfy ob[ecLlves ln Lhe llghL of
sLakeholder analysls
'do we need Lo do Lhlngs Lo wln over
sLakeholders?'
Add new feaLures for sLakeholder's beneflL
W urawback ls slze may lncrease
W 13 LsLabllsh meLhods of communlcaLlon wlLh
all parLles
'how do we keep ln conLacL?'
38
SLep 1 conLlnued
W ro[ecLs are rarely carrled ln vacuum
W 21 LsLabllsh llnk beLween pro[ecL and any
sLraLeglc plan
ldenLlfy and prlorlLlze Lhe pro[ecLs
LsLabllsh framework for pro[ecL
'why dld Lhey wanL Lhe pro[ecL?'
WhaL h/w and s/w parL needed
39
SLep 2 LsLabllsh pro[ecL
lnfrasLrucLure
W 22 ldenLlfy lnsLallaLlon sLandards and
procedures
WhaL are Lhe developmenL procedures?
'whaL sLandards do we have Lo follow?'
Change conLrol and managemenL
W 1o ensure LhaL requlremenLs are lmplemenLed ln safe
and orderly manner
CuallLy sLandards
W LsLabllsh quallLy checks aL each phase of SuLC
SLep 2 LsLabllsh pro[ecL
lnfrasLrucLure%ConL)
40
W 3 Ident|fy pro[ect team organ|zat|on
ldenLlfy your requlremenL of Leam
Choose besL people
'where do l flL ln?'
ulvlde Lhe acLlvlLles
CreaLe groups
1here should be a pro[ecL leader
SLep 2 LsLabllsh pro[ecL
lnfrasLrucLure%ConL)
41
W 31 ulsLlngulsh Lhe pro[ecL as elLher ob[ecLlve
or producLbased
Cb[ecL v/s roducL
ro[ecL can be dlsLlngulshed by Lhelr alm wheLher
lL ls Lo produce a producL or Lo meeL cerLaln
ob[ecLlve
ls Lhere more Lhan one way of achlevlng
success?
MosLly ln earller sLage pro[ecLs are ob[ecLlve and ln
laLer sLage lL become producL drlven
42
SLep 3 Analysls of pro[ecL
characLerlsLlcs
W 32 Analyze oLher pro[ecL characLerlsLlcs
%lncludlng quallLy based ones)
whaL ls dlfferenL abouL Lhls pro[ecL?
WheLher lL ls a lnformaLlon sysLem or embedded
sysLem?
WhaL are Lhe crlLlcal lssues?
MalfuncLlonlng LhreaLened human llfe?
SLep 3 Analysls of pro[ecL
characLerlsLlcs
43
W 33 ldenLlfy hlgh level pro[ecL rlsks
'whaL could go wrong?'
'whaL can we do Lo sLop lL?'
W 34 1ake lnLo accounL user requlremenLs
concernlng lmplemenLaLlon
lor example cusLomer wanL Lhe producL ln [ava
W 33 SelecL developmenL meLhodology and llfe
cycle approach
waLerfall? lncremenLs? roLoLypes?
enerally Company use Lhe same meLhod or SuLC as
Lhey were uslng ln pasL
lL also depends on pro[ecL need
44
SLep 3 conLlnued
W 36 evlew overall resource esLlmaLes
When lL ls clear LhaL whaL are Lhe rlsks and whaL
approach we are golng Lo use
lL good Lo reesLlmaLe efforLs and resources
luncLlon polnL based esLlmaLlon ls used Lo
measure sysLem slze
'does all Lhls lncrease Lhe cosL?'
SLep 3 conLlnued
43
@L 4 IDLN@II IL@
DU@ ND @IVI@IL
-ow more deLalled plannlng acLlvlLy Lake place
41 ldenLlfy and descrlbe pro[ecL producLs
'whaL do we have Lo produce?'
46
ro[ecL
producLs
ManagemenL
roducLs
Module
roducLs
SysLem
roducLs
Module
code
Module
ueslgn uoc
rogress
eporLs
A producL breakdown sLrucLure
%8S)
Cverall
SpeclflcaLlon
lnLegraLed
1esL Cases
W 1he resulL of an acLlvlLy
W Could be %among oLher Lhlngs)
physlcal Lhlng %'lnsLalled pc')
a documenL %'loglcal daLa sLrucLure')
a person %'Lralned user')
a new verslon of an old producL %'updaLed
sofLware')
47
roducLs
W 1he followlng are -C1 normally producLs
acLlvlLles %eg 'Lralnlng')
evenLs %eg 'lnLervlews compleLed')
resources and acLors %eg 'sofLware
developer') may be excepLlons Lo Lhls
W roducLs CA- 8L Jellvetole or
lotetmeJlote
48
roducLs
W roducL ldenLlLy
W uescrlpLlon whaL ls lL?
W uerlvaLlon whaL ls lL
based on?
W ComposlLlon whaL
does lL conLaln?
W lorm
W elevanL sLandards
W CuallLy crlLerla
teote o lu fot #test Joto
49
roducL descrlpLlon %u)
SLep 42 conLlnued
30
4 Document
Gener|c
product
f|ows
Cverall sysLem
speclflcaLlon
Module
deslgn
Module code
lnLegraLlon
1esL cases
lnLegraLed
1esLed sofLware
llg roducL llow ulagram
%lu)
user
requlre
menL
W 1he 8S and lu wlll probably have ldenLlfled
generlc producLs eg 'sofLware modules'
W lL mlghL be posslble Lo ldenLlfy speclflc
lnsLances eg 'module A' 'module 8'
W 8uL ln many cases Lhls wlll have Lo be lefL Lo
laLer more deLalled plannlng
31
SLep 43 ecognlze producL lnsLances
W ldenLlfy Lhe acLlvlLles needed Lo creaLe each
producL ln Lhe lu
W 1o generaLe one producL from anoLher Lhere
musL be one or more acLlvlLles are used
W More Lhan one acLlvlLy mlghL be needed Lo creaLe
a slngle producL Crder ls lmporLanL
W uraw up acLlvlLy neLwork
32
44 roduce ldeal acLlvlLy neLwork
33
An 'ldeal' acLlvlLy
Speclfy
Cverall
SysLem
ueslgn
Module A
ueslgn
lnLegraLlon
1esL cases
ueslgn
Module 8
1esL
lnLegraLed
sofLware
Code
Module A
Code
Module 8
SLep 43 Add checkpolnLs lf needed
34
ueslgn
module A
ueslgn
module 8
ueslgn
sysLem
ueslgn
module C
Code
module A
Code
module 8
Code
module C
1esL
sysLem
ueslgn
module A
ueslgn
module 8
ueslgn
sysLem
ueslgn
module C
Code
module A
Code
module 8
Code
module C
1esL
sysLem
CheckpolnL
puL ln a
check polnL
W 31 Carry ouL boLLomup esLlmaLes%esLlmaLlon of
sLaff efforL)
ln SLep36 we have done Lopdown esLlmaLlon
1op down v/s 8oLLomup
dlsLlngulsh carefully beLween effott and elopseJ Llme
LfforL ls amounL of work LhaL needs Lo be done
CalculaLe efforL
Llapsed Llme ls Lhe Llme beLween sLarL and Lhe end of
Lhe Lask
AcLlvlLles on acLlvlLy neLwork can be annoLaLed wlLh
Lhelr elapsed Llmes so LhaL overall duraLlon of pro[ecL
can be calculaLed
33
SLep 3LsLlmaLe efforL for each
acLlvlLy
W 32 evlse plan Lo creaLe conLrollable
acLlvlLles
lL ls very dlfflculL Lo [udge Lhe progress of a Long
acLlvlLy
WlLh long acLlvlLy lL ls dlfflculL Lo monlLor and
conLrol Lhe acLlvlLy
break up very long acLlvlLles lnLo a serles of
smaller ones
bundle up very shorL acLlvlLles %creaLe check llsLs?)
SLep 3LsLlmaLe efforL for each acLlvlLy
36
W 61ldenLlfy and quanLlfy rlsks for acLlvlLles
damage lf rlsk occurs %measure ln Llme losL or
money)
llkellhood lf rlsk occurrlng
W 62 lan rlsk reducLlon and conLlngency
measures
rlsk reducLlon acLlvlLy Lo sLop rlsk occurrlng
ConLlngency Measures acLlon lf rlsk does occur
Lx use a conLracL sLaff lf a member of Lhe pro[ecL
Leam ls unavallable aL a key Llme because of
serlous lllness
37
SLep 6 ldenLlfy acLlvlLy rlsks
W 63 Ad[usL overall plans and esLlmaLes Lo
Lake accounL of rlsks
Ad[usL Lhe plans accordlng Lo Lhe rlsk lnvolved
wlLh lL
eg add new acLlvlLles whlch reduce rlsks
assoclaLed wlLh oLher acLlvlLles eg Lralnlng
plloL Lrlals lnformaLlon gaLherlng
38
W 71 ldenLlfy and allocaLe resources Lo acLlvlLles
1ype of sLaff needed
-umbers
SLaff avallablllLy
W 72 evlse plans and esLlmaLes Lo Lake lnLo accounL
resource consLralnLs
Some sLaff may be needed for more Lhan one Lask aL same
Llme so prlorlLy should be glven Lo Lhe crlLlcal acLlvlLy
eg sLaff noL belng avallable unLll a laLer daLe
nonpro[ecL acLlvlLles
C/ of Lhls sLep ls anLL charL
39
SLep 7 AllocaLe resources
anLL charLs
60
SelecL sub[ecLs
ueslgn
quesLlonnalre
8ook machlne
ConducL LesLs
Analyze resulLs
Week commenclng
3
12
19
26
MACP
AlL
9
16
lan LesLlng
2
urafL changes
ane
ane
lred
ackson
lred
ane
Mo
L1 lead LesLer
1A LesLlng asslsLanL
W 81 evlew quallLy aspecLs of pro[ecL plan
When Lask ls reporLed compleLe lL ls lmporLanL Lo
revlew lLs quallLy
1here should be some quallLy crlLerla
W 82 uocumenL plan and obLaln agreemenL
61
SLep 8 evlew/publlclse plan
Step 3 and 10: Execute plan
and create lower level plans