Estimation guidelines

Depending on current project state, available time and needs, you might want to apply different methods of estimation. Basic level can be described as in table below:

Confidence level

ROM (Rough Order of Magnitude)

Quick estimation giving first indication about expected cost, but with low confidence level. More common in very early stages of a project.
Result can be achieved using expert, analogous or affinity estimation.

Budget estimation

Estimation on story/task level can be applied if stories are described in more details, team has better understanding about scope and technical challenges, and there is more time.
If team has started with ROM estimation. Over time, initially unknown activities and requirements become clearer and need to be reflected in a refined project plan. This process is called ‘progressive elaboration‘.

Definitive estimation

This level of confidence is required on Sprint planning, so that the team would know exactly how much time they require to complete the tasks and are able to verify how it fits their capacity.

Estimation process

In order to have common approach across the projects at M&P, it has been decided each project team would follow timewise estimation (hours / days / weeks).

Estimation can be performed in various tools, however results shall be stored in JIRA ticket system, depending on the confidence level:

ROM → original estimation is stored in epics

Budget → original estimation is stored in stories

Definitive → original estimation is stored in sub-tasks

Such approach allows to easily share estimated values and verify it during progressive elaboration.

Estimation guidelines

What is dev-work, i.e. what’s included in Original Estimate/can be logged on DEV tickets:

Technical discussions

Developer Testing

What is NOT dev-work, i.e. what should NOT be included in estimations:

QA Testing (Logged on general QA ticket, just comment is added specifying tasks)

Code Reviews (Logged on general