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?YesProduct BacklogPrioritize a Backlog item
Is the project team ready to estimate the top Stories (for coming Sprint) in Product backlog?YesProduct BacklogEstimate a Backlog item
Is the project team ready to create a 2 weeks Sprint in Jira?YesCurrent SprintCreate a Sprint
Are Team Members willing to create Tasks and associate them with Stories in Jira?YesProduct BacklogCreate a Backlog item
Has the project team plan to contribute to Platform Maturity Improvement?YesBeijing Release Platform Maturity

ExtAPI is not included on the MVP list for the release will not be subject to the minimum recommendation for each maturity category.

Release ManagementIs there a Release Planning Template available and completed in wiki?YesRelease 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)YesResources 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.YesResources and Repositories (Deprecated)
Have new developers made themself familiar on the Onboarding Process?Yes
Onboarding
Is the project team aware of the Release milestone? Any misses will required TSC exception.Yes

Integration and TestingHas the Integration Team defined the vendor equipment list?N/A
ExtAPI has not identified any vendor equipement
Has the Integration Team defined the End 2 End Release Test Case?N/A

ExtAPI is not on MVP, so E2E Test Case is not required

Development



Is the Project Team committed to develop Unit Test?

Yes

Has the Project Team put in place an Automated Unit Test infrastructure?N/A

ExtAPI is not on MVP, so Automated Unit Test is not required

Is the Project Team committed to create Continuous System Integration Testing (CSIT) test case?Yes

Is the Project Team committed to perform Scrum ceremonies?Yes2018 weekly Project meetingsScrum Overview
Are the Project Team members aware of Continuous Integration Principles (don't break the build, Fix the build,...)?Yes
Continuous Integration
Has the Project Team a clear understanding on the Code Coverage expectations?Yes

Code Coverage and Static Code Analysis

Does the Project Team understand the Free and Open Source Software (FOSS) process?Yes
Free and Open Source Software
Is the Project Team willing to fill out accordingly the FOSS table?YesProject FossFill out sub-pages for each project under Free and Open Source Software
Is the Project Team willing to comply to the Commit Process?Yes
Commit Messages
Does the Project Team understand the purpose of Code Review?Yes
Code Review
Is the Project Team aware of the Coding Guidelines?Yes
Development Practices (Jave Coding Style)