Version v2.1.4 rev-87b1c37bc7e35b1aa0790026963f651232af4404
Print | Close Introduction

Outcomes are at the center of HERMES. Outcomes are allocated to tasks and roles. Interrelated outcomes are grouped into modules.

An outcome can be a document that has been based on a document template, such as a project charter or a business process description.

However, an outcome can also be a new state of an existing outcome, such as Operating Infrastructure Implemented or IT System Activated.

Project outcomes do not necessarily have to be only technical outcomes such as IT applications. A project outcome can often also mean trained users and the activated organization with its processes.  This systemic view results in a comprehensive system at the end of a project consisting of several elements.

The figure below shows an example of a project and its outcomes.

 

Overview of Outcomes

The table below shows the outcomes for each module and the partners involved. 

HERMES defines minimum outcomes which are required in order to meet the requirements of governance. The list not only comprises outcomes to be examined by the auditors but the "must haves", i.e. the outcomes which are essential for a module. Minimum outcomes are essential elements in guaranteeing the success of a project. If a module is not relevant to particular project, the defined minimum outcomes become obsolete.

The list of minimum outcomes reflects the general project situation without taking into account the special characteristics of an individual project.  

Module Outcome User Developer Operator
Agile Development Checklist X
Increment X*
Minutes X
Product Backlog X* X*
Project Decision Management / Execution X*
Project Management Plan X*
Release Plan X X X
Sprint Backlog X* X*
Deployment Organization Acceptance Report X* X* X*
Checklist X
Deployment Concept X* X*
Deployment Measures and Organization Implemented X X
Deployment Measures Executed X X
Project Decision Management / Execution X*
Project Decision Steering X* X* X*
Information Security and Data Protection Checklist X
ISDP Measures X* X* X*
ISDS Concept X* X* X*
Project Decision Management / Execution X*
IT Migration Acceptance Report X* X* X*
Checklist X
Detail Specifications X X
Legacy System Decommissioned X X X
Migration Concept X* X*
Migration Executed X X X
Migration Procedure X
Project Decision Management / Execution X*
IT Operation Agreement X
Operating Concept X* X*
Operating Infrastructure Implemented X
Operating Manual X*
Operation Activated X X
Operational Structure Implemented X
System Integrated X
IT System Checklist X
Detailed Study X X
Detail Specifications X X
Integration and Installation Instructions X
Integration Concept X X X
Interfaces Implemented X
Project Decision Management / Execution X*
Prototype Developed X
Prototype Documentation X
Situation Analysis X X
System Activated X X X
System Architecture X* X*
System Developed / Parameterized X
System Requirements X* X*
User Manual X X
Organizational Structure Concept for Organizational Structure X*
Description of the Organization X*
Organizational Structure Activated X
Organization Realized X
Process Description X*
Procurement Agreement X
Checklist X
Evaluation Report X*
Minutes X
Offer X* X*
Project Decision Steering X* X* X*
Project Management Plan X*
Publication X*
Tender Documentation X*
Product Product Activated X
Product Concept X*
Product Documentation X*
Product Implemented X
User Manual X X
Project Foundations Analysis of Legal Framework X*
Protection Needs Analysis X*
Study X* X*
Project Management Agreement X
Amendment Request X* X*
Change Status List X*
Checklist X
Enquiry X
Evaluation Report X*
Final Project Evaluation X*
Inspection Report X
Lessons Learned X
Minutes X
Phase Report X*
Project Charter X*
Project Decision Management / Execution X*
Project Management Plan X*
Project Status Report X*
Stakeholder List X* X*
Work Order X
Project Steering Checklist X
Project Charter X*
Project Decision Steering X* X* X*
Project Initiation Order X*
QA and Risk Report X
Testing Minutes X
Test Concept X* X* X*
Test Data X X
Test Report X* X* X*
Test System X

* Minimum outcomes required

Outcome Descriptions

Explanation of Outcome Description

Every outcome has an outcome description.

All outcome descriptions have the same structure:

  • Description: Creates fundamental understanding of the outcome
  • Content: Describes the content of a document
  • Relationships (online version only): Shows how an outcome relates to modules, roles, and tasks

For many outcomes, there are one or more document templates available. They provide greater detail for the outcome descriptions and are a specific resource in the application of HERMES. The document templates can be adapted to meet the needs of an organization.

There are two cases where no document templates are available:

  • The outcome describes a state, e.g. Product Implemented, or Operation Activated
  • If a document template is specific to a project, or if it is set by the core organization, for instance User manual or agreements