How to Estimate Your Software Project Using Agile Methodology: Storyboarding, Story Points, and More

Estimating a software project using Agile methodology can seem daunting, but with the right tools and techniques, you can effectively plan and manage your project. In this article, we will discuss using storyboarding, measuring story size with story points, and incorporating additional estimates for QA and project management activities. We'll also provide an example table of estimates and a method for converting story points into hours to help you estimate the length and team size required for your project.


A storyboard is a visual representation of your project's user stories, describing the main features and functionality of the software. Storyboarding helps you prioritize and organize work, ensuring that the team understands the project requirements and scope.

To create a storyboard, follow these steps:

1.1. Write user stories: Begin by identifying the main features and functionality your software should provide. Write them down as user stories, which are short descriptions of the desired outcome from a user's perspective.

1.2. Organize user stories: Group related user stories together to create a cohesive flow. This will help you prioritize work and identify dependencies.

1.3. Create the storyboard: Use a visual tool, such as a whiteboard or digital board, to represent user stories and their relationships. This will allow you to have an overview of the project and make adjustments as needed.

Measuring Story Size Using Story Points

To estimate the effort required for each user story, Agile teams use story points, which represent the complexity, effort, and uncertainty of a user story. Assigning story points is a relative process that requires the collaboration of the entire team.

2.1. Determine a baseline: Choose a simple user story as a baseline, and assign it a value (e.g., 1 story point).

2.2. Estimate other stories: Compare the complexity of other user stories to the baseline, assigning a story point value accordingly. Common scales include linear (1, 2, 3, 4...) or Fibonacci sequence (1, 2, 3, 5, 8...).

2.3. Refine estimates: As the team works on the project, update story point estimates as needed, based on the actual effort required.

Example Table of Estimates

Here's an example of a table of estimates for a software project:

Total story points: 29 Total QA effort: 8.7 (30% of 29) Total project management effort: 4.35 (15% of 29)

Converting Story Points to Hours and Estimating Team Size

To estimate the duration and team size required for the project, you need to convert story points into hours. This conversion factor will vary depending on your team's experience and the project's complexity. For example, you might decide that 1 story point equals 4 hours of work.

Using the example table above, we can calculate the total effort as follows:

Total effort (in hours) = (29 story points + 8.7 QA + 4.35 PM) * 4 hours/story point = 168.8 hours

To estimate the duration and team size, you need to consider the number of available work hours per team member and the project deadline. For example, if you have a deadline of 4 weeks and each team member can work 40 hours per week, you have a total of 160 available work hours per team member.

To calculate the required team size, divide the total effort by the available work hours per team member:

Team size = Total effort (in hours) / Available work hours per team member = 168.8 hours / 160 hours = 1.05

In this example, you would need at least 2 team members to complete the project within the given deadline. Keep in mind that these estimates are just a starting point and should be adjusted as needed throughout the project based on actual progress and team performance.

Estimating a software project using Agile methodology involves several steps, including storyboarding, assigning story points, and accounting for QA and project management activities. By following these guidelines and adjusting estimates as needed, you can effectively plan and manage your project, ensuring that you have the necessary resources and time to deliver a successful product.