RELEASE MANAGEMENT ADVISORY

PROJECT RELEASE NUMBER DESCRIPTION

ADDA52RUMMY APP 0.0.0

INTENDED AUDIENCE
NAVEEN, KUNAL, TEAM LEADS [CRM, MARKETING, QA, DEV], PRODUCT OWNERS

STATUS STATUS KEY

PENDING: Work still needs to be done PENDING
N/A: This item cannot logically apply N/A
WAIVED: This item could apply, but the stakeholders deem it unimportant WAIVED
DONE: The stakeholders agree that the item has been satisfied DONE
FAILED: This item has forced us to abandon this release FAILED

BUILD RELEASE DETAILS

PRIORITY PLATFORMS RELEASED ON FILES(S) / RESOURCE(S) MODIFIED RESPONSIBLE START DATE END DATE BACKWARD COMPATIBILITY
ITEM(S) / FEATURE(S)

KNOWN ISSUES
ISSUE SUMMARY STATUS RESPONSIBLE

FIXED ISSUES
ISSUE SUMMARY STATUS RESPONSIBLE

DEVELOPMENT TEAM | EXIT CRITERIA

FEATURE / TASK STATUS RESPONSIBLE
All needed design work has been completed
All needed design work has been reviewed
All development work has been completed
All development work has been peer reviewed
All defects assigned to this release have been fixed
All development documentation has been updated
All unit test code has been updated
The development team is satisfied with this release

QA TEAM | EXIT CRITERIA

ITEM STATUS RESPONSIBLE COMMENTS
The QA plan and test cases have been updated Rahul Shrivastava
The QA plan has been completely carried out Rahul Shrivastava
All discovered defects have been logged Rahul Shrivastava
Any change requests or spec updates due to defects have been addressed Rahul Shrivastava
All fixed defects have been verified as fixed Rahul Shrivastava
The QA team is satisfied with this release

BUILD RELEASE CRITERIA

ITEM STATUS RESPONSIBLE
Task(s) / Feature(s) DEMO
Task(s) / Feature(s) Owner Signed-Off
All components have been properly tagged for release, and the release configuration is clearly defined.
Change-control practices have been followed, meaning that the released product does not contain
unapproved changes.
The rollback plan has been prepared.
Create a backup of the build environment, and place the development environment under change control.
Synchronize the date / time stamp on all release files.
The operations team is satisfied with this release.
Governance Teams' Approval (* minimum 2 approval mandatory)
Dependent Team(s) Informed
Post Release Check
Regression Check

REFERENCE DOCUMENTATIONS
ITEM STATUS DETAILS
WBS (Work Breakdown Structure)
Project Plan Document (this will include effort estimation document)
Dev Team Unity Testing Report
QA Report (Test Case Execution + Issues Logged)
Requirement Owners' Testing Report
Burndown Report
Capacity Planning Sheet
RELEASE MANAGEMENT ADVISORY