DRAFT PROPOSAL FOR COMMENTS
This checklist is expected to be completed for the project to pass the M1 Release Planning Milestone.
| Practice Area | Checkpoint | Yes/No | Evidence - Comment | How to? |
|---|---|---|---|---|
| Product Management | Are Product Backlog Epics entered in Jira? | YES | Getting issues... | |
| Are Product Backlog Stories entered in Jira? | YES | Getting issues... | 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? | NO | Prioritize a Backlog item | ||
| Is the project team ready to estimate the top Stories (for coming Sprint) in Product backlog? | NO | Estimate a Backlog item | ||
| Is the project team ready to create a 2 weeks Sprint in Jira? | NO | Create a Sprint | ||
| Are Team Members willing to create Tasks and associate them with Stories in Jira? | YES | Create a Backlog item | ||
| Release Management | Is there a Release Planning Template available and completed in wiki? | YES | [vnfrqts] Amsterdam 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) | 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. | Resources and Repositories (Deprecated) | |||
| Have new developers made themself familiar on the Onboarding Process? | YES | reviewed at 7-11-2017 call | Onboarding | |
| Is the project team aware of the Release milestone? Any misses will required TSC exception. | YES | reviewed at 7-11-2017 call | ||
| Integration and Testing | Has the Integration Team defined the vendor equipment list? | N/A | Link to evidence | VNF Requirements deliverables are documents not software |
| Has the Integration Team defined the End 2 End Release Test Case? | JIRA Issues created on this: | VNF Requirements Test Case Descriptions need to be (1) aligned with End 2 End Release Test Case and (2) Reference VNFs in End 2 End Release test cases should be validated against these VNF Requirements test case Descriptions | ||
| Development | Is the Project Team committed to develop Unit Test? | N/A | This project does not generate code | |
| Has the Project Team put in place an Automated Unit Test infrastructure? | N/A | This project does not generate code | ||
| Is the Project Team committed to create Continuous System Integration Testing (CSIT) test case? | ||||
| Is the Project Team committed to perform Scrum ceremonies? | Scrum Overview | |||
| Are the Project Team members aware of Continuous Integration Principles (don't break the build, Fix the build,...)? | Continuous Integration | |||
| Has the Project Team a clear understanding on the Code Coverage expectations? | N/A | This project does not generate code | ||
| Does the Project Team understand the Free and Open Source Software (FOSS) process? | YES | 2017-7-11 mtg Notes & Agenda | Free and Open Source Software | |
| Is the Project Team willing to fill out accordingly the FOSS table? | YES | 2017-7-11 mtg Notes & Agenda | 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 | 2017-7-11 mtg Notes & Agenda | Commit Messages | |
| Does the Project Team understand the purpose of Code Review? | YES | 2017-7-11 mtg Notes & Agenda | Code Review | |
| Is the Project Team aware of the Coding Guidelines? | N/A | This project does not generate code | Development Practices (Jave Coding Style) | |