What are Assumptions?
An Assumption is an unvalidated factor that has the potential to influence the outcome of the project.
Project on Demand provides an Assumption management solution that facilitates Assumption recording, validation and review management.
How should they be used?
The Assumption management process within Project on Demand is as follows:
Project Management Process Step | Action within Project on Demand | |
---|---|---|
1 | Identify and record the Assumption. | Create a new Assumption. |
2 | Assign ownership of the Assumption. | Set the Owner. |
3 | Perform a risk assessment to establish when the Assumption is required to be validated. | Set the Validation Date and Review Date. |
4 | Monitor the Assumption and perform periodic reviews. | Monitor Dashboard / Assumption Management for any overdue Assumption reviews. |
5 | Validate the Assumption. | Set Status to Resolved. |
Assumption Properties
Name | Description | Possible Values |
---|---|---|
ID | Unique Assumption reference number. | Number - Generated by the application. |
Description | Full description of the Assumption. | Text. |
Identified By | The person who identified the Assumption. | User with Project access or text. |
Identified Date | The date the Assumption was identified. | Autogenerated to date of creation but fully customisable. |
Validation Date | The date by which the Assumption needs to be validated. | Date. |
Implications | The impact on the project if the Assumption cannot be validated. | Text. |
Owner | The person who has been assigned ownership of the Assumption. | User with Project access or text. |
Review Date | The next scheduled review date. | Autogenerated to date of creation but fully customisable. |
Status | The current state of the Assumption. | Open or Closed. |
Concurrency Control
Assumptions implement optimistic concurrency control.