Mandate

Responsible authority

Background

Objectives

When baseline data is shared by several initiatives, then those initiatives can make use of it for improved two-way communication with their stakeholders.

Stakeholders can in one place share their insights on their situation, and validate or comment upon related assumptions by project participants.

Advocates of new initiatives for a particular area can via the baseline identify the ongoing initiatives. This will help them in avoiding double or parallel work, or in identifying prior work or resources on which they could build.

Scope

The actors, processes and resources in a delineated socio-technical area.

Constraints

Fact finding and documentation may be constrained by certain factors. These can be described here.

Interfaces

To other baselines and to initiatives making use of the baseline.

User's quality expectations

Here one could express the quality levels that are anticipated in the baseline work. As more or higher-cost initiatives are relying upon the baseline, then a higher quality can be expected.

Outline of the business case

The reason for a baseline outside of a project is that baseline facts are often of value to multiple initiatives (programmes and projects). If each of these initiatives — singly and severally — gathers baseline data, then the quality of the baseline data may suffer.

Baseline tolerances

Tolerances could be related to quality level, delivery time, scope and level of detail.

Key roles

Who will be the executive and project manager?

Who is providing funding, who are the users, any other known interested party.


bg.gif
cs.gif
da.gif
de.gif
et.gif
el.gif
en.gif
es.gif
fr.gif
ga.gif
it.gif
lv.gif
lt.gif
hu.gif
mt.gif
nl.gif
pl.gif
pt.gif
ro.gif
sk.gif
sl.gif
fi.gif
sv.gif
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License