Skip to end of metadata
Go to start of metadata

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 AreaCheckpointYes/NoEvidence - CommentHow to?
Product ManagementAre Product Backlog Epics entered in Jira?Yes

Getting issues...

Create a Backlog item

Difference between a Product and Sprint Backlog

Are Product Backlog Stories entered in Jira?Yes

Getting issues...

Create a Backlog item
Are Product Backlog Stories linked to Product Backlog Epics?YesProduct BacklogWork in a Sprint
Are Product Backlog Stories prioritized?YesSee BacklogPrioritize 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?YesSprint Planning BoardCreate a Sprint
Are Team Members willing to create Tasks and associate them with Stories in Jira?YesSee OOM-460Create a Backlog item
Has the project team plan to contribute to Platform Maturity Improvement?YesOOM provides many of the capability needed for platform maturity - see OOM for Production-Grade Deployments
Release ManagementIs 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 for your project? (this includes all Sub-Components Names, Sub-Components Repositories Names, Maven Group ID, Sub-Components Description)YesResources 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.YesResources and Repositories
Have new developers made themself familiar on the Onboarding Process?Yes

Onboarding

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 TestingHas the Integration Team defined the vendor equipment list?YesSee email
Has the Integration Team defined the End 2 End Release Test Case?YesSee email
Development



Is the Project Team committed to develop Unit Test?

NoNot Applicable
Has the Project Team put in place an Automated Unit Test infrastructure?NoNot Applicable
Is the Project Team committed to create Continuous System Integration Testing (CSIT) test case?YesSee: OOM/ONAP CD dashboardsee 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,...)?YesThis is why we created the CD system (smile)Continuous Integration
Has the Project Team a clear understanding on the Code Coverage expectations?YesNot Applicable

Code Coverage and Static Code Analysis

Does the Project Team understand the Free and Open Source Software (FOSS) process?YesNo change in open-source usage in this releaseFree and Open Source Software
Is the Project Team willing to fill out accordingly the FOSS table?YesSame as AmsterdamFill out sub-pages for each project under Free and Open Source Software
Is the Project Team willing to comply to the Commit Process?YesSee exampleCommit Messages - we also adjusted the wiki to clearly define the format and operations
Does the Project Team understand the purpose of Code Review?YesSee reviewsCode 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?YesNot ApplicableDevelopment Practices (Jave Coding Style)