Skip to end of metadata
Go to start of metadata

This checklist is expected to be completed for the project to pass the M1 Release Planning Milestone.

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

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?Ongoing
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?TBD
Create a Sprint
Are Team Members willing to create Tasks and associate them with Stories in Jira?Yes
Create a Backlog item
Release ManagementIs there a Release Planning Template available and completed in wiki?YesPortal Platform M1 Release Planning (Beijing Release)
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)Need to finishResources 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?YesThe committers will direct new developers to the wiki for details.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 evidenceWe are working with the Integration Project to clarify the details for E2E testing.




Development



Is the Project Team committed to develop Unit Test?

YesWe will meet the 50% code coverage standards and static code analysis as recommended for maturity guidelines.Code Coverage and Static Code Analysis
Has the Project Team put in place an Automated Unit Test infrastructure?YesWe will be using JUnit as the majority of our code is Java.
Is the Project Team committed to create Continuous System Integration Testing (CSIT) test case?

No

(No resources, so it depends on the community help)

The seed code currently is integrated with the Robot Framework. We will ensure we work with the Integration Project to evolve those tests for the release.
Is the Project Team committed to perform Scrum ceremonies?YesThese details need to be worked out amongst the contributors and committers.Scrum Overview
Are the Project Team members aware of Continuous Integration Principles (don't break the build, Fix the build,...)?YesThe committers will ensure all code commits do not break the build.Continuous Integration
Has the Project Team a clear understanding on the Code Coverage expectations?YesThe committers will screen all commits to ensure the code coverage %'s are met.

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?Yes
Fill out sub-pages for each project under Free and Open Source Software
Is the Project Team willing to comply to the Commit Process?YesThe committers will require incoming code submissions adhere to guidelines.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)