PRASHANT SINGH
1706225
ROHIT GARG
1706237

It is always important to have visible milestones in the life cycle where various stakeholders meet, face to face ,to discuss progress and plans

Purpose of the milestones in the lifecycle :
• Demonstrate how well a project is performing.
• Synchronize stakeholders expectations.
• Achieve concurrence on three evolving perspectives: the requirements ,the design, and the plan.
• Synchronize related artifacts into a consistent and balanced state.

• Identify the important risks,issues,and out-oftolerance conditions.
• Perform a global assessment for the whole lifecycle ,not just the current situation of an individual perspective or intermediate product.

Three types of joint management reviews are conducted throughout the process:
• Major milestones
• Minor milestones
• Status assessments

• These system wide events are held at the end of each development phase.
• They provide visibility to system wide issues.
• Synchronize the management and engineering perspectives.
• Verify that the aims of the phase have been achieved .

• Occurs at the end of the inception phase.
• Present to all stakeholders a recommendation on how to proceed with development
,including a plan, estimated cost and schedule
,and expected benefits and cost savings.

LIFE CYCLE ARCHITECTURE MILESTONE
• Occurs at the end of the elaboration phase.
• Demonstrate an executable architecture to all the stakeholders.
• A more detailed plan for construction phase is presented for approval.
• Critical issues relative to requirements and operational concept are addressed.

INITIAL OPERATIONAL CAPABILITY
MILESTONE
• Occurs late in the construction phase.
• Assess the readiness of the software to begin the transition into customer/user sites
• Authorize the start of acceptance testing .
• Issues are addressed concerning installation instructions, software versions descriptions ,user and operator manuals ability of the development organization to support user sites.

• Software quality metrics are reviewed to determine .
• The readiness of the test environment and the test software for acceptance testing is assessed.

PRODUCT RELEASE MILESTONE
• Occurs at the end of the transition phase.
• Assess the completion of the software .
• Results of the acceptance testing are reviewed.
• Open issues are addressed.
• Software quality metrics are reviewed.

MINOR MILESTONE
• These iteration-focused events .
• Conducted to review the content of an iteration in detail .
• Authorize continued work.

MILESTONE OF AN ITERATION
• Iteration Readiness Review.
• Iteration Assessment Review.

PERIODIC STATUS ASSESSMENTS
• Serve as project snapshots
• A mechanism for open addressing
,communicating and resolving management issues ,technical issues, and project risks.
• Objective data derived directly from on-going activities and evolving product configurations.
• A mechanism for disseminating process,progress,quality trends,practices,and experience information to and from all stakeholders in an open forum.