PERT With Wings

This extension assists you to make consistent PERT estimates table in JIRA / Azure DevOps comments across projects.

Install on Chrome
Install on Firefox requires extra steps.

How to use

  1. Navigate to your JIRA / Azure DevOps ticket and click on comment box to make it editable.

  2. Click on the PERT button in bottom right in your window.

  3. Fill in the boxes and click 'Add PERT Estimate' button.

FAQ

What is PERT?

PERT (Program Evaluation and Review Technique) calculates a weighted average as the PERT estimate by using the formula

PERT Estimate = Optimistic + 4 × Likely + Pessimistic 6

Optimistic Estimate

Estimate for all favourable conditions with no risks or changes.

The Optimistic Estimate is the “best-case” and thus shortest duration, or lowest cost, to complete the work.

The fastest time you can complete an activity. This assumes that all the necessary resources have been put in place and nothing unexpected occurs. This estimate is hard to achieve most of the time because projects are expected to face some challenges.

—Kelly Birch

Likely Estimate

Estimate for both favourable and unfavourable conditions, with some risks occurring.

The name is accurate in the estimate is based on changes, but ones that have been planned for and can be mitigated. The Most Likely estimate captures the highest likelihood of completing the work in the given duration or cost.

The most likely figure if there aren't any significant issues, but also not the best optimistic case. A realistic estimate. If you were asked for a quick time estimate this might be the figure you would come up with.

—Kelly Birch

Pessimistic Estimate

Estimate for all unfavourable conditions with all negative risks occurring and no mitigation of negative risks

It is the opposite of the Optimistic estimate in concept. The Pessimistic Estimate is the “worst-case” and thus longest duration, or highest cost, to complete the work.

This refers to the maximum time needed to complete an activity. It assumes and factors in all the negative things that may affect an activity. Most project teams assume resource unavailability and rework when deriving this estimate.

—Kelly Birch
Why can't I see the PERT button?

Try reloading the JIRA / Azure DevOps ticket

Why is the calculation wrong?

It's probably a bug. Please create a bug in JIRA.

I have an idea to make PWW better.

Please create a ticket in JIRA.

Firefox extra steps.

Following features needs to be enabled from about:config in order to use PERT with Wings in Firefox

dom.events.asyncClipboard.clipboardItem true
layout.css.has-selector.enabled true

Changelog

1.2.0 (2023-03-08)
Now showing dev tasks separately with dev time as a total in the PERT table.
Minimum QA estimated is no longer added to total with zero percentage of QA.
After adding PERT estimate, videos, tags and emojis which were already in the comment gets broken because PWW tries to set these tags again. As a workaround for this we now have a copy estimate button. Instead of adding the estimate directly to the comment box, now we can copy it and paste it anywhere. (In firefox dom.events.asyncClipboard.clipboardItem preferences needs to be set to true. To change preferences in Firefox, visit about:config.)
Fixed an issue where PWW was not receiving focus and was not fully functional when a ticket (or issue creation dialogue) is opened in a modal.
Now showing errors for invalid estimates. Allowing only hour value (1.5) or hours and minutes (1h 30m) in estimate fields.
1.1.6 (2023-01-31)
Fixed label styles in Azure DevOps
E2E tests added.
1.1.5 (2023-01-16)
PERT bookmarklet is a browser extension now!
If you have more than one dev task, additional dev tasks are considers as optional tasks by default.
We have the ability to add a QA PERT estimate received from QA team.
We have the ability to add a Complexity/Risk level.
We are not rounding the time amount to closest 10 minutes by default anymore.
2022-10-18
Add Azure devops support
2022-06-21
Add better validation to input fields to avoid erroneous calculations.
Remove fill Original Estimate field in JIRA ticket feature since JIRA doesn't allow you to change this field after its set and in some cases estimate time is not the best time to set the value here.
Add feature to round totals. Also can set the default in configs per project.
2022-04-29
Add minimize modal button.
Add project based default value content.
Add automated tests row.
Add warning if comment box is not in edit mode.

Contribute

https://github.com/aligent/pert-with-wings.