...
| Practice Area | Checkpoint | Yes/No | Evidences | How to? | |
|---|---|---|---|---|---|
| Architecture | Has the Project team reviewed the APIs with the Architecture Committee (ARC)?Architecture walkthrough to understand how each project contributes on Release Use Case. ARC to organize the walkthrough. | N/A | OOM provides no APIs. | ||
| Is there a plan to address the findings the API review? | Link to plan | The plan could be as simple as a Jira issue to track the implementation of findings or a documented plan within the wikiN/A | OOM provides no API's. | ||
| Does the team clearly understand that no changes in the API definition is allowed without formal TSC review and approval? | Yes | NAIn the case some changes are necessary, bring the request to the TSC for review and approval | OOM provides no API's. | ||
Is there any changes in the scope, functionalities, deliverable, dependency, resources, API, repositories since M1 milestone? | If Yes, please a link to the evidence of these changes. | Critical point to understand is that change is inevitable, and that right timing and clear communication to the community will ease the process of accepting changes. | No | ||
| Provide link to the API Documentation. | N/A | OOM Provides no API's | |||
| Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | Provide Link to Project backlogYes | Stories are marked done as completed | ||
| Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | Yes | Tasks are marked done as completed | |||
| Have all findings from previous milestones been addressed? | Provide link to JIRA findings | ||||
| Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | Goal: 50% for Incubation project in Beijing | Guidance on Code Coverage and Static Code AnalysisTools: SonarN/A | Helm/Kubernetes do not have unit tests and is not supported by Sonar. See Sonar OOM Results | |
| Is there any pending commit request older than 36 Business hours in Gerrit? | |||||
Do you have a plan to address by M4 the Critical vulnerabilities in the third party libraries used within your project? | Ensure by M4 the Nexus-IQ report from “Jenkins CLM” shows 0 critical security vulnerability. Open the Nexus-IQ report for the details on each repo. | ||||
| Are all the Jenkins jobs successfully passed ( Merge-Jobs)? | Provide link to evidence | ||||
| Are all binaries available in Nexus?Provide link to evidence | No | Blocked waiting on See Casablanca Risks # 6. | |||
| Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? | Provide link to evidence | |||
| Has the project code successfully passed the Daily Build process?Goal is to ensure the latest project commit has not broken the Integration Daily Build | Yes | OOM CD Jenkins Jobs |
