**********
Level 2 - Repeatable
Disciplined Process and Process Definition
 |
Predictability increases with basic project controls to track cost, schedule and functionality, SQA and baselines management in place |
|
No commitments are made without thorough review and ratification |
|
While development process vary from project to project, management controls are standardized to repeat success on similar projects with similar applications |
|
Able to meet targeted dates with increased accuracy |
|
Given success with one project, chances of repeating the same level of performance is high if application area, tools, methods, and staff are largely unchanged |
1. Requirement Management
|
Register requirements and update requirements baseline, manage requirement driven changes |
|
Verify the requirements with customer |
|
Maintain change plan (Process) as per allocation |
|
Specify how the allocated requirements will be built into the software items, documentation's (Process, execution, Traceability) |
|
Keep track of the status of requirements (measurement, QA review) |
2. Software Quality Assurance
|
Plan and perform EQA and IQA activities, verify and validate development process, software activities, procedures, standards and deliverables, communicate results, |
|
Address non-compliances, take corrective action based on reviews and audits and escalate, |
|
SQA budget, Mgmt review. |
3. Software Project Planning
|
Allocate requirements, estimate the work to be performed, document estimates |
|
Define and prepare the plan of how the software project work will be done, |
|
Identify milestone and obtain commitment of all concerned |
|
Obtain resources for executing the project and Review of planned and unplanned activities by PM (measurement) |
4. Software Project Tracking and Oversight
|
Track actuals such as time, cost, resources utilized & responsibilities, |
|
Identify jointly the causes of changes in plan, open issues, risk, action items and manage commitment changes |
|
Monitor project performance against estimates, deliverables, take corrective actions, know the effect of deviations, Mgmt. review (periodic and event based). |
5. Software Configuration Management
|
Plan SCM activities, Define SCM procedure, use SCM baseline for identifying and tracing software items/ configuration items within each project |
|
Control of changes to configuration items in baseline |
|
Audit of SCM, CR/TR status, effort spent on SCM, PM review |
6. Software subcontract Management
|
Evaluate, select and train sub-contractor as per procedure, |
|
Exchange technical details, monitor performance and results of sub-contractors , |
|
Review of schedules/ actuals by PM, maintain communication, effort spent in monitoring (SQC audit) |
