Portal Platform Deliverables for Planning Milestone Checklist (Beijing Release)
- Former user (Deleted)
- Manoop Talasila
This checklist is expected to be completed for the project to pass the M1 Release Planning Milestone.
Usage
Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
Fill out the Yes/No column
Provide link to evidence (when necessary)
Practice Area | Checkpoint | Yes/No | Evidence - Comment | How to? |
|---|---|---|---|---|
Product Management | Are Product Backlog Epics entered in Jira? | Yes | Getting issues... | |
Are Product Backlog Stories entered in Jira? | Yes | Getting issues... | ||
Are Product Backlog Stories linked to Product Backlog Epics? | Yes | |||
Are Product Backlog Stories prioritized? | Ongoing | |||
Is the project team ready to estimate the top Stories (for coming Sprint) in Product backlog? | Yes | |||
Is the project team ready to create a 2 weeks Sprint in Jira? | TBD | |||
Are Team Members willing to create Tasks and associate them with Stories in Jira? | Yes | |||
Release Management | Is there a Release Planning Template available and completed in wiki? | Yes | ||
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) | Need to finish | |||
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 | |||
Have new developers made themself familiar on the Onboarding Process? | Yes | The committers will direct new developers to the wiki for details. | ||
Is the project team aware of the Release milestone? Any misses will required TSC exception. | Yes | |||
Integration and Testing | Has the Integration Team defined the vendor equipment list? | N/A | Link to evidence | |
Has the Integration Team defined the End 2 End Release Test Case? | N/A | Link to evidence | We are working with the Integration Project to clarify the details for E2E testing. | |
Development | Is the Project Team committed to develop Unit Test? | Yes | We will meet the 50% code coverage standards and static code analysis as recommended for maturity guidelines. | |
Has the Project Team put in place an Automated Unit Test infrastructure? | Yes | We 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? | Yes | These details need to be worked out amongst the contributors and committers. | ||
Are the Project Team members aware of Continuous Integration Principles (don't break the build, Fix the build,...)? | Yes | The committers will ensure all code commits do not break the build. | ||
Has the Project Team a clear understanding on the Code Coverage expectations? | Yes | The committers will screen all commits to ensure the code coverage %'s are met. | ||
Does the Project Team understand the Free and Open Source Software (FOSS) process? | Yes | |||
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? | Yes | The committers will require incoming code submissions adhere to guidelines. | ||
Does the Project Team understand the purpose of Code Review? | Yes | |||
Is the Project Team aware of the Coding Guidelines? | Yes | Development Practices (Jave Coding Style) | ||