...
| Item | Guidance | Practices |
| Problem statement and objectives | A clear description of the nature of the problem or opportunity the product/service is trying to address and the objectives of the project in addressing it. |
|
| Users | Who are the users of this service? | |
| Benefits | What are the benefits for the user in using the service? Why would a user use the service? | N/A - business-oriented |
| Service description | A functional description of what the service is. | |
| Market analysis | Define how the proposed product/service differs from other offerings that are available (if any). | N/A - business-oriented |
| Costs | A specification of costs. Depending on the scale and cost of the development, a detailed business case estimation of the costs and (if applicable) revenues should be produced based on the available template. | N/A - non-software-related management |
| Funding | The project should demonstrate that funding is available to cover the foreseen costs or estimate any additional funding required. | N/A - non-software-related management |
| Roadmap | A high-level roadmap showing the key functional and non-functional developments during the project. | ADD |
| Planning | A plan showing the overall timescale with effort requirements and milestones for the whole project. | ADD |
| Resources | The necessary resources should have been identified and be available to allow development to begin. |
...
| Item | Guidance | Practices |
| Service definition | This point covers documentation across the development: everything from marketing materials, service descriptions and operational support arrangements. | N/A |
| Code quality | Security and quality code audits must be successfully completed (e.g., specialist software support resources) in order for a service/product to qualify for production. | |
| Marketing and visibility | This includes marketing content and a plan to promote the new service to increase uptake and explain how marketing activities will help in this increase. Also, investigate ways to make it easier for potential users to test or trial your service. | |
| Service policy | Who can use the service and what, if any, are the costs? This could involve governance outside of the PMO, e.g., the Cost Sharing Committee. | N/A |
| IPR | A check of the code to estimate any risks if a public release is planned. |
|
| GDPR | Even a website needs a privacy statement, further work is required if the service requires personal information. | ADD |
| Operational support | This point covers items such as:
|
|
| Roadmap | Is there a roadmap for the next 12 months? | ADD? |
| KPIs | What key performance indicators have been defined, and what are their expected values for which period of time (for example service uptake)? For software-only services include how you plan to measure usage. | ADD? |
...