Wednesday, 28 August 2013

Explain different project closure reports.

The different project closure reports are:
a.     General Information
b.     Performance Summary
c.      Process Details
d.     Tools Used
e.     Risk Management


a.     General Information:
Project Code                                Xxxxx
Life Cycle                           Development, Full life cycle
Business Domain                      Finance. Web-based application for managing accounts.
Project leader/ Module Leader    
Business Manager                    XXXXXXX
Software Quality Adviser      Xxxxx
b.     Performance Summary:
Performance Parameter
Actual
Estimated
Deviation
Reasons for Deviation (If Large)
Total Effort (person-days)
597
501
19%
Two major change requests that came.
Peak Team Size
9
9
0
N/A
Start Date
03 Apr 2000
03 Apr 2000
0
N/A
End Date
03 Nov 2000
30 Nov 2000
27 Days
Two major change requests consumed more than 5% of the effort.
Quality (number of defects delivered per FP)
0.002
0.0125

Quality improved because of defect prevention and use of incremental process.
Productivity
58
57
2%
N/A
Cost of quality
31.4%
33%
5%
N/A
Defect injection rate
0.022
0.03
-26%
Improved because of defect prevention.
Defect removal efficiency
97.4
97
Small
N/A
c.      Process Details
·        Rational Unified Process was employed.
·        Development and analysis were done iteratively
·        3 iterations for development and 2 for design and analysis.
·        Requirement traceability was done through Requisite Pro tool.
d.     Tools Used:
·        Notes on Tools Used
·        External Tools: VSS, VJA, Requisite Pro, MSP
·        Internal Tools: BugsBunny, WAR

e.     Risk Management:
·        Risks identified at the start of the project
·        Risk 1 Lack of support from database architect and database administrator of the customer
·        Risk 2 Improper use of RUP, as it is being used for the first time
·        Risk 3 Personnel attrition
·        Risk 4 Problems with working on customer's database over the link. Risks encountered during the project
·        Risk 1 Impact of conversion to VAJ 3.0
·        Risk 2 Lack of support from database architect and database administrator of the customer
·        Risk 3 Improper use of RUP, as it is being used for the first time
Risk 4 Personnel attrition

No comments:

Post a Comment