The delivery area of an Initiative/Release displays its Deliverables, Requirements and Iterations.
A Deliverable represents everything that could be delivered. It is owned by an Initiative/Release and followed by any others.
A Deliverable has the following set of attributes:
|Name||The name of the Deliverable|
|Description||The description of the Deliverable|
|Delegated||A delegated Deliverable is managed by another Initiative/Release. If this flag is true then the current Initiative/Release is simply a follower of the Deliverable, else it is the owner.|
|Owner||Only if Deliverable is delegated. The owner is the Initiative/Release that manages the Deliverable.|
|Package||The possible planning Package. Note: the Package is depending of the Initiative/Release, meaning if a same Deliverable is associated to many Initiatives/Releases then a Package could be defined for each Initiative/Release.|
List of Deliverables
The list of Deliverables is a sortable and filterable table. It's also possible to hide and show columns.
By clicking on a Requirement, its identity card is displayed.
The following table describes the possible action:
|Action||Owner (not delegated)||Follower (delegated)|
|Edit all attributes of the Deliverable.||Edit the Package and custom attributes of the Deliverable.|
|Delete definitively the Deliverable.||-|
|-||Unfollow the Deliverable.|
Identity card of a Deliverable
The identity card of a Deliverable contains:
- The list of attributes
- The associated requirements
The attribute “Owner” is displayed only for a delegated Deliverable.
The associated Requirements list is a subset of all available Requirements in the Deliverable owner. This is possible to modify the association only if the Deliverable is owned by the current Initiative/Release (meaning it is not delegated): to do this simply click on the icon inside the Requirements' panel.
All Requirements of the Initiative/Release are displayed, the associated are checked.
There are 2 kinds of requirements:
- Needs: describes all the required functionalities of an Initiative/Release
- Defects: describes all the problems of an Initiative/Release
A Requirement is either provided externally (for example with a plugin) or directly created in BizDock.
A Requirement has the following set of attributes:
|Defect||Settled to true if the Requirement is a Defect, else it is a Need|
|External ref ID||The external ref ID of the requirement. Only for external Requirement.|
|Name||The name of the Requirement|
|Description||The description of the Requirement|
|Category||The category of the Requirement|
|Status||The status of the Requirement, could be: New, In progress, Ready to test, Closed, Rejected|
|Priority||The priority of the Requirement, could be: Could, Should, Must, Won't|
|Severity||The severity of the Requirement, could be: Trivial, Minor, Major, Critical, Blocker|
|Author||The Employee that created the Requirement|
|Story points||The number of points for the Requirement|
|Estimation||The time estimation (in hours) to do the Requirement. Usually this value doesn't change.|
|Effort made||The spent time (in hours) until now on the Requirement. This value is changing until the requirement is closed.|
|Remaining effort||The estimated remaining time (in hours) to achieve the Requirement. This value is changing until the requirement is closed.|
|Iteration||The attached Iteration. Only for a Requirement of an Initiative|
|In scope||Define if the Requirement is approved or not.|
|Deliverables||The Deliverables associated with the Requirement.|
List of Requirements
The list of Requirements is a sortable and filterable table. It's also possible to hide and show columns.
By clicking on a Requirement, its identity card is displayed.
It possible to create a new Requirement by clicking on the icon, and to edit one by clicking on the icon.
For an external Requirement it is possible to edit only the associated Deliverables and the custom attributes.
When editing the Deliverables of a Requirement (through the edit page), the result has the same impact than editing the associated Requirements of a Deliverable.
Identity card of a Requirement
All Requirement's data can be seen via the Requirement identity cart.
The status page is an overview of all Requirements, sorted by Needs and Defects.
The Needs section contains 2 charts with the distribution by priority:
- Pie chart: the inside area segregates the mandatory Needs again the optional ones, and the outside area shows the status for each segment.
- Bar chart: for each priority a set of bars is given which represents the number of Requirements by status.
The Defects section contains 2 charts with the distribution by severity:
- Pie chart: the inside area segregates the blocker Needs again the non-blocker ones, and the outside area shows the status for each segment.
- Bar chart: for each severity a set of bars is given which represents the number of Requirements by status.
The Iterations are usually used with Agile methodology. They are provided externally, for instance by a plugin.
It is not possible to manage the attributes of an Iteration from BizDock, except the “Story points” and the custom attributes.
An Iteration has the following set of attributes:
|Name||The name of the Iteration.|
|Description||The description of the Iteration.|
|Closed||Define if the Iteration is closed. A closed Iteration is represented by 2 points in the burndown chart, a non-closed by only 1.|
|Story points||The total story points available for the Iteration. This information is used to compute the burndown chart.|
|Start date||The start date of the Iteration.|
|End date||The end date of the Iteration. This date is used to order the Iterations in the burndown chart.|
|Source||A string that represents the source (meaning the provider) of the Iteration. This information could be used to filter the Iterations in order to obtain the burndown chart for the only wished ones.|
List of Iterations
The list of Iterations is a sortable and filterable table. It's also possible to hide and show columns.
By clicking on an Iteration, its identity card is displayed.
It is possible to edit the “Story points” and the custom attributes of an Iteration by clicking on its edit icon .
Just under the list of Iterations, a burndown chart is displayed. It contains all Iterations of the current list with a non-null value for the “Story points” attribute.
The chart is not automatically updated when a filter is modified in the table, the user should click on the refresh icon .
The x-axis represents the Iterations ordered by “End date” (older first). The y-axis represents the plurality of the “Story points”.
The chart is represented by 2 lines:
- The first (in gray) is the planned situation
- The second (in blue) is the real situation
The planned situation is computed as follow:
- The first point (that is the start of the first Iteration) is the sum of all “Story points” of the Iterations.
- The second point (that is the end of the first Iteration and the start of the second) is the sum of all “Story points” of the Iterations minus the first.
- The third point (that is the end of the second Iteration and the start of the third) is the sum of all “Story points” of the Iterations minus the first and the second.
- And so on
The real situation is computed as follow:
- The first point is the sum of all “Story points” of the Iterations. So it is always the same value than the planned situation.
- The second point is the sum of all “Story points” of the Iterations minus the sum of “Story points” for all closed Requirements of the first Iteration.
- The third point is the sum of all “Story points” of the Iterations minus the sum of “Story points” for all closed Requirements of the first and the second Iterations.
- And so on
The points (except the first) of the real situation are displayed only for closed Iterations.
Identity card of an Iteration
All Iteration's data can be seen via the Iteration identity cart.