Initiative / Release

Permissions

View basic data

Here is the needed permission to display the basic data of an Initiative/Release:

  • The user has the permission PORTFOLIO_ENTRY_VIEW_DETAILS_ALL_PERMISSION, or
  • The user has the permission PORTFOLIO_ENTRY_VIEW_PUBLIC_PERMISSION and the Initiative/Release is public and not a concept, or
  • The user has the permission PORTFOLIO_ENTRY_VIEW_DETAILS_AS_MANAGER_PERMISSION and he is the manager of the Initiative/Release, or
  • The user has the permission PORTFOLIO_ENTRY_VIEW_DETAILS_AS_STAKEHOLDER_PERMISSION and he is a stakeholder of the Initiative/Release or of a portfolio of the Initiative/Release, or
  • The user has the permission PORTFOLIO_ENTRY_VIEW_DETAILS_AS_PORTFOLIO_MANAGER_PERMISSION and he is the manager of a portfolio of the Initiative/Release

View complete data

Here is the needed permission to display the complete data of an Initiative/Release:

  • The user has the permission PORTFOLIO_ENTRY_VIEW_DETAILS_ALL_PERMISSION, or
  • The user has the permission PORTFOLIO_ENTRY_VIEW_DETAILS_AS_MANAGER_PERMISSION and he is the manager of the Initiative/Release, or
  • The user has the permission PORTFOLIO_ENTRY_VIEW_DETAILS_AS_STAKEHOLDER_PERMISSION and he is a stakeholder of the Initiative/Release or of a portfolio of the Initiative/Release, or
  • The user has the permission PORTFOLIO_ENTRY_VIEW_DETAILS_AS_PORTFOLIO_MANAGER_PERMISSION and he is the manager of a portfolio of the Initiative/Release

Update

Here is the needed permission to update (add, edit or interact) an Initiative/Release:

  • The user has the permission PORTFOLIO_ENTRY_EDIT_ALL_PERMISSION, or
  • The user has the permission PORTFOLIO_ENTRY_EDIT_AS_MANAGER_PERMISSION and he is the manager of the Initiative/Release, or
  • The user has the permission PORTFOLIO_ENTRY_EDIT_AS_PORTFOLIO_MANAGER_PERMISSION and he is the manager of a portfolio of the Initiative/Release

This permission is not used for the deletion of an Initiative/Release. All other deletions (for example delete a Stakeholder) use this permission.

Delete

Here is the needed permission to delete an Initiative/Release:

  • The user has the permission PORTFOLIO_ENTRY_DELETE_ALL_PERMISSION

The sidebar is displayed on each page of the Initiative/Release(the current page is highlighted). It contains all links to reach all data, and depends of the User's permissions.

Link Description Permission
Overview Dashboard with KPIs and more relevant information View complete data
Details Full description of the Initiative/Release including attachments View basic data
Financials (Details, Status) All financial information see financial permissions
Stakeholders List of stakeholders and Portfolio's stakeholders View basic data
Governance List of Milestones with planned date and status View complete data
Delivery (Deliverables, Requirements, Requirements status, Iterations) All information about the delivery part of the Initiative or Release. Note: Iterations menu is not available for Release. View complete data
Planning (Overview, Packages, Resources) Planning Packages with the capability to allocate Resources (Employees, Org Units and Competencies). View complete data
Status reporting (Status registers, Events, Timesheets) Status Reports, Risks, Issues, Events and Timesheets View complete data
Plugins (under Integration menu) Lists of activated and available plugins with configuration capabilities. Update
Partner syndication (under Integration menu) List of Agreement relations. Update

Attributes

An Initiative or Release has the following set of attributes:

Field Description
Confidential A confidential Initiative/Release is displayed only for authorized Users. A “closed eye” icon is displayed in the breadcrumb.
Active An inactive (also called archived) Initiative/Release is usually not displayed in the BizDock lists. An “archived” icon is displayed in the breadcrumb.
OPEX by default Default expenditure type of the Initiative/Release. Available only if the effort-based budget/forecast is enabled in System preferences. This flag is used when generating budget/forecast from an allocated resource that hasn't a Planning Package.
Concept A concept is a non-started project. A “concept” icon is displayed in the breadcrumb.
Name Name of the Initiative/Release.
Description Description of the Initiative/Release.
Type A type used to categorize the Initiative/Release.
A type also defines the possible Stakeholder roles.
Governance ID A free identifier.
ERP ref ID The identifier that is used in external financial tools.
Initiative manager The manager of the Initiative/Release.
Sponsoring unit The sponsoring unit of the Initiative/Release.
A sponsoring unit is an Organizational Unit with “Can sponsor” checked.
Delivery unit(s) An Initiative/Release can have many delivery units.
A delivery unit is an Organizational Unit with “Can deliver” checked.

Identity card

Overview

A KPI box is gray if it doesn't contain values and the coloring rules could be updated in the KPI Manager.

The Initiative/Release overview page is composed by:

  • List of KPI boxes:
