M1 Deliverables for Planning Milestone Checklist Template
- Steven wright
DRAFT PROPOSAL FOR COMMENTS
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? |
|---|---|---|---|---|
Security | Has the Release Security/Vulnerability table been filled out in the protected Security Vulnerabilities wiki space? | NA | Table in the protected Security Vulnerabilities wiki space corresponds to the latest NexusIQ scan | VNFRQTS is a documentation project. |
Have known vulnerabilities (critical and severe) to address/remove in the release been identified with JIRA ticket? | NA | JIRA tickets exist for vulnerabilities or the project indicates that there will be no vulnerability library replacement. | Create JIRA tickets VNFRQTS is a documentation project. | |
Has the project committed to the release CII badging level? | NA | Project plans that include | See https://www.coreinfrastructure.org/programs/badge-program/ VNFRQTS is a documentation project. | |
Has the project created their project CII questionnaire and completed the ONAP level CII requirements | NA | VNFRQTS is a documentation project. | ||
If the project uses java, has the project integrated with the oparent.pom? | NA | Oparent.pom included in the project | VNFRQTS is a documentation project. | |
Product Management | Are Product Backlog Epics entered in Jira? | Yes | Getting issues... | |
Are Product Backlog Stories entered in Jira? | Yes | Getting issues... | ||
Are Product Backlog Stories linked to Product Backlog Epics? | Yes | |||
Are Product Backlog Stories prioritized? | Yes | |||
Is the project team ready to estimate the top Stories (for coming Sprint) in Product backlog? | Yes | |||
Is the project team ready to create a 2 weeks Sprint in Jira? | Yes | |||
Are Team Members willing to create Tasks and associate them with Stories in Jira? | Yes | |||
Has the project team plan to contribute to Platform Maturity Improvement? | NA | Provide a link to project Planning, Platform Maturity table. | VNFRQTS is documentation | |
Release Management | Is there a Release Planning Template available and completed in wiki? | Yes | ||
Has the Platform Maturity Table been updated with current status and Release goal? | NA | VNFRQTS is documentation | For each Release, there is a Platform Maturity table created for PTLs to record their goals and achievements at M4 (Example: Casablanca Release Platform Maturity). | |
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 | |||
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 | |||
Have new developers made themself familiar on the Onboarding Process? | Yes | |||
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? | NA | Link to evidence | VNFRQTS is documentation |
Has the Integration Team defined the End 2 End Release Test Case? | NA | Link to evidence | VNFRQTS is documentation | |
Development | Is the Project Team committed to develop Unit Test? | NA | VNFRQTS is documentation | |
Has the Project Team put in place an Automated Unit Test infrastructure? | NA | VNFRQTS is documentation | ||
Is the Project Team committed to create Continuous System Integration Testing (CSIT) test case? | NA | VNFRQTS is documentation | ||
Is the Project Team committed to perform Scrum ceremonies? | Yes | |||
Are the Project Team members aware of Continuous Integration Principles (don't break the build, Fix the build,...)? | Yes | |||
Has the Project Team a clear understanding on the Code Coverage expectations? | NA | Code Coverage and Static Code Analysis VNFRQTS is documentation | ||
Does the Project Team understand the Free and Open Source Software (FOSS) process? | Yes | |||
Is the Project Team willing to fill out accordingly the FOSS table? | Yes | 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 | |||
Does the Project Team understand the purpose of Code Review? | Yes | |||
Is the Project Team aware of the Coding Guidelines? | NA | Development Practices (Jave Coding Style) VNFRQTS is documentation (in .rst) |