Skip to end of metadata
Go to start of metadata

Deliverables for Planning Milestone Checklist Template

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
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 Area

Checkpoint

Response

Supporting Documentation

Notes

Product Management

Are Product Backlog Epics entered in Jira?

Yes



 

Are Product Backlog Stories entered in Jira?

Yes



 

Are Product Backlog Stories linked to Product Backlog Epics?

 Yes



 

Are Product Backlog Stories prioritized?

Yes

 


 

Is the project team ready to estimate the top Stories (for coming Sprint) in Product backlog?

 Yes

 


 

Are Team Members willing to create User Stories/Tasks and associate them with Epics in Jira?”

 Yes

 


Release Management

Is there a Release Planning Template available and completed in wiki?

Yes

Release Planning Template-License

 

 

Have all the "Release Components Name" been defined in your project? (this includes all Sub-Components Names, Sub-Components Repositories Names, Maven Group ID, Sub-Components Description)

Yes

Release Resources

 

 

Have all the "Resources committed to the Release" been defined in your project? This includes First and Last names, LFID, Email Address and Location for PTL, Project Manager, Committers and Contributors.

 Yes

Release Resources

 Expect code contribution from: AT&T, Ericsson, Tech Mahindra, and Orange

 

Have new developers made themselves familiar on the Developer's Guide?

 Yes

 

Acumos Developer's Guide to CI-CD Resources and Processes at the LF

 

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 automation test cases list?

 No

Link to evidence

 need to follow-up with test team

 

Has the Integration Team defined the End 2 End Release Test Cases?

 No

Link to evidence

 need to follow-up with test team

Development

Is the Project Team committed to develop Unit Test?

 Yes

 

 

 

Has the Project Team put in place an Automated Unit Test infrastructure?

 Yes

 

 Plan to follow Acumos infrastructure

 

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

 



Are the Project Team members aware of Continuous Integration Principles (don't break the build, Fix the build,...)?

Yes

 

review developer's guide

 

Has the Project Team a clear understanding on the Code Coverage expectations?

Yes

 

obtain code coverage expectations

 

Is the Project Team willing to comply to the Commit Process?

Yes

 

review developer's guide

 

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 (Java Coding Style)

  • No labels