M1 Release Planning Milestone definition
Usage
| 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? | Product Backlog | Work in a Sprint | ||
| Are Product Backlog Stories prioritized? | yes | Prioritize a Backlog item | ||
| Is the project team ready to estimate the top Stories (for coming Sprint) in Product backlog? | yes | Estimate a Backlog item | ||
| Is the project team ready to create a 2 weeks Sprint in Jira? | yes | Create a Sprint | ||
| Are Team Members willing to create Tasks and associate them with Stories in Jira? | yes | Create a Backlog item | ||
| Has the project team plan to contribute to Platform Maturity Improvement? | Provide a link to project Planning, Platform Maturity table. | |||
| Release Management | Is there a Release Planning Template available and completed in wiki? | Release Planning Template | ||
| Have all the "Release Components Name" been defined in Resources and Repositories for your project? (this includes all Sub-Components Names, Sub-Components Repositories Names, Maven Group ID, Sub-Components Description) | Resources and Repositories | |||
| 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 | |||
| Have new developers made themself familiar on the Onboarding Process? | Yes | Described process on several LOG meetings to upcoming committers LOG Meeting Minutes 2018-01-02 | ||
| Is the project team aware of the Release milestone? Any misses will required TSC exception. | Yes | LOG Meeting Minutes 2018-01-16 | ||
| Integration and Testing | Has the Integration Team defined the vendor equipment list? | Link to evidence | Testing on Auto Continuous Deployment via Jenkins and Kibana discussed with Integration team on 20180116 and a couple meetings before | |
| Has the Integration Team defined the End 2 End Release Test Case? | Link to evidence | Testing on Auto Continuous Deployment via Jenkins and Kibana | ||
| Development | Is the Project Team committed to develop Unit Test? | Yes | for new code in https://gerrit.onap.org/r/#/c/28129/ | |
| Has the Project Team put in place an Automated Unit Test infrastructure? | Yes | LOG-118 - Getting issue details... STATUS | ||
| Is the Project Team committed to create Continuous System Integration Testing (CSIT) test case? | yes | migrate Auto Continuous Deployment via Jenkins and Kibana and LOG-118 - Getting issue details... STATUS | ||
| Is the Project Team committed to perform Scrum ceremonies? | yes | Scrum Overview (each meeting we review spring, epics and backlog) | ||
| 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? | yes | |||
| Does the Project Team understand the Free and Open Source Software (FOSS) process? | yes | We use the ELK stack, Kubernetes, Rancher, Filebeat, Jenkins | ||
| 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 Already filled | ||
| Is the Project Team willing to comply to the Commit Process? | yes | Commit Messages - pushing the format and process, editing the page with devops adjustments, | ||
| Does the Project Team understand the purpose of Code Review? | yes | Code Review - also added to the wiki | ||
| Is the Project Team aware of the Coding Guidelines? | yes | Development Practices (Jave Coding Style) yes, added to the process |