We also worked on the wiki subpages to aide git clones, building, deploying devops duties
Is the Project Team committed to develop Unit Test?
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? |
|---|---|---|---|---|
| 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 | See Backlog | Prioritize a Backlog item | |
| Is the project team ready to estimate the top Stories (for coming Sprint) in Product backlog? | Estimate a Backlog item | |||
| Is the project team ready to create a 2 weeks Sprint in Jira? | Yes | Sprint Planning Board | Create a Sprint | |
| Are Team Members willing to create Tasks and associate them with Stories in Jira? | Yes | See OOM-460 | Create a Backlog item | |
| Has the project team plan to contribute to Platform Maturity Improvement? | Yes | OOM provides many of the capability needed for platform maturity - see OOM for Production-Grade Deployments | ||
| Release Management | Is there a Release Planning Template available and completed in wiki? | OOM Beijing - M1 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 | We also worked on the wiki subpages to aide git clones, building, deploying devops duties | ||
| Is the project team aware of the Release milestone? Any misses will required TSC exception. | Yes | We discuss this in multiple OOM meetings OOM Meeting Notes - 2018-01-17 | ||
| Integration and Testing | Has the Integration Team defined the vendor equipment list? | Yes | See email | |
| Has the Integration Team defined the End 2 End Release Test Case? | Yes | See email | ||
| Development | Is the Project Team committed to develop Unit Test? | No | Not Applicable | |
| Has the Project Team put in place an Automated Unit Test infrastructure? | No | Not Applicable | ||
| Is the Project Team committed to create Continuous System Integration Testing (CSIT) test case? | Yes | See: OOM/ONAP CD dashboard | see also Auto Continuous Deployment via Jenkins and Kibana | |
| 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,...)? | Yes | This is why we created the CD system | Continuous Integration | |
| Has the Project Team a clear understanding on the Code Coverage expectations? | Yes | Not Applicable | ||
| Does the Project Team understand the Free and Open Source Software (FOSS) process? | Yes | No change in open-source usage in this release | Free and Open Source Software | |
| Is the Project Team willing to fill out accordingly the FOSS table? | Yes | Same as Amsterdam | 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 | See example | Commit Messages - we also adjusted the wiki to clearly define the format and operations | |
| Does the Project Team understand the purpose of Code Review? | Yes | See reviews | Code Review - we apply the 2nd company principle and utilize contributors to help test/review along with committers | |
| Is the Project Team aware of the Coding Guidelines? | Yes | Not Applicable | Development Practices (Jave Coding Style) |