http://ghafoorsblog.com/tags/agile-estimation/Recent content in Agile-Estimation on Ghafoor's Personal BlogHugoennoreply@example.com (AG Sayyed)noreply@example.com (AG Sayyed)Copyright © 2024-2026 AG Sayyed. All Rights Reserved.Fri, 31 Oct 2025 11:40:28 +0000http://ghafoorsblog.com/courses/ibm/devops-content/devops-pcert/02-agile-development-and-scrum/03-module/005-practical-exercise/Wed, 04 Jun 2025 13:09:18 +0000noreply@example.com (AG Sayyed)http://ghafoorsblog.com/courses/ibm/devops-content/devops-pcert/02-agile-development-and-scrum/03-module/005-practical-exercise/<h2 id="understanding-story-points">Understanding Story Points</h2> <p>Story points are a unit of measure used to estimate the relative effort required to complete a user story. Unlike time-based estimates (hours/days), story points consider:</p> <p><strong>Key Factors:</strong></p> <ul> <li><strong>Complexity</strong> - How difficult is the work?</li> <li><strong>Amount of Work</strong> - How much code/testing is needed?</li> <li><strong>Risk/Uncertainty</strong> - How many unknowns exist?</li> </ul> <p><strong>Common Story Point Scale (Fibonacci):</strong></p> <ul> <li>1 point = Very simple task (30 minutes - 2 hours)</li> <li>2 points = Simple task (2-4 hours)</li> <li>3 points = Medium task (4-8 hours)</li> <li>5 points = Large task (1-2 days)</li> <li>8 points = Very large task (2-3 days)</li> <li>13 points = Epic (should be broken down)</li> </ul> <hr> <h2 id="practical-exercise-building-a-task-management-app">Practical Exercise: Building a Task Management App</h2> <p><strong>Team:</strong> 4 developers (Frontend, Backend, QA, DevOps)<br> <strong>Sprint Duration:</strong> 2 weeks (10 working days)<br> <strong>Team Velocity:</strong> 45 story points (based on last 3 sprints)</p>