Logging 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

filling out 20180627

Practice Area

Checkpoint

Yes/No

Evidence - Comment

How to?

Practice Area

Checkpoint

Yes/No

Evidence - Comment

How to?

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

yes

Logging Casablanca Scope

Prioritize a Backlog item

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

Yes

yes - during weekly meeting

Estimate a Backlog item

Is the project team ready to create a 2 weeks Sprint in Jira?

Yes

yes - during weekly meeting

Create a Sprint

Are Team Members willing to create Tasks and associate them with Stories in Jira?

Yes

yes, off existing stories, epics

Create a Backlog item

Has the project team plan to contribute to Platform Maturity Improvement?

Yes

Logging Casablanca M1 Release Planning#PlatformMaturity



Release Management

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

Yes

Logging Casablanca M1 Release Planning



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)

No

(in-progress)

Resources and Repositories (Deprecated)#LoggingEnhancements

In progress off of closing off 2 naming issues for POMBA in

LOG-192: POMBA: Architecture/seed-code/deployment/review - Scope changeClosed

CIMAN-169: POMBA/Logging: 6 new repos for 6 containersDone



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

but pending

POMBA

Resources and Repositories (Deprecated)

Resources and Repositories (Deprecated)#LoggingEnhancements



Have new developers made themself familiar on the Onboarding Process?

Yes

(3 active, 6+ pending)

I have communicated also via LOG-192

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?

N/A

Link to evidence



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

N/A

Link to evidence



Development




Is the Project Team committed to develop Unit Test?

yes





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

yes

https://git.onap.org/logging-analytics/tree/reference/logging-slf4j

pomba as it gets committed



Is the Project Team committed to create Continuous System Integration Testing (CSIT) test case?

no

in-progress

both for logging and pomba



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

80+% currently

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?

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)