AAF R4 - M1 Milestone Checklist

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

M1 Release Planning Milestone definition

Practice Area	Checkpoint	Yes/No	Evidence - Comment	How to?

Practice Area	Checkpoint	Yes/No	Evidence - Comment	How to?
Security	Has the Release Security/Vulnerability table been filled out in the protected Security Vulnerabilities wiki space?	Yes	Table in the protected Security Vulnerabilities wiki space corresponds to the latest NexusIQ scan R4 AAF Security/Vulnerability - Full Content
	Have known vulnerabilities (critical and severe) to address/remove in the release been identified with JIRA ticket?	Yes	Note, Shiro has new library release. This may address some Shiro Issues.	AAF-732
	Has the project committed to the release CII badging level?	Yes	Silver	https://bestpractices.coreinfrastructure.org/en/projects/2303
	Has the project created their project CII questionnaire and completed the ONAP level CII requirements	Yes	Silver	https://bestpractices.coreinfrastructure.org/en/projects/2303
	If the project uses java, has the project integrated with the oparent.pom?	Yes	Oparent.pom included in the project
Product Management	Are 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?	Yes	Product Backlog	Work in a Sprint
	Are Product Backlog Stories prioritized?	Yes		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?	Yes		Create 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?	Yes	Dublin Release Platform Maturity	AAF continues to work towards synchronizing with ONAP tools and practices.
Release Management	Is there a Release Planning Template available and completed in wiki?	Yes	Release Planning Template
	Has the Platform Maturity Table been updated with current status and Release goal?	Yes	Dublin Release Platform Maturity	For each Release, there is a Platform Maturity table created for PTLs to record their goals and achievements at M4 (Example: Casablanca Release Platform Maturity).
	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)	Yes	Resources and Repositories (Deprecated)
	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	AAF Resources 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 Testing	Has the Integration Team defined the vendor equipment list?	NA	AAF is software only	AAF deliverable are Microservices
Integration and Testing	Has the Integration Team defined the End 2 End Release Test Case?	NA	Link to evidence
Development	Is the Project Team committed to develop Unit Test?	Yes		AAF has continuous improvement, and one mostly dedicated person, in addition to community help
	Has the Project Team put in place an Automated Unit Test infrastructure?	Yes		CSIT
	Is the Project Team committed to create Continuous System Integration Testing (CSIT) test case?	Yes		CSIT
	Is the Project Team committed to perform Scrum ceremonies?	Yes		AAF has one Team meeting per week for 1 hour. Internal Company Scrum for PTL and contractor is 15 mins a day, which includes ONAP work.
	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		Code Coverage and Static Code Analysis AAF is documentation
	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?	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) AAF is documentation (in .rst)