| Point Level | Level of Effort | Description | Example Tickets |
|---|---|---|---|
| 0 | None (or due to recent defect and not going to give additional points to fix it) | Actions conducted by non developer/engineering personnel. Simple verification tasks. Also includes tickets that must be reviewed during Backlog Grooming and Sprint Planning | |
| 1 | Less than an hour | Activating a plugin and verifying it's operation | |
| 3 | 1-3 hours | Updating a plugin or theme via composer | data-491 - Onetrust data deletion request |
| 5 | Less than a day | Investigate HealthDay feed ingestion issues | |
| 8 | 1-2 days | Add new fields to web service along with adding fields in database structure and then verify data shows up properly in RabbitMQ | WP-139 WPMCK-6 |
| 13 | 2-4 days | WordPress or PHP upgrade | Together these would be 13 (WP-1559 WP-1560) |
| 21 | Create a new marketing website - A considerably large effort possibly taking multiple sprints - reserved for Project Abstracts | ||
| 34 | A considerably large effort possibly taking multiple sprints - reserved for Project Abstracts | ||
| 55 | A considerably large effort possibly taking multiple sprints - reserved for EPICs | ||
| 89 | A considerably large effort possibly taking multiple sprints - reserved for EPICs |
The Level of Effort we’re estimating is based on t-shirt sizing and is generally based on the level of effort for the developers that are part of the team and not really the amount of time QA or POs need to put into a ticket. And then we usually just bump it up one size based on uncertainty, e.g., if a product owner writes “add new Facebook feature – details to come later”, that sounds like probably a small to medium (5-8 points) but based on the vagueness we might initially size it as a medium-large (8-13 points) depending on what else we’re guessing about it till we get the details. And then we can always re-estimate the points for a story up until the point a sprint starts and then no more re-estimating points.