User Story Estimation Guidelines

The estimation can be done either by a single developer, usually the Team Lead, or by the whole development squad.

Estimation Process

To get those story points estimates and time estimation, the process goes like this:

• The Project Manager discusses the feature at length with the client
• The Project Manager writes the necessary documentation and user stories
• The Team Lead estimates those user stories with other SE at the squad
• Open communication must be maintained between the Project Manager and Team Lead at any given time
• As a generally accepted agile pattern, bugs, quotes and small tasks issues are NOT assigned any points as these issues cannot be properly estimated.

Story Points

When assigning points to user stories, we follow these comprehensive guidelines to accurately gauge the complexity and effort required:

• 0 point:

  • Description: Minimal complexity with a known, straightforward solution.
  • Effort: Typically less than an hour of work.
  • Examples: Simple changes like text or image modifications fall into this category.

• 1 point:

  • Description: Minimal complexity with a known solution.
  • Effort: Requires a few hours to a day to complete.
  • Examples: Tasks that are straightforward but take a bit more time than zero-point stories.

• 2 points:

  • Description: No inherent complexity (as in "it's something we've done before") but requires more time to implement.
  • Effort: Typically spans 1-2 days.
  • Examples: Familiar tasks that may be time-consuming.

• 3 points:

  • Description: Medium complexity due to some unknowns or research requirements.
  • Effort: Usually takes 2-3 days.
  • Examples: Tasks where developers know how to approach roughly 50% of the work but need to investigate the rest.

• 5 points:

  • Description: High complexity, often involving significant unknowns or extensive research.
  • Effort: Typically ranges from 3 to 5 days.
  • Examples: Tasks that require substantial research or involve work that the team hasn't encountered before.

• 8 points:

  • Description: Suggests that the user story is overly complex or too large.
  • Effort: Indicates that the story should be re-evaluated and broken down into smaller, more manageable tasks.

Where to Input User Story Points in Jira

In our project management workflow, Jira plays a pivotal role in tracking and managing user stories. User story points, which reflect the estimated complexity and effort required for each task, are a crucial component of this process. Here's how and where to input these points within Jira:

Jira User Story Points Field

Jira provides a dedicated field for user story points. This field serves as the central repository for recording and tracking the estimated points associated with each user story. By assigning these points, we communicate the anticipated workload and complexity of the task to our development team and stakeholders.

Utilizing the Field

When creating or editing a user story in Jira, you can locate the "User Story Points" field within the user story details. This is the designated space where you should input the appropriate point value based on the user story's estimated complexity and effort level.

Aligning with Estimation Guidelines

To ensure consistency and accuracy in our project planning, we follow the multi-faceted estimation guidelines outlined previously. By aligning the user story points in Jira with these guidelines, we provide a clear and standardized way to assess and prioritize tasks within the project.