Step-by-step guide
How to use and enable visual graph of requirements
Adding Requirement
To add requirement use "..." next to Create button, there after find "Product Requirement for Clarity Map
| Panel | |
|---|---|
On this page:
|
Specifying properties
After confirming page creation you get confluence page that is done based on template inherited from standard confluence requirement blueprint
Properties relevant for Requirements Clarity map
| Property name | Description | Format, possible values |
|---|---|---|
| Short name | A title of the node for Clarity Map Graph | Char : 15 |
| Description | Long description of requirement | Text |
| Epic | link to Jira issue, presumably epic | |
| Clarity | How clear is requirement. Defines fill color on Clarity Map Graph |
|
| Size | How big is requirement. Defines size of the node on Clarity Map Graph. T-shirt size based qualification of size of requirement |
|
| Status | Defines status of this requirement. As soon as there is associated epic in Jira - Status is determined by status of linked issue, before that - status is not defined |
|
| Question and Answers | Open questions and answers for given requirement | Text |
Adding Requirement Graph
You go with "+" sign on control button bar and then " ... Other macros", then select Requirement Clarity Map
Provide
| Parameter | Description |
|---|---|
| Space Key | Confluence key of the space where your requirements pages are located |
| Page Title | Root of the tree where you want macros to start processing |
| Whether or not you want to enable hints on the map usage |
Insert adds a graph to your confluence page
What you can see and what you can do with a graph
Size
Clarity
How clear is a requirement is defined by one of three choices
- UNKNOWN - team doesn't understand what risks are there, what effort is required for this to be implemented
- UNCERTAIN - team has some understanding of what this requirements is about. There are some unclear items that needs to be researched or investigated
- CLEAR - team understands complexity of requirement, understands implementation steps, acceptance criteria are defined
Status
Status of corresponding requirement is determined by status of associated Jira epic. In case no epic is yet created - status is NULL. On graph you can easily determine that by color of the bezel
| Info | ||
|---|---|---|
| ||
Requirement Clarity Map macro needs Application Link between Confluence and Jira to get statuses. To make it work you have to authenticate yourself on Jira side. |
Hierarchy
Ray diagram represent hierarchical structure of all requirements underneath provided root element. In sample case "Family"
+ / - signs are options to expand / collapse corresponding node
Properties
Selecting a node - opens property panel.
Following values are available for inline editing
- Short name
- Clarity
- Size
- Description
- Questions and Answers
Timeline snapshots
Coming soon
| Info |
|---|
Related articles
| Content by Label | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Page properties | ||
|---|---|---|
| ||
|