Name Description Default coloring rules
Risks & Issues Numbers of active Risks and Issues. Blue in all cases.
Employees Sum of days of the allocated Employees. Red if none is confirmed, Amber if at least one is confirmed (but not all), Green if any are confirmed.
Allocation requests Sum of days of the allocated Org Units and Competencies. Red if none is confirmed, Amber if at least one is confirmed (but not all), Green if any are confirmed.
Open story points Sum of story points for the open Needs. Blue in all cases.
Open requirements Number of open Requirements. Blue in all cases.
Open defects Number of open defects. Red if at least one is blocker, Amber if at least one is existing, Green if no open defect.
In-scope requirements Number of in-scope requirements. Red if at least one non-scoped, Green if all in-scope.
Progress Estimated value of the Initiative/Release's progression based one the Packages, the full description of this KPI is given below. See below
Release burndown Remaining, made and estimated efforts of the Initiative/Release requirements (all values are given in man days). For Release only: the trend chart contains also a theoretical line which represents a linear distribution of the release capacity from the start to the end implementation (note: the estimated effort line is not represented). The implementation start and end dates correspond to specific governance milestones. Blue in all cases.
Deviation CAPEX Budget and forecast CAPEX totals with the related deviation (see the financial page for computation details). This KPI is displayed only if the user has the financial "view" permission. Red if the deviation is greater than 10, Amber if the deviation is positive but less than 10, Green if the deviation is 0 or negative.
Deviation OPEX Budget and forecast OPEX totals with the related deviation (see the financial page for computation details). This KPI is displayed only if the user has the financial "view" permission. Red if the deviation is greater than 10, Amber if the deviation is positive but less than 10, Green if the deviation is 0 or negative.
  • Milestones trend: the evolution of the planning and of the resource values (allocation, budget) according to the milestones' approvals. By clicking on a row, the full status at the approvement date is detailed.
  • Latest status report: last recorded report with its status
  • Next milestones: List of all non-accepted Milestones

Progress KPI

This KPI is based on the Packages of the Initiative/Release.

A Package could have 3 status:

  • Not started
  • On-going
  • Closed

The progression of a Package depends of its status:

  • Not started: 0%
  • On-going: X%, where X is a common value that is stored as a preference system
  • Closed: 100%

For sure X is an approximation. It make sense and converge to the reality only when the progression is computed for a large enough set of Packages.

The definitions of the KPI values are:

  • Main value: an estimated progression value of the Initiative/Release in percent
  • Additional1 value: an estimation of expected consumed days, meaning “at this moment - given the initial estimations of allocated resources - we should have consumed this number of days”
  • Additional2 value: the real value of consumed days, meaning “at this moment the Employees have timesheeted this number of days”

Here are the detailed calculations:

Main value = ((sum(days of allocated resources associated to a "On-going" Package) * X% + sum(days of allocated resources associated to a "Closed" Package)) / sum(days of all allocated resources associated to a Package)) * 100
Additional1 value = sum(days of allocated resources associated to a "On-going" Package) * X% + sum(days of allocated resources associated to a "Closed" Package)
Additional2 value = sum(timesheeted days of all Packages)

An allocated resource is either an Employee or an Org Unit or a Competency.

The coloring rules are based only on additional values. Here are the explainations:

  • Green: the expected consumed days is greater than the real consumed days
  • Amber: the real consumed days is greater than the expected consumed days but not more than 15%,
  • Red: else

Details

The Initiative/Release details page is composed by:

  • The attributes (standard and custom)
  • List of Portfolios
  • List of Dependencies
  • List of Attachment documents: click on the icon to download one

Data management

Edit an Initiative/Release

  1. Go to the details page of an Initiative/Release,
  2. Click on the “Edit” icon in the details table,
  3. Modify the attributes and Save,
  4. The data have been updated.

Delete an Initiative/Release

  1. Go to the details page of an Initiative/Release,
  2. Click on the “Delete” icon in the details table,
  3. Confirm that you want to delete the entry. An Initiative/Release can not be restored once deleted. If you delete one by error, you will have to re-create it.
  4. The entry is deleted.

Edit the Portfolios

  1. Go to the details page of an Initiative/Release,
  2. Click on the “Edit” icon in the Portfolios table,
  3. Check / uncheck the Portfolios and Save
  4. The selected Portfolios have been updated.

Add a Dependency

  1. Go to the details page of an Initiative/Release,
  2. Click on the “Add” icon inside the Dependencies table,
  3. Select a type and the related entry,
  4. Click on Save,
  5. Both entries are now dependent.

Delete a Dependency

  1. Go to the details page of an Initiative/Release,
  2. Click on the “Delete” icon inside the Dependencies table for the wished Dependency,
  3. Confirm that you want to delete the Dependency,
  4. The Dependency is deleted.

Add a Document

  1. Go to the details page of an Initiative/Release,
  2. Click on the “Add” icon inside the attachment documents table,
  3. Select a file from the computer and Save,
  4. The Document is now available.

Delete a Document

  1. Go to the details page of an Initiative/Release,
  2. Click on the “Delete” icon inside the attachment documents table for the wished Document,
  3. Confirm that you want to delete the Document. A Document can not be restored once deleted. If you delete one by error, you will have to re-create it.
  4. The Document is deleted.