...
This checklist is expected to be completed for the project to pass the M1 Release Planning Milestone.
M1 Release Planning Milestone definition
| Practice Area | Checkpoint | Yes/No | Evidence - Comment | How to? | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product Management | Are Product Backlog Epics entered in Jira? | Yes |
| |||||||||||
| Are Product Backlog Stories entered in Jira? | Yes |
| Create a Backlog item | |||||||||||
| Are Product Backlog Stories linked to Product Backlog Epics? | Yes | Product Backlog | Work in a Sprint | |||||||||||
| Are Product Backlog Stories prioritized? | Yes | Product Backlog | Prioritize a Backlog item | |||||||||||
| Is the project team ready to estimate the top Stories (for coming Sprint) in Product backlog? | Yes | Product Backlog | Estimate a Backlog item | |||||||||||
| Is the project team ready to create a 2 weeks Sprint in Jira? | Yes | Current Sprint | Create a Sprint | |||||||||||
| Are Team Members willing to create Tasks and associate them with Stories in Jira? | Yes | Product Backlog | Create a Backlog item | |||||||||||
| Has the project team plan to contribute to Platform Maturity Improvement? | Yes | Beijing Release Platform Maturity | ExtAPI is not included on the MVP list for the release will not be subject to the minimum recommendation for each maturity category. | |||||||||||
| Release Management | Is there a Release Planning Template available and completed in wiki? | Yes | Release Planning Template | |||||||||||
| Have all the "Release Components Name" been defined in Resources and Repositories (Deprecated) for your project? (this includes all Sub-Components Names, Sub-Components Repositories Names, Maven Group ID, Sub-Components Description) | Yes | Resources and Repositories (Deprecated) | ||||||||||||
| Have all the "Resources committed to the Release" been defined in Resources and Repositories for your project? This includes First and Last names, LFID, Email Address and Location for PTL, Project Manager, Committers and Contributors. | Yes | Resources and Repositories (Deprecated) | ||||||||||||
| Have new developers made themself familiar on the Onboarding Process? | Yes | Onboarding | ||||||||||||
| Is the project team aware of the Release milestone? Any misses will required TSC exception. | Yes | |||||||||||||
| Integration and Testing | Has the Integration Team defined the vendor equipment list? | N/A | Link to evidence | VNFRQTS is a documentation project - no Vendor equipment is requiredExtAPI has not identified any vendor equipement | ||||||||||
| Has the Integration Team defined the End 2 End Release Test Case? | N/A | Link to evidence | VNFRQTS is a documentation project - no E2E Release Test case is defined ExtAPI is not on MVP, so E2E Test Case is not required | |||||||||||
| Development | Is the Project Team committed to develop Unit Test? | N/A | VNFRQTS is a documentation project - no Unit Test case is defined - leverages the LF toolchain maintained by documentation projectYes | |||||||||||
| Has the Project Team put in place an Automated Unit Test infrastructure? | N/A | VNFRQTS is a documentation project - no ExtAPI is not on MVP, so Automated Unit Test case is defined - leverages the LF toolchain maintained by documentation projectis not required | ||||||||||||
| Is the Project Team committed to create Continuous System Integration Testing (CSIT) test case? | N/A | VNFRQTS is a documentation project - no Unit Test case is defined - leverages the LF toolchain maintained by documentation projectYes | ||||||||||||
| Is the Project Team committed to perform Scrum ceremonies? | Yes | 2018 weekly Project meetings | Scrum Overview | |||||||||||
| Are the Project Team members aware of Continuous Integration Principles (don't break the build, Fix the build,...)? | Yes | VNFRQTS is a documentation project - no Unit Test case is defined - leverages the LF toolchain maintained by documentation project | Continuous Integration | |||||||||||
| Has the Project Team a clear understanding on the Code Coverage expectations? | N/A | VNFRQTS is a documentation project - no Unit Test case is defined - leverages the LF toolchain maintained by documentation project | Yes | |||||||||||
| Does the Project Team understand the Free and Open Source Software (FOSS) process? | Yes | Free and Open Source Software | ||||||||||||
| Is the Project Team willing to fill out accordingly the FOSS table? | Yes | Project Foss | Fill out sub-pages for each project under Free and Open Source Software | |||||||||||
| Is the Project Team willing to comply to the Commit Process? | Yes | Commit Messages | ||||||||||||
| Does the Project Team understand the purpose of Code Review? | N/A | VNFRQTS is a documentation project Yes | Code Review | |||||||||||
| Is the Project Team aware of the Coding Guidelines? | N/A | VNFRQTS is a documentation project Yes | Development Practices (Jave Coding Style) |