Outcomes are at the heart of HERMES. Outcomes are assigned to tasks and roles. Content-related outcomes are grouped into modules.

An outcome can be a document that was drafted on the basis of a document template such as a project order, a business process description.

However, an outcome can also be a new state of an existing outcome, e.g. "operating infrastructure realized" or "IT system activated".

In many cases, project outcomes are not only technical outcomes such as IT applications. The project outcome often also consists of trained users and the activated organization with its processes. This systemic point of view results in a comprehensive system consisting of several elements being activated at the end of the project.

Figure 24 shows the course of the project with sample outcomes.

Figure 6: Outcomes are at the heart of HERMES
Figure 6: Outcomes are at the heart of HERMES

Outcome overview

HERMES defines the minimum outcomes required to meet governance requirements. The following table contains not only those outcomes that must be checked by the auditors, but also all those that must be produced in a module as a "must have". The minimum outcomes are the safeguards for ensuring the project's success. If a module is not relevant for the project, the minimum outcomes defined in it are also dropped.

The list of minimum outcomes reflects a general project situation without going into the special features of the individual projects.

The table shows the outcomes per module and the partners involved.

TableĀ 47: Outcomes per module and partners involved
Module Outcome User Developer Operator
Project steering Checklist
Project order X*
Project decision steering X* X* X*
Project initiation order X*
QA and risk report
Project management Change request X* X*
Change status list X*
Work order
Evaluation report X*
Quote request
Phase report X*
Review report
Project order X*
Project decision management & execution X*
Lessons learned
Project management plan X*
Final project evaluation X*
Project status report X*
Stakeholder Interests
Stakeholder list X* X*
Agile development Checklist
Increment X*
Product backlog X* X*
Project decision management & execution X*
Project management plan X*
Release plan
Sprint backlog X* X*
Project foundations Legal basis analysis X*
Protection needs analysis X*
Study X* X* X*
Business organization Business organization activated
Business organization concept X* X*
Organization implemented
Organization description X* X*
Process description X* X*
Product User manual
Product activated
Product realized
Product documentation X*
Product concept X* X*
IT system User manual
Detailed specifications
Detailed study
Integration and installation instructions
Integration concept
Project decision management & execution X*
Prototype realized
Prototype documentation
Interfaces realized
Situation analysis
System activated
System developed or parameterized
System requirements X* X* X*
System architecture X* X* X*
Procurement Offer X* X* X*
Tender documentation X*
Evaluation report X*
Project decision steering X* X* X*
Project management plan X*
Publication X*
Deployment organization Acceptance report X* X* X*
Deployment concept X* X*
Deployment measures carried out
Deployment measures and organization realized
Project decision management & execution X*
Project decision steering X* X* X*
Testing Minutes
Test data
Test concept X* X* X*
Test report X* X* X*
Test system
IT migration Acceptance report X* X* X*
Legacy system decommissioned
Detailed specifications
Migration carried out
Migration concept X* X* X*
Migration procedure
Project decision management & execution X*
IT operation Operation activated
Operating manual X*
Operating infrastructure realized
Operating concept X* X* X*
Operating organization realized
System integrated
Information security and data protection Checklist
ISDP concept X* X* X*
ISDP measures X* X* X*
Project decision management & execution X*

Outcome descriptions

Explanation regarding outcome description

For each outcome, there is a description of the outcome that is always structured in the same way:

  1. Description
    creates a fundamental understanding of the outcome
  2. Content
    describes the content of a document
  3. Relationships (only available online)
    shows how the outcome relates to modules, roles and tasks
  4. Document template (only available online)
    A document template is available for some outcomes. It elaborates on the outcome descriptions and is a concrete aid for the application of HERMES. The document templates can be adapted to the needs of the organization.

There are two cases where no document templates are available:

  1. The outcome describes a state, e.g.
    1. Product realized
    1. Operation activated
  2. The document template is project-specific or prescribed by the core organization, e.g.
    1. User manual
    1. Agreements

Outcome directory

  1. Acceptance report
  2. Legacy system decommissioned
  3. Change request
  4. Change status list
  5. Offer
  6. User manual
  7. Work order
  8. Tender documentation
  9. Operation activated
  10. Operating manual
  11. Operating infrastructure realized
  12. Operating concept
  13. Operating organization realized
  14. Checklist
  15. Detailed specifications
  16. Detailed study
  17. Deployment concept
  18. Deployment measures carried out
  19. Deployment measures and organization realized
  20. Evaluation report
  21. Business organization activated
  22. Business organization concept
  23. Increment
  24. Integration and installation instructions
  25. Integration concept
  26. ISDP concept
  27. ISDP measures
  28. Migration carried out
  29. Migration concept
  30. Migration procedure
  31. Quote request
  32. Organization implemented
  33. Organization description
  34. Phase report
  35. Product backlog
  36. Product activated
  37. Product realized
  38. Product documentation
  39. Product concept
  40. Project order
  41. Lessons learned
  42. Project initiation order
  43. Project management plan
  44. Final project evaluation
  45. Project status report
  46. Minutes
  47. Prototype realized
  48. Prototype documentation
  49. Process description
  50. Review report
  51. Publication
  52. QA and risk report
  53. Legal basis analysis
  54. Release plan
  55. Interfaces realized
  56. Protection needs analysis
  57. Situation analysis
  58. Sprint backlog
  59. Stakeholder Interests
  60. Stakeholder list
  61. Study
  62. System activated
  63. System developed or parameterized
  64. System integrated
  65. System requirements
  66. System architecture
  67. Test data
  68. Test concept
  69. Test report
  70. Test system
  71. Agreement