MUSIC Deliverables for Planning Milestone Checklist

Practice Area	Checkpoint	Yes/No	Evidence - Comment	How to?
Product Management	Are Product Backlog Epics entered in Jira?	NA		Create a Backlog item Difference between a Product and Sprint Backlog
	Are Product Backlog Stories entered in Jira?	NA		Create a Backlog item
	Are Product Backlog Stories linked to Product Backlog Epics?	NA	https://jira.onap.org/secure/RapidBoard.jspa?rapidView=99&projectKey=OPTFRA&view=planning.nodetail&epics=visible	Work in a Sprint
	Are Product Backlog Stories prioritized?	NA		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?	NA		Create a Sprint
	Are Team Members willing to create Tasks and associate them with Stories in Jira?	NA		Create a Backlog item
	Has the project team plan to contribute to Platform Maturity Improvement?	Yes	OOF Beijing Release Planning
Release Management	Is there a Release Planning Template available and completed in wiki?		OOF Beijing Release Planning
	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)	Yes	Resources 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.	Yes	Resources and Repositories. Will request the contributors to add their LF ID and email, if not already present.
	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 Testing	Has the Integration Team defined the vendor equipment list?		Not applicable
Integration and Testing	Has the Integration Team defined the End 2 End Release Test Case?	No	This is work in progress.
Development	Is the Project Team committed to develop Unit Test?	Yes
	Has the Project Team put in place an Automated Unit Test infrastructure?	No
	Is the Project Team committed to create Continuous System Integration Testing (CSIT) test case?	Yes
	Is the Project Team committed to perform Scrum ceremonies?	Yes		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?	Yes	Since the seed-code is being on-boarded as a part of Beijing release, we plan to reach 30% code coverage in R2, with a stretch goal of 50% code coverage.	Code Coverage and Static Code Analysis
	Does the Project Team understand the Free and Open Source Software (FOSS) process?	Yes	As a part of the seed-code upstreaming, this list will be produced.	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?	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	OOF/HAS is primarily a Python project. The coding guidelines used in the see code are in compliance with those used in OpenStack.	Development Practices (Jave Coding Style)