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

Usage

  1. Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
  2. Fill out the Yes/No column
  3. Provide link to evidence (when necessary)


Practice AreaCheckpointYes/NoEvidence - CommentHow to?
Product ManagementAre Product Backlog Epics entered in Jira?Yes

Create a Backlog item

Difference between a Product and Sprint Backlog

Are Product Backlog Stories entered in Jira?Yes

Additional stories need to be created

Create a Backlog item
Are Product Backlog Stories linked to Product Backlog Epics?Yes
Work in a Sprint
Are Product Backlog Stories prioritized?YesPrioritization is based on EpicsPrioritize a Backlog item
Is the project team ready to estimate the top Stories (for coming Sprint) in Product backlog?No
Estimate a Backlog item
Is the project team ready to create a 2 weeks Sprint in Jira?YesCompletedCreate 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?YesUsability Initiatives for Beijing (Release 2)
Release ManagementIs there a Release Planning Template available and completed in wiki?YesRelease Planning Template - Doc Beijing Release (R2)
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#Documentation
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#Documentation
Have new developers made themselves 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/ALink to evidence
Has the Integration Team defined the End 2 End Release Test Case?N/ALink to evidence
Development



Is the Project Team committed to develop Unit Test?

N/A

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

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

Is the Project Team committed to perform Scrum ceremonies?N/A
Scrum 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?N/A

Code Coverage and Static Code Analysis

Does the Project Team understand the Free and Open Source Software (FOSS) process?N/A
Free and Open Source Software
Is the Project Team willing to fill out accordingly the FOSS table?N/A
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
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)