Assignment: Agile Estimation

In this assignment, you will be practicing agile estimation techniques. You will be working on a hypothetical project and using the techniques discussed in class to estimate the effort required to complete the project.

Task:

Your task is to estimate the effort required to complete the development of an e-commerce website. The website will have the following features:

User registration and login

Product catalog with search and filtering capabilities

Shopping cart and checkout process

Payment gateway integration

Order tracking and history

Instructions:

Break down the project into small tasks: In order to estimate the effort required for each task, you need to first break down the project into small tasks. Use the features listed above as a starting point and further break them down into smaller tasks.

Use story points to estimate the effort: Once you have broken down the project into small tasks, use story points to estimate the effort required for each task. Assign a relative value to each task based on its complexity, risk, and uncertainty. Use the Fibonacci sequence (1, 2, 3, 5, 8, 13) to assign story points.

Estimate the velocity of your team: Estimate the velocity of your team by looking at how many story points your team can complete in a given sprint. Use your team's historical data if available, or make an educated guess if you are starting a new project.

Determine the number of sprints required: Based on the total number of story points, estimate the number of sprints required to complete the project. Assume that each sprint is two weeks long.

Deliverables:

Submit a report that includes the following:

A breakdown of the project into small tasks

Story point estimates for each task

Estimated project velocity

Estimated number of sprints required to complete the project

You will be graded on the following criteria:

Accuracy and completeness of the breakdown of the project into small tasks

Accuracy and justification of story point estimates

Accuracy and justification of project velocity estimates

Accuracy and justification of the number of sprints required