Issue Estimation Process

We use T-shirt sizing mapped to a modified Fibonacci sequence to estimate issues.

T-Shirt Sizing

Tasks are categorized into sizes:

• XS: 1
• S: 2
• M: 3
• L: 5
• XL: 8

Determining Task Size

Criteria for Estimating

Complexity:

• XS: Very simple, no unknowns, straightforward tasks.
• S: Simple, minor unknowns, low complexity.
• M: Moderate complexity, some unknowns, manageable challenges.
• L: High complexity, significant unknowns, substantial challenges.
• XL: Very high complexity, many unknowns, major challenges.

Effort:

• XS: Minimal effort, typically less than a day.
• S: Minor effort, usually a day or less.
• M: Moderate effort, a few days, manageable by one person.
• L: Significant effort, likely a week or more, may need multiple people.
• XL: Very high effort, multiple weeks, requires coordination across teams.

Dependencies:

• XS: No dependencies, fully within control.
• S: Few dependencies, mostly within control.
• M: Some dependencies, manageable within the team.
• L: Multiple dependencies, requires coordination with other teams.
• XL: Numerous dependencies, extensive coordination needed.

Risk:

• XS: No risk, straightforward execution.
• S: Low risk, minor potential issues.
• M: Moderate risk, some potential issues.
• L: High risk, significant potential issues.
• XL: Very high risk, major potential issues.

Example estimations

• XS: Updating a text label, making a configuration change or fixing a small bug.
• S: Adding a simple improvement, a small UI adjustment or a small feature.
• M: Implementing a new feature in an existing module with clear requirements.
• L: Overhauling a core system component, requiring extensive testing.
• XL: Developing a new system from scratch, requiring significant design and coordination. Consider if this should be a project