Planning is Ruffly's most important feature. It allows you to view your work breakdown and resource allocation across time.
The Rufflyness is a dynamic contingency on your project (i.e our best guess as to when this project might be completed)
There are two factors that influence the Rufflyness.
Estimates are your team's best guess as to how complicated this piece of work is, relative to the other pieces of work. This is then used as a proxy for how long it might take to complete the task.
Actuals are the actual effort it took to complete the the task.
Consider the following example:
A task to "Create a registration page" has an estimated effort of 11 story points.
Now lets consider three scenarios of actuals for this particular task.
|Estimated Effort||Actual Effort||Error (%)|
In the first scenario, this task took 8 story points instead of the estimated 11. Ruffly uses this data to adjust the Rufflyness factor of your project.
However, in most projects, estimates are often underquoted. Due to unexpected complexity of work, or scope creep, a given task can take much longer to complete, than initially estimated.
In the final scenario, this task took 13 story points instead of the estimated 13. Ruffly then uses this data point to re-calculate the Rufflyness factor of your project.
As you're working through the project, and work is being done, the Rufflyness factor decreases, due to an increased level of certainty on the outstanding tasks.
Here's an example of how Ruffly calculates the dynamic contingency of a project.
You can update requirement status directly in the planning view, ensuring you're always on top of your project.