0% found this document useful (0 votes)
2 views

SPM Part3

The document outlines a review process model that includes review meetings, data collection, project termination reviews, and visualization of project progress. It emphasizes the importance of logging defects, collecting project metrics, and conducting final reviews to learn from past projects. Additionally, it discusses earned value analysis as a method to monitor project performance in terms of schedule and cost.

Uploaded by

sarvachan verma
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
2 views

SPM Part3

The document outlines a review process model that includes review meetings, data collection, project termination reviews, and visualization of project progress. It emphasizes the importance of logging defects, collecting project metrics, and conducting final reviews to learn from past projects. Additionally, it discusses earned value analysis as a method to monitor project performance in terms of schedule and cost.

Uploaded by

sarvachan verma
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 13

Review process model

(cont..)
2

2 Review meeting
🞑 In the meeting, the reviewers give their comments based on the logs

🞑 The comments may be pertain to a : Defect, Work simplification &


Maintainability
🞑 Moderator ensures that the discussion remains focused and
productive. The recorder scribes all the defects and review statistics
in the form of review log
 Rework
🞑 Author addresses all the issues raised by the reviewers by
carrying out the necessary modification and prepares a
rejoinder to all the points scribed in the review log
🞑 Rejoinder is circulated among all the reviewers
🞑 In a final meeting the reviewers check whether all the issues have
been resolved satisfactorily. At the end of the meeting, final summary
report of the review is prepared
23 Data collection
 Data representing the results of the meetings is recorded.
 In addition to recording all the defects ,the data about the time spent by the
reviewers in the review activity must also be captured.
 The different reports in which the review data are captured are as follows
🞑 Review Preparation Log
 Each reviewer prepares a review preparation log
 The different items recorded by the reviewer are
 Data about the defects, their locations , their criticality and total time
spent
🞑 Review Log : The defects which are agreed by the author are logged
 The defect logs are crucial record since these help in tracking defects to
closure
🞑 Review Summary Report : Summarizes the review data and presents the
overall picture of the review
 Contains information about total defects and the amount of time spent
24 Project Termination Review
 Project termination reviews are important for
successful, failed as well as prematurely abandoned projects
 It marks the official closure of the project
 It provides important opportunities to learn from past mistakes
as well as success
 Reasons for project termination before the natural closing date
🞑 Project is completed successfully and handed over to the customer
🞑 Incomplete requirements
🞑 Lack of resources
🞑 Some key technologies used in the project have become obsolete
🞑 Economics of the project has changed
25 Project termination process
 Project Survey
🞑 The objective is to collect various types of information pertaining to
the project
🞑 An electronic survey is usually very effective
🞑 The information is collected through a set of questionnaire to bring
out important process and management.
 Collection of Objective Information
🞑 A critical aspect of the review is to collect various project metrics.
The metrics include cost, schedule & quality reviews
 Debriefing Meeting
🞑 This preparatory meeting helps to ensure the final review
meeting focuses on the most relevant aspects
🞑 Only the seniors members of the team participate
26 Project termination process
🞑 The meeting helps to obtain some direct feedback about the
project from the senior members of the team
 Final project review
🞑 This meeting addresses various issues like
 Projectplanning and tracking, preliminary phases,
configuration
management, verification and validation
 Result publication
🞑 Project leader summarizes the positive and negative findings
as well as prescription for improvement
🞑 Summary is published for necessary correction for future
projects
27 Visualizing Progress
 After collecting the data about the progress of the project, a manager
needs to present the data.
 Some methods of presenting the picture of a project and its future are
🞑 Gantt chart
 Essentially an activity bar chart indicating the scheduled activity
dates and duration with activity floats
🞑 Slip chart
 Provides a more striking visual induction of the activities
 The more the slip line bends, the greater the variation from the
plan. Very jagged slip line indicates a need for
rescheduling
🞑 Timeline
 A method of recording and displaying the way in
Slip
Gantt charts charts
28
29 The timeline

Records the way targets have


changed throughout the project
30 Cost monitoring
 A project could be late because the staff originally
committed, have not been deployed
 In this case the project will be behind time but under

budget
 A project could be on time but only because

additional resources have been added and so by over


budget
 Need to monitor both achievements and costs
31 Earned value analysis
 Planned value (PV) or Budgeted cost of work
scheduled (BCWS) –
🞑 The assigned value
🞑The original budgeted cost for the item
 Earned value (EV) or Budgeted cost of work

performed (BCWP) –
🞑The total value credited to a project at any
point of time
32 Earned value – an example
 Tasks
🞑 Specify module 5 days
🞑 Code module 8 days
🞑 Test module 6 days

 At the beginning of day 20, Planned Value (PV) = 19 days


 If everything but testing completed, EV = 13 days
 Schedule variance = EV-PV i.e. 13-19 = -6
 Schedule performance indicator (SPI) = EV/PV
i.e 13/19 = 0.68
33 Earned value analysis – actual co
 Actual cost (AC) is also known as Actual cost of work
performed (ACWP)
 In previous example, if
🞑 ‘Specify module’ actually took 3 days (planned 5 days)

🞑 ‘Code module’ actually took 4 days (planned 8 days)


 Actual cost = 7 days
 Cost variance (CV) = EV-AC i.e. 13-7 = 6 days
 Cost performance indicator (CPI) = EV/AC i.e 13/7 = 1.86
 Positive CV or CPI > 1.00 means project under budget or the work
is completed better than planned

You might also like