8/19/2019 Prm704 Lecture 26
1/56
Quick Recap
8/19/2019 Prm704 Lecture 26
2/56
Lesson 11: Monitoring and Controlling Project Work
Topic 11A: Identify the Monitor and Control Project Work ProcessTopic 11B: Develop an Integrated Change Control yste!
Topic 11C: "tili#e the Integrated Change Control yste!
Topic 11D: $evie% Delivera&les and Work $es'lts
Topic 11(: Control the Project cope
8/19/2019 Prm704 Lecture 26
3/56
“Change Control”
Syste !or "pleenting Monitoring and Controlling
3
8/19/2019 Prm704 Lecture 26
4/56
C#$ considerations !or each change %prior to
authorisation& '()
) The i!pact on non*IT infrastr'ct'res %ithin the
organisation
) (ffect+risk+i!pact of not i!ple!enting the change
) Technical capa&ility and technical approval
) ,inancial approval -if re.'ired/
) Third party+s'pplier involve!ent in the i!ple!entation of
the change) B'siness approval -if re.'ired/
) $evie%+assess!ent of the change priority
4
8/19/2019 Prm704 Lecture 26
5/56
5
8/19/2019 Prm704 Lecture 26
6/56
#cti*ities o! change +uilding
) &'ilding a ne% prod'ction !od'le
) creating a ne% version of one or !ore soft%are !od'les
) p'rchasing e.'ip!ent or services e0ternally
)
preparing a hard%are !odification) prod'cing ne% or a!ended doc'!entation sho%ing the
co!ponents of the change &'ild
) devising a +ackout plan
)
devising testing re.'ire!ents as appropriate) doc'!enting re.'ired reso'rces for the change
i!ple!entation
6
8/19/2019 Prm704 Lecture 26
7/56
7
8/19/2019 Prm704 Lecture 26
8/56
Change re*ie,
) The change has had the desired effect and !et its
o&jectives) "sers and c'sto!ers are content %ith the res'lts or to
identify any shortco!ings
) There have &een no 'ne0pected or 'ndesira&le side
effects to f'nctionality availa&ility capacity+perfor!ancesec'rity !aintaina&ility etc2
) The reso'rces 'sed to i!ple!ent the change %ere as
planned
) The i!ple!entation plan %orked correctly -so incl'de
co!!ents fro! the i!ple!enters/
) The change %as i!ple!ented on ti!e and to cost
) The &acko't plan f'nctioned correctly if the &acko't plan
%as i!ple!ented
8
8/19/2019 Prm704 Lecture 26
9/56
R-P .%Rational -ni!ied Process& Con!iguration
and Change Manageent
) CCM is one of $"P3s 4 Disciplines
) Analysis and Design B'siness Modeling
Con!iguration and Change Manageent
Deploy!ent (nviron!ent I!ple!entation Project
Manage!ent2 $e.'ire!ents Test
9
8/19/2019 Prm704 Lecture 26
10/56
CCM Work!lo,
10
8/19/2019 Prm704 Lecture 26
11/56
Role: Con!iguration Manager'1)
) Manages the overall Config'ration Manage!ent -CM/
infrastr'ct're and environ!ent for the prod'ct
develop!ent tea!
) $ole is often shared &y a Config'ration -or Change/
Control Board -CCB/
11
8/19/2019 Prm704 Lecture 26
12/56
Role: Con!iguration Manager'()
) Consists of representatives fro! all interested parties
incl'ding c'sto!ers developers and 'sers
) In a s!all project a single tea! !e!&er s'ch as the
project !anager or soft%are architect !ay play this role
12
8/19/2019 Prm704 Lecture 26
13/56
Role: Con!iguration Manager'/)
) ho'ld 'nderstand config'ration !anage!ent principles
) ho'ld &e skilled in esti!ating cost and sched'le
i!pacts of change re.'ests
) ho'ld &e a&le to co!!'nicate effectively in order to
negotiate scope changes and in order to deter!ine ho%
each change re.'est sho'ld &e handled and &y %ho!
13
8/19/2019 Prm704 Lecture 26
14/56
Role: Change Control Manager'1)
) This role defines and oversees the change control
process2
) This role is often shared &y a Config'ration -or Change/
Control Board -CCB/ and consists of representativesfro! all interested parties like c'sto!ers developers
and 'sers
) In a s!all project the project !anager or soft%are
architect !ay play this role
14
8/19/2019 Prm704 Lecture 26
15/56
Role: Change Control Manager'()
) ho'ld 'nderstand change !anage!ent principles
) ho'ld &e skilled in esti!ating cost and sched'le
i!pacts of change re.'ests
) ho'ld &e a&le to co!!'nicate effectively in order to
negotiate scope changes and in order to deter!ine ho%
each change re.'est sho'ld &e handled and &y %ho!
15
8/19/2019 Prm704 Lecture 26
16/56
Plan Project Con!iguration 0 Change Control'1)
) (sta&lishes an appropriate plan for !anaging and
controlling change to the artifacts that are developed as
%ork prod'cts of the soft%are develop!ent process
) Contains 5 Tasks
16
8/19/2019 Prm704 Lecture 26
17/56
Plan Project Con!iguration 0 Change Control'()
) (sta&lish Config'ration Manage!ent -CM/ Policies
) Define Config'ration Identification Practices
)
Define Baseline Practices) Define Archiving Practices
) Define Config'ration tat's $eporting $e.'ire!ents
17
8/19/2019 Prm704 Lecture 26
18/56
Plan Project Con!iguration 0 Change Control'/)
) Write Config'ration Manage!ent -CM/ Plan
) Write the CM Plan
)
$evie% and Approve the CM Plan) Maintain the CM Plan
18
8/19/2019 Prm704 Lecture 26
19/56
Plan Project Con!iguration 0 Change Control')
) (sta&lish Change Control Process
) (sta&lish the Change $e.'est Process
)
(sta&lish the Change Control Board) Define Change $evie% 6otification Protocols
19
8/19/2019 Prm704 Lecture 26
20/56
Create Project Con!iguration
Manageent %CM&
2n*ironents'1)) This activity esta&lishes an environ!ent %here the
overall prod'ct can &e developed &'ilt and !ade
availa&le for stakeholders2
) Contains 7 Tasks
20
8/19/2019 Prm704 Lecture 26
21/56
Create Project Con!iguration
Manageent %CM&
2n*ironents'()) et 'p the CM 8ard%are (nviron!ent
) et 'p the CM 8ard%are (nviron!ent
)
Map the Architect're to the $epository) Create Initial et of 9ersioned (le!ents
) Define Baseline Pro!otion evels
21
8/19/2019 Prm704 Lecture 26
22/56
Create Project Con!iguration
Manageent %CM&
2n*ironents'/)) Create Integration Workspaces
) The integration %orkspace is %here s'&syste! and
syste! integrators convince the!selves that
separately developed and tested co!ponents can
indeed %ork together as a prod'ct2
) Integrators co!&ine the ele!ents delivered to the
integration %orkspace to prod'ce a B'ild2
22
8/19/2019 Prm704 Lecture 26
23/56
8/19/2019 Prm704 Lecture 26
24/56
Manage Change Re3uests '()
) '&!it Change $e.'est
) Co!plete C$ ,or!
) '&!it the Change $e.'est
) (0a!ple:) a!ple Change $e.'est ,or!2doc
) Change $e.'est ,or!2doc
24
http://var/www/apps/conversion/tmp/2012/9.%20Change%20Management/Sample%20Change%20Request%20Form.dochttp://var/www/apps/conversion/tmp/2012/9.%20Change%20Management/Change%20Request%20Form.dochttp://var/www/apps/conversion/tmp/2012/9.%20Change%20Management/Change%20Request%20Form.dochttp://var/www/apps/conversion/tmp/2012/9.%20Change%20Management/Sample%20Change%20Request%20Form.doc
8/19/2019 Prm704 Lecture 26
25/56
Manage Change Re3uests '/)
) "pdate Change $e.'est
) $etrieve the Change $e.'est ,or!
) "pdate and $es'&!it the Change $e.'est ,or!
25
8/19/2019 Prm704 Lecture 26
26/56
Manage Change Re3uests ')
) $evie% Change $e.'ests
) ched'le CCB Control Meeting
) $etrieve Change $e.'ests for $evie%
) $evie% '&!itted Change $e.'ests
26
8/19/2019 Prm704 Lecture 26
27/56
Manage Change Re3uests '4)
) Confir! D'plicated or $ejected C$
) $etrieve the Change $e.'est ,or!
) Confir! D'plication or 9alidity
) "pdate the Change $e.'est tat's
27
8/19/2019 Prm704 Lecture 26
28/56
Manage Change Re3uests '5)
) ched'le and Assign Work
) Allocate Change $e.'est to an Iteration
) Assign $esponsi&ility
) Descri&e Work and (0pected
8/19/2019 Prm704 Lecture 26
29/56
Manage Change Re3uests '6)
) 9erify Changes in B'ild
) $esolve Change $e.'est
) 9erify Changes in Test B'ild
) 9erify Changes in $elease B'ild
29
8/19/2019 Prm704 Lecture 26
30/56
Monitor 0 Report Con!iguration Status '1)
) This activity provides visi&ility to config'ration change
activity thro'gh ongoing !onitoring and reporting2
) Contains 7 Tasks
30
8/19/2019 Prm704 Lecture 26
31/56
Monitor 0 Report Con!iguration Status '()
) $eport on Config'ration tat's goals:
) 'pport project Config'ration tat's Acco'nting
tasks2
) ,acilitate prod'ct revie% thro'gh defect tracking and
reporting tasks2
) (ns're that data is =rolled*'p= and reported for the
p'rposes of tracking progress and trends2
31
8/19/2019 Prm704 Lecture 26
32/56
Monitor 0 Report Con!iguration Status '/)
) Perfor! Config'ration A'dit
) Perfor! Physical Config'ration A'dit -check if
&aseline contains all re.'ired %ork prod'cts/
) Perfor! ,'nctional Config'ration A'dit -check that a
&aseline !eets re.'ire!ents/
) $eport ,indings
32
8/19/2019 Prm704 Lecture 26
33/56
Change and 7eli*er Con!iguration "tes'1)
) This activity !anages project artifacts and the %ork
involved fro! their initial creation as private artifacts
thro'gh to their delivery and general availa&ility to the
project tea! and other stakeholders2) Contains ; Tasks
33
8/19/2019 Prm704 Lecture 26
34/56
Change and 7eli*er Con!iguration "tes'()
) Create Develop!ent Workspace
) A develop!ent %orkspace is a private develop!ent
area that provides an environ!ent in %hich a tea!
!e!&er can !ake changes to %ork prod'cts %itho'tthe changes &eco!ing i!!ediately visi&le to other
tea! !e!&ers2
34
8/19/2019 Prm704 Lecture 26
35/56
Change and 7eli*er Con!iguration "tes'/)
) Make changes
) Checks o't the files that need to &e changed2
) Makes the changes2
) Perfor!s 'nit tests to verify the changes2
) >ets the changes approved2
) Checks in the changes2
) Pro!ote the changes2
35
8/19/2019 Prm704 Lecture 26
36/56
Change and 7eli*er Con!iguration "tes')
) Deliver Changes
) Prepare for Delivery
) Deliver Changes
) "pdate Work
8/19/2019 Prm704 Lecture 26
37/56
Change and 7eli*er Con!iguration "tes'4)
) "pdate Workspace
) (ns're tea! !e!&ers are %orking on the !ost
recent versions of the project files
) "pdate the files displayed in the develop!ent vie%
-%orkspace/ %ith those in the reco!!ended &aseline
37
8/19/2019 Prm704 Lecture 26
38/56
Change and 7eli*er Con!iguration "tes'5)
) Create Baselines
) (ns're that all developed %ork prod'cts are capt'red
and archived at given points in ti!e as a &asis for
f'rther prod'ct develop!ent
) >ood candidates for a &aseline are the sets of files
and directories 'nder version control that are
developed integrated and released together
38
8/19/2019 Prm704 Lecture 26
39/56
Change and 7eli*er Con!iguration "tes'6)
) Pro!ote Baseline
) (sta&lish %hen the creation of a Baseline is
co!pleted and ho% a co!pleted Baseline !'st &e
la&eled) Baselines -individ'ally tested co!ponents fro!
vario's i!ple!enters and develop!ent tea!s
co!&ined together to %ork together as a prod'ct/ are
=tagged= to reflect the level of soft%are !at'ritysta&ility and .'ality they !ay have achieved
39
8/19/2019 Prm704 Lecture 26
40/56
Manage $aselines 0 Releases '1)) This activity ens'res that consistent sets of related or
dependent artifacts can &e identified as part of a
?&aseline? for vario's p'rposes s'ch as the identification
of release candidates prod'ct versions artifact !at'rity
or co!pleteness2) Contains 5 Tasks
40
8/19/2019 Prm704 Lecture 26
41/56
8/19/2019 Prm704 Lecture 26
42/56
Manage $aselines 0 Releases '()
) Create Baseline
) @done
) Pro!ote Baseline
) @done
42
8/19/2019 Prm704 Lecture 26
43/56
8inal Conclusions
) What are CCM o&jectives
) Managing change is !ore than j'st checking*in and
checking*o't files2 It incl'des !anage!ent of
%orkspaces parallel develop!ent integration and&'ilds2
) Which are the !ain topics for CCM
) Coordinating the Activities and Artifacts
) Coordinating Iterations and $eleases) Coordinating Changes to oft%are
43
8/19/2019 Prm704 Lecture 26
44/56
8inal Conclusions
) When CCM is esta&lished
)
8/19/2019 Prm704 Lecture 26
45/56
8inal Conclusions
) Who tells 's ho% CCM can &e done
) In PMB
8/19/2019 Prm704 Lecture 26
46/56
Control Project Scope
46
8/19/2019 Prm704 Lecture 26
47/56
Scope onitoring and control
) At the planning stage the project scope %as identified
%ith the help of:
) cope definition -in and o't/
) $e.'ire!ents
) Delivera&les
) WB
8/19/2019 Prm704 Lecture 26
48/56
Scope Control
) Scope control involves controlling changes to the
project scope
) 9oals o! scope control are to:
) Infl'ence the factors that ca'se scope changes
) Ass're changes are processed according to
proced'res developed as part of integrated change
control
) Manage changes %hen they occ'r
) ariance is the difference &et%een planned and act'al
perfor!ance2 Control variances
EF
8/19/2019 Prm704 Lecture 26
49/56
;he !actors o! scope change
) Ti!e is shorter than planned
) 8'!an reso'rces not availa&le
) Material reso'rces shortage
) $e.'ire!ents changed
8/19/2019 Prm704 Lecture 26
50/56
Progress tracking
) Tracking is the process of co!paring act'al %ith plan
) 8elp to 'nderstand the project iss'es and j'stify
re.'ests for changes
) With act'al in hands yo' %ill operate %ith facts
) Planned characteristics are recorded %ith the help of
&aseline
8/19/2019 Prm704 Lecture 26
51/56
$aselines
) M Project allo% storing the project &aseline
) Baseline sho'ld &e stored first %hen the
planning stage is co!pleted) It can &e 'pdated d'ring the project
i!ple!entation to reflect changes
) Baseline is a snapshot of:) Tasks
) $eso'rces
) Assign!ents
8/19/2019 Prm704 Lecture 26
52/56
;asks +aseline
) ,or each task it %ill sho% planned characteristics of
) D'ration
) tart and finish date
) $eso'rces assigned
) Cost
) Dependencies
8/19/2019 Prm704 Lecture 26
53/56
-se o! +aseline
) Planned data are 'sed to calc'late
) Critical Path
) ,ree and float slack
) (arly and late start and finish date
) They also are 'sed to !onitor the project perfor!ance in
ter!s of ti!eline and cost
8/19/2019 Prm704 Lecture 26
54/56
$aseline options
) ,or entire project
) ,or selected tasks
) ,or a part of the project that starts fro! selected task
8/19/2019 Prm704 Lecture 26
55/56
8/19/2019 Prm704 Lecture 26
56/56
-sing ta+les
) 9ie% H Ta&le H 9ariance
) ho% variances in task ti!ing &et%een &aseline and
act'al
) 9ie% H Ta&le H Work
) ho% differences &et%een &aseline and act'al %ork
efforts
) 9ie% H Ta&le H Cost
) ho% differences in cost &et%een &aseline and act'al