---
title: Priority and Effort Resources
---

:::caution[Programme Sunset]
The open Mentorship Programme has been sunset and is no longer accepting new participants. These pages remain available as reference material.

I'm now running a private, personalised professional development programme on an invite-only basis - hand-selecting a small number of participants so the shape of each journey can be built around them. There is no application process; participation is by direct invitation only.

Being active in my [Discord community](https://chat.nhcarrigan.com/) increases your chances of being invited.
:::

**PRIORITY ASSIGNMENT AND EFFORT ESTIMATION GUIDES**

## Priority Assignment Guide

### Understanding Priority

**Priority is based on dependencies, not personal preference.**

Priority determines the order in which user stories should be completed based on:
- Which stories block other stories
- Which stories must be completed first
- Logical sequence requirements

### Priority Assignment Process

#### Step 1: Identify Dependencies

**Questions to Ask:**
- Which stories must be completed before others can start?
- Which stories block multiple other stories?
- What is the logical sequence of feature development?

**Example:**
- Authentication must be completed before user-specific features
- Database models must exist before features that use them
- Core features must exist before advanced features

#### Step 2: Map Dependencies

**Create a dependency map:**
- List all user stories
- Identify which stories depend on others
- Identify which stories block others
- Create a dependency graph

#### Step 3: Assign Priority Levels

**Priority Levels:**
- **High Priority:** Blocks multiple other stories or is foundational
- **Medium Priority:** Blocked by high priority, may block some stories
- **Low Priority:** Blocked by other stories, doesn't block others

### Priority Example

**User Stories:**
1. As an unauthenticated user, I can create an account
2. As an authenticated user, I can view my profile
3. As an authenticated user, I can edit my profile
4. As an authenticated user, I can create a post
5. As a user, I can view posts from other users

**Dependency Analysis:**
- Story 1 blocks stories 2, 3, and 4 (authentication required)
- Story 2 blocks story 3 (must view before editing)
- Story 4 blocks story 5 (must create before viewing)
- Stories 2 and 4 don't block each other

**Priority Assignment:**
- **High:** Story 1 (blocks multiple stories)
- **Medium:** Stories 2 and 4 (blocked by 1, but don't block each other)
- **Low:** Stories 3 and 5 (blocked by other stories)

## Effort Estimation Guide

### Understanding Effort

**Effort represents the amount of work required to complete a story.**

Effort helps you:
- Plan your work timeline
- Balance high-priority tasks with available time
- Estimate project completion
- Make informed decisions about task selection

### Effort Estimation Methods

#### Story Points

**Common Scales:**
- **Fibonacci:** 1, 2, 3, 5, 8, 13, 21
- **T-Shirt Sizes:** XS, S, M, L, XL
- **Linear:** 1, 2, 3, 4, 5

**Story Point Guidelines:**
- **1-2 points:** Simple, straightforward tasks
- **3-5 points:** Moderate complexity, some unknowns
- **8-13 points:** Complex, multiple components, significant unknowns
- **21+ points:** Very complex, should be broken down

#### Time-Based Estimation

**Time Estimates:**
- **Small:** 1-4 hours
- **Medium:** 4-16 hours
- **Large:** 16-40 hours
- **Very Large:** 40+ hours (consider breaking down)

### Effort Estimation Factors

**Consider:**
- **Complexity:** How complex is the implementation?
- **Uncertainty:** How much is unknown?
- **Dependencies:** Are dependencies clear and available?
- **Scope:** How much work is involved?
- **Risk:** What could go wrong?

### Effort Example

**User Stories with Effort Estimates:**

1. **Create account (5 points):** Building entire authentication flow is complex
2. **View profile (3 points):** Moderate complexity, needs API and UI
3. **Edit profile (3 points):** Similar to view, plus update logic
4. **Create post (5 points):** Complex with validation, API, UI
5. **View posts (1 point):** Simple display of existing data

## Label Examples

### Priority Labels

**Option 1: Text Labels**
- `priority: high`
- `priority: medium`
- `priority: low`

**Option 2: Numbered**
- `priority: 1` (highest)
- `priority: 2`
- `priority: 3` (lowest)

**Option 3: Descriptive**
- `priority: critical`
- `priority: important`
- `priority: nice-to-have`

### Effort Labels

**Option 1: Story Points**
- `effort: 1`
- `effort: 2`
- `effort: 3`
- `effort: 5`
- `effort: 8`
- `effort: 13`

**Option 2: T-Shirt Sizes**
- `effort: xs`
- `effort: s`
- `effort: m`
- `effort: l`
- `effort: xl`

**Option 3: Time-Based**
- `effort: small` (1-4 hours)
- `effort: medium` (4-16 hours)
- `effort: large` (16-40 hours)

## Best Practices

### Priority Best Practices

✅ Base priority on dependencies, not interest
✅ Review dependencies carefully
✅ Update priorities as dependencies change
✅ Consider blocking relationships

❌ Don't prioritize based on what's most fun
❌ Don't prioritize based on excitement level
❌ Don't ignore dependencies

### Effort Best Practices

✅ Be honest about complexity
✅ Consider unknowns and risks
✅ Break down large stories
✅ Review estimates after completion to improve

❌ Don't underestimate complex tasks
❌ Don't overestimate simple tasks
❌ Don't ignore your own skill level

## Combining Priority and Effort

### Work Planning Strategy

**When you have limited time:**
- Choose high-priority, low-effort tasks first
- This allows progress even with time constraints

**When you have more time:**
- Tackle high-priority, high-effort tasks
- These are often foundational and important

**Example Decision Matrix:**

| Priority | Effort | Action |
|----------|--------|--------|
| High | Low | Do first |
| High | High | Do when you have time |
| Medium | Low | Good for quick wins |
| Medium | High | Plan for dedicated time |
| Low | Low | Do when caught up |
| Low | High | Consider breaking down |

---

*Priority and effort help you plan and execute work effectively. Use them together to make informed decisions about what to work on.*

