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?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?Yesvnfrqts Project Plan

vnfrqts is a Documentation Project.

Beijing release produces additional types of documents to improve useability of ONAP by VNF Providers and others.

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 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
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 evidenceVNFRQTS is a documentation project - no Vendor equipment is required
Has the Integration Team defined the End 2 End Release Test Case?N/ALink to evidenceVNFRQTS is a documentation project - no E2E Release Test case is defined
Development



Is the Project Team committed to develop Unit Test?

N/A
VNFRQTS is a documentation project - no Unit Test case is defined - leverages the LF toolchain maintained by documentation project
Has the Project Team put in place an Automated Unit Test infrastructure?N/A
VNFRQTS is a documentation project - no Unit Test case is defined - leverages the LF toolchain maintained by documentation project
Is the Project Team committed to create Continuous System Integration Testing (CSIT) test case?N/A
VNFRQTS is a documentation project - no Unit Test case is defined - leverages the LF toolchain maintained by documentation project
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,...)?YesVNFRQTS is a documentation project - no Unit Test case is defined - leverages the LF toolchain maintained by documentation projectContinuous Integration
Has the Project Team a clear understanding on the Code Coverage expectations?N/AVNFRQTS is a documentation project - no Unit Test case is defined - leverages the LF toolchain maintained by documentation project

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?N/AVNFRQTS is a documentation project Code Review
Is the Project Team aware of the Coding Guidelines?N/AVNFRQTS is a documentation project Development Practices (Jave Coding Style)