| Best practice | Outcome(s) |
|---|
| BP-A.1: Identify stakeholders | A prioritised list of stakeholders |
| BP-A.2: Establish communications with stakeholders | Communication structure and channels |
| BP-A.3: Collect requirements | Requirements |
| BP-B.1: Assess available technologies | Current technologies |
| BP-B.2: Set up documentation | Documentation |
| BP-B.3: Manage artifacts | Artifact versioning |
| BP-B.4: Automate build & delivery | Automation, scripts |
| BP-B.5: Manage product issues | Issue tracker |
| BP-B.6: Manage sideground IPR | IPRs |
| BP-C.1: Manage risks | List of risks |
| BP-C.2: Identify product success criteria | Success criteria |
| BP-C.3: Implement a quality plan | A quality plan, approach and test cases |
| BP-C.4: Verify outcomes | Artifacts are verified |
| BP-C.5: Monitor quality | Quality monitoring plan |
| BP-C.6: Validate the product with stakeholders | Stakeholders validate product |
| BP-C.7: Refine the quality assurance process | QA is constantly reviewed and optimized |
| BP-D.2: Establish internal comms | In-project communication channels |
| BP-D.3: Implement a decision-making process | In-project decision-making process |
| BP-D.4: Manage team assignments | Team schedule and assignment plan |
| BP-E.1: Design for maintainability | Maintainability is included into product |
| BP-E.2: Manage maintenance issues | Maintenance issues are identified |
| BP-E.3: Implement a change request process | Change request process |
| BP-E.4: Define a change implementation procedure | Change implementation plan |
