<h1>Agile Software Development<br></h1><p><span style="font-size: 16px">Course Includes below modules:</span><br></p><ul><li><span style="font-size: 16px">Agile Fundamentals<br></span></li><li><span style="font-size: 16px">Agile Requirements and Planning</span></li><li><span style="font-size: 16px">Scrum &amp;</span></li><li><span style="font-size: 16px">Agile in real world</span><span style="font-size: 18px">?</span></li></ul><h2>Introduction<br></h2><p><span style="font-size: 18px">Agile is a dynamic and iterative approach to project management and software development that emphasizes flexibility, collaboration, and customer satisfaction. Unlike traditional waterfall models, where projects follow a linear and sequential process, Agile allows for more fluid and adaptive methodologies. This approach is particularly well-suited for projects with rapidly changing requirements or those that require continuous improvement and customer feedback.</span><br></p><p><span style="font-size: 16px"><br></span></p>

Agile Home

<p><span style="font-size: 16px">In Agile project management, the terms "adaptive" and "predictive" represent two different approaches to planning and executing projects. Understanding the differences between these approaches can help teams choose the right methodology based on the nature of their project and organizational needs.</span></p><h2><span style="font-size: 16px"></span><span style="font-size: 22px">Adaptive Approach:</span></h2><p><span style="font-size: 16px">The adaptive approach, often associated with Agile methodologies, is characterized by flexibility and responsiveness to change. Here are some key features of the adaptive approach:</span></p><ol><li style="font-size: 16px"><p><strong>Iterative Process</strong>: Projects are broken down into small, manageable iterations (sprints or cycles) that typically last between one to four weeks. Each iteration involves planning, execution, and review.</p></li><li style="font-size: 16px"><p><strong>Continuous Feedback</strong>: Regular feedback from stakeholders, including customers, is integral. This allows for adjustments and refinements based on real-world insights and changing requirements.</p></li><li style="font-size: 16px"><p><strong>Incremental Delivery</strong>: Working software or product increments are delivered at the end of each iteration, allowing for continuous integration and testing.</p></li><li style="font-size: 16px"><p><strong>Flexibility to Change</strong>: Adaptive methodologies embrace change, even late in the development process. This is essential for projects with uncertain or evolving requirements.</p></li><li style="font-size: 16px"><p><strong>Collaboration and Communication</strong>: High levels of collaboration among team members and stakeholders are crucial. Daily stand-ups, sprint reviews, and retrospectives are common practices.</p></li><li style="font-size: 16px"><p><strong>Focus on Value</strong>: The primary goal is to deliver the most valuable features to the customer as early as possible. Prioritization is based on customer needs and business value.</p></li></ol><div class="se-component se-image-container __se__float-none" style="width: 100%"><figure style="width: 100%;"><img src="https://www.api.cstechie.com/upload/editor-image/adaptive-approach_1721583424964.jpg" alt="" data-rotate="" data-proportion="true" data-size="100%," data-align="none" data-percentage="100," data-file-name="adaptive-approach.jpg" data-file-size="324349" data-origin="," origin-size="3000,2000" style="width: 100%;"></figure></div><p style="text-align: center">Fig 1<br></p><h2 style="line-height: 1.2"><br>Predictive Approach</h2><p style="line-height: 2em"><span style="font-size: 16px">The predictive approach, often associated with traditional project management (such as Waterfall), is characterized by a more rigid and structured planning process. Here are some key features of the predictive approach:</span></p><ol><li style="font-size: 16px"><p style="line-height: 2em"><strong>Detailed Planning</strong>: Extensive planning is done at the beginning of the project. This includes defining scope, timelines, resources, and deliverables in detail.</p></li><li style="font-size: 16px"><p style="line-height: 2em"><strong>Linear Process</strong>: Projects follow a sequential flow, with each phase completed before moving on to the next. Common phases include requirements gathering, design, development, testing, and deployment.</p></li><li style="font-size: 16px"><p style="line-height: 2em"><strong>Fixed Scope</strong>: The project scope is typically defined upfront and changes are minimized. Any changes usually require a formal change request process.</p></li><li style="font-size: 16px"><p style="line-height: 2em"><strong>Predictability</strong>: With a detailed plan in place, predictive methodologies aim to provide clear timelines, budgets, and resource allocations. This approach is suitable for projects with well-understood and stable requirements.</p></li><li style="font-size: 16px"><p style="line-height: 2em"><strong>Limited Flexibility</strong>: Changes to the project plan are generally discouraged once the project is underway. Adjustments can be costly and time-consuming.</p></li><li style="font-size: 16px"><p style="line-height: 2em"><strong>Documentation and Process</strong>: Emphasis is placed on thorough documentation and adherence to established processes and standards.</p><div class="se-component se-image-container __se__float-none" style="width: 100%"><figure style="width: 100%;"><img src="https://www.api.cstechie.com/upload/editor-image/the-waterfall-model-infographic-is-used-in-software-engineering-or-software-development-processes-the-illustration-has-6-steps-like-agile-methodology-or-design-thinking-for-application-system-vector_1721589799158.jpg" alt="" data-rotate="" data-proportion="true" data-size="100%," data-align="none" data-percentage="100," data-file-name="the-waterfall-model-infographic-is-used-in-software-engineering-or-software-development-processes-the-illustration-has-6-steps-like-agile-methodology-or-design-thinking-for-application-system-vector.jpg" data-file-size="75476" data-origin="," style="width: 100%;"></figure></div></li></ol><p style="text-align: center"><span style="font-size: 16px">Fig 2<br></span></p><h2><span style="font-size: 22px">Comparison:</span></h2><table><tbody><tr><td><div><strong>Feature</strong></div></td><td><div><strong>Adaptive</strong>&nbsp;</div></td><td><div><strong>Predictive</strong></div></td></tr><tr><td><div>Planning</div></td><td><div>Iterative and ongoing<br></div></td><td><div>Extensive upfront planning<br></div></td></tr><tr><td><div>Flexibility</div></td><td><div>High, embraces change<br></div></td><td><div>Low, change is minimized<br></div></td></tr><tr><td><div>Feedback<br></div></td><td><div>Continuous from stakeholders<br></div></td><td><div>Limited, usually at milestones<br></div></td></tr><tr><td><div>Delivery<br></div></td><td><div>Incremental and frequent<br></div></td><td><div>Final product at the end<br></div></td></tr><tr><td><div>Scope<br></div></td><td><div>Evolving based on feedback<br></div></td><td><div>Fixed at the start<br></div></td></tr><tr><td><div>Process<br></div></td><td><div>Collaborative and flexible<br></div></td><td><div>Structured and sequential<br></div></td></tr><tr><td><div>Documentation<br></div></td><td><div>Lightweight and as needed<br></div></td><td><div>Comprehensive and detailed</div></td></tr></tbody></table>

Adaptive Vs Predective Approach

<p><span style="font-size: 18px">Agile planning is a methodology used to deliver projects more efficiently and effectively by breaking them down into manageable increments. It allows teams to adapt to changing requirements and deliver value iteratively. Here are the key components and steps involved in Agile planning:</span></p><h2>Key Components of Agile Planning<br></h2><ol><li><span style="font-size: 16px"><strong>Product Backlog</strong>: A prioritized list of features, enhancements, bug fixes, and other work items for the product.</span></li><li><span style="font-size: 16px"><strong>Sprint Planning</strong>: A meeting where the team selects items from the product backlog to work on during the upcoming sprint.</span></li><li><span style="font-size: 16px"><strong>Sprints</strong>: Short, time-boxed periods (usually 1-4 weeks) during which the team works on the selected items.</span></li><li><span style="font-size: 16px"><strong>Daily Standups</strong>: Short, daily meetings where team members discuss their progress, plans for the day, and any impediments.</span></li><li><span style="font-size: 16px"><strong>Sprint Review</strong>: A meeting at the end of the sprint to demonstrate the completed work to stakeholders.</span></li><li><span style="font-size: 16px"><strong>Sprint Retrospective</strong>: A meeting after the sprint review to discuss what went well, what didn't, and how to improve.</span></li></ol><div class="se-component se-image-container __se__float-none"><figure><img src="https://www.api.cstechie.com/upload/editor-image/agile-planning_1737959741272.png" alt="Agile Planning" data-rotate="" data-proportion="true" data-size="," data-align="none" data-percentage="auto,auto" data-file-name="agile-planning.png" data-file-size="138471" data-origin="," style=""></figure></div><p style="text-align: center">Agile Planning Image<br></p><h2>Steps in Agile Planning</h2><ol><li><span style="font-size: 16px"><strong>Define the Vision and Goals:</strong></span><ul><li style="font-size: 16px">Understand the product vision and business goals.</li><li style="font-size: 16px">Identify stakeholders and their needs.</li></ul></li><li><span style="font-size: 16px"><strong>Create and Prioritize the Product Backlog:</strong></span><ul><li style="font-size: 16px">Work with stakeholders to gather requirements and create user stories.</li><li style="font-size: 16px">Prioritize the user stories based on business value, risk, and dependencies.<br></li></ul></li><li><span style="font-size: 16px"><strong>Sprint Planning:</strong></span><ul><li style="font-size: 16px">Review the product backlog and select items for the upcoming sprint.</li><li style="font-size: 16px">Define the sprint goal and break down user stories into tasks.<br></li><li style="font-size: 16px">Estimate the effort required for each task (using story points, hours, etc.).<br></li></ul></li><li><span style="font-size: 16px"><strong>Execute the Sprint:</strong></span><ul><li style="font-size: 16px">Team members work on the tasks, attending daily standups to coordinate and resolve issues.</li><li style="font-size: 16px">Use a task board (e.g., Kanban) to track progress.<br></li></ul></li><li><span style="font-size: 16px"><strong>Sprint Review and Retrospective</strong>:<br></span><ul><li style="font-size: 16px">Demonstrate the completed work to stakeholders during the sprint review.</li><li style="font-size: 16px">Gather feedback and update the product backlog as needed.<br></li><li style="font-size: 16px">Conduct a sprint retrospective to discuss improvements for the next sprint.<br></li></ul></li><li><span style="font-size: 16px"><strong>Iterate and Improve</strong>:<br></span><ul><li style="font-size: 16px">Apply insights from the retrospective to improve processes.</li><li style="font-size: 16px">Repeat the cycle, continuously delivering increments of the product and refining the approach.<br></li></ul></li></ol>

Agile Planning

<h2>There Are three concepts for Agile planning:</h2><ol><li style="font-size: 16px">Effort vs Duration.</li><li style="font-size: 16px">Accuracy vs Precision.</li><li style="font-size: 16px">Relative vs Absolute.</li></ol><h3>1. Effort vs. Duration:</h3><p><span style="font-size: 18px"><strong>Effort</strong>:</span></p><ul><li style="font-size: 16px">Effort is about the amount of work required to complete a task or project.</li><li style="font-size: 16px">It's measured in units like person-hours, person-days, or story points.</li><li style="font-size: 16px">Effort is not tied to the calendar but rather to the work itself.</li><li style="font-size: 16px">Think of it this way: if a task needs 40 hours of effort, that's 40 hours of work regardless of whether you spread it over a week, a month, or get multiple people to work on it.</li></ul><p><span style="font-size: 18px"><strong>Duration</strong>:</span></p><ul><li style="font-size: 16px">Duration is the actual time that will pass from the start to the finish of a task or project.</li><li style="font-size: 16px">It's measured in calendar days, weeks, or months.</li><li style="font-size: 16px">Duration depends on how many people are working on the task and their availability.</li><li style="font-size: 16px">For example, if one person works full-time on a 40-hour task, the duration is 5 days. If two people work on it, the duration might be 2.5 days.</li></ul><p><br></p><div class="se-component se-image-container __se__float-none" style="width: 100%"><figure style="width: 100%;"><img src="https://www.api.cstechie.com/upload/editor-image/effort-vs-duration_1722235155334.png" alt="Effort vs Duration in Agile" data-rotate="" data-proportion="true" data-size="100%," data-align="none" data-percentage="100," data-file-name="effort-vs-duration.png" data-file-size="43213" data-origin="," style="width: 100%;"></figure></div><p><br></p><p><span style="font-size: 18px"><strong>In Summary</strong>:</span></p><ul><li style="font-size: 16px">Effort is about the total work needed; duration is about the total time taken.</li><li style="font-size: 16px">They are connected but not the same: a high-effort task can have a short duration if many people work on it, and a low-effort task can have a long duration if resources are limited.</li></ul><p><br></p><h3>2. Accuracy vs. Precision:</h3><p><span style="font-size: 18px"><strong>Accuracy</strong>:</span></p><ul><li style="font-size: 16px">Accuracy is about how close your estimate or measurement is to the actual value or outcome.</li><li style="font-size: 16px">If you estimate a task will take 10 hours and it actually takes 10 hours, your estimate is accurate.</li></ul><p><span style="font-size: 18px"><strong>Precision</strong>:</span></p><ul><li style="font-size: 16px">Precision is about the consistency and detail of your estimates or measurements.</li><li style="font-size: 16px">If you repeatedly estimate tasks with very similar outcomes, your estimates are precise.</li><li style="font-size: 16px">For example, estimating a task will take exactly 10.1234 hours is precise, but it may not be accurate if the actual time varies widely.</li></ul><div class="se-component se-image-container __se__float-none" style="width: 100%"><figure style="width: 100%;"><img src="https://www.api.cstechie.com/upload/editor-image/accuracy-precision_1722925645587.png" alt="Accuracy vs. Precision" data-rotate="" data-proportion="true" data-size="100%," data-align="none" data-percentage="100," data-file-name="accuracy-precision.png" data-file-size="49690" data-origin="," style="width: 100%;"></figure></div><p><span style="font-size: 18px"><strong>In Summary</strong>:</span></p><ul><li style="font-size: 16px">Accuracy means getting close to the actual value; precision means being consistently detailed.</li><li style="font-size: 16px">Ideally, you want both accurate and precise estimates, but in practice, it's often more important to be accurate in Agile planning.</li></ul><p><br></p><h3>3. Relative vs. Absolute Estimation:</h3><p><span style="font-size: 18px"><strong>Relative Estimation</strong>:</span></p><ul><li style="font-size: 16px">This involves comparing the size or complexity of tasks against each other rather than assigning fixed time units.</li><li style="font-size: 16px">Common in Agile, using techniques like story points or t-shirt sizes (e.g., small, medium, large).</li><li style="font-size: 16px">For instance, if Task A is twice as complex as Task B, and Task B is 2 story points, then Task A is 4 story points.</li></ul><p><span style="font-size: 18px"><strong>Absolute Estimation</strong>:</span></p><ul><li style="font-size: 16px">This involves estimating the effort or duration in fixed time units, such as hours or days.</li><li style="font-size: 16px">More traditional and straightforward but can be challenging in the face of uncertainties.</li><li style="font-size: 16px">For example, estimating that Task A will take exactly 8 hours.</li></ul><p><span style="font-size: 18px"><strong>In Summary</strong>:</span></p><ul><li style="font-size: 16px">Relative estimation focuses on comparing tasks to each other, making it flexible and adaptive to changes.</li><li style="font-size: 16px">Absolute estimation provides concrete timelines but can be hard to get right in complex projects.</li><li style="font-size: 16px">Agile prefers relative estimation for its adaptability and ease of comparison.</li></ul>

Agile Planning Concepts

<h2>Estimation Process:<br></h2><p><span style="font-size: 18px"><strong>Agile Estimation</strong> is the process of predicting the amount of effort, time, and resources required to complete a piece of work in an agile project. It typically involves the entire team and relies on relative estimation techniques.</span><br></p><h2><span style="font-size: 18px">1. Who is responsible for estimation?<br></span></h2><p><span style="font-size: 18px">Ans : Development Team<br></span></p><h2><span style="font-size: 18px">2. How Long does it takes ?<br></span></h2><p><span style="font-size: 18px">Ans: Depends on Estimation style, methods, number of stories, understanding of the domain and expertise of the team.<br></span></p><h2>Estimation Techniques:<br></h2><h3>Planning Poker</h3><p><span style="font-size: 18px"><strong>Planning Poker</strong> is a collaborative estimation technique that involves team members assigning story points to tasks based on their complexity.</span></p><ul><li style="font-size: 18px">Each team member selects a card representing their estimate.</li><li style="font-size: 18px">All cards are revealed simultaneously.</li><li style="font-size: 18px">Discussions follow if there are discrepancies, and the process repeats until consensus is reached.</li></ul><h2><br></h2><h3>T-Shirt Sizes</h3><p><span style="font-size: 18px">Tasks are categorized into sizes (XS, S, M, L, XL) based on their complexity. This technique is quick and useful for initial estimations.</span></p><p></p><h3>Bucket System</h3><p><span style="font-size: 18px">Tasks are placed into "buckets" representing different ranges of effort (e.g., 1-2 points, 3-5 points). This helps in quickly categorizing tasks based on effort.</span></p><h3>&nbsp;Dot Voting</h3><p><span style="font-size: 18px">Team members vote on the complexity of tasks using dots or stickers. The task with the most dots is considered the most complex, and so on.</span></p><h2><br></h2><h2>Steps in the Agile Estimation Process</h2><ol><li><p><span style="font-size: 18px"><strong>Preparation</strong>:</span></p><ul><li style="font-size: 18px">Gather the team and ensure everyone understands the estimation techniques.</li><li style="font-size: 18px">Prepare a list of tasks or user stories to be estimated.</li></ul></li><li><p><span style="font-size: 18px"><strong>Initial Estimation</strong>:</span></p><ul><li style="font-size: 18px">Use a technique like Planning Poker to provide initial estimates for tasks.</li><li style="font-size: 18px">Discuss any discrepancies and refine estimates as needed.</li></ul></li><li><p><span style="font-size: 18px"><strong>Review and Adjust</strong>:</span></p><ul><li style="font-size: 18px">Regularly review estimates during sprint planning and adjust based on new information or changes in scope.</li></ul></li><li><p><span style="font-size: 18px"><strong>Track and Learn</strong>:</span></p><ul><li style="font-size: 18px">Track actual effort against estimates to identify discrepancies.</li><li style="font-size: 18px">Use these insights to improve future estimations.</li></ul></li></ol><h2><br></h2><h2>Best Practices</h2><ul><li style="font-size: 18px"><strong>Collaborative Estimation</strong>: Involve the entire team in the estimation process to leverage diverse perspectives.</li><li style="font-size: 18px"><strong>Use Historical Data</strong>: Reference past project data to inform current estimates.</li><li style="font-size: 18px"><strong>Continuous Improvement</strong>: Regularly review and adjust estimation techniques based on team feedback and project outcomes.</li><li style="font-size: 18px"><strong>Focus on Value</strong>: Prioritize tasks that deliver the most value to the customer.</li></ul><h2><br></h2><h2>Example of the Estimation Process</h2><p><span style="font-size: 18px">Let’s go through an example using Planning Poker:</span></p><ol><li><p><span style="font-size: 18px"><strong>Prepare the Stories</strong>:</span></p><ul><li style="font-size: 18px">User Story 1: "As a user, I want to log in so that I can access my account."</li><li style="font-size: 18px">User Story 2: "As a user, I want to reset my password so that I can regain access to my account."</li></ul></li><li><p><span style="font-size: 18px"><strong>Conduct Planning Poker</strong>:</span></p><ul><li style="font-size: 18px">Team members discuss User Story 1.</li><li style="font-size: 18px">Each member selects a card (e.g., 3, 5, 8 story points).</li><li style="font-size: 18px">Cards are revealed: 3, 5, 5, 8.</li><li style="font-size: 18px">Discuss differences: The member who selected 8 explains their reasoning (e.g., complexity in handling errors).</li><li style="font-size: 18px">Reach consensus: After discussion, all agree on 5 story points.</li></ul></li><li><p><span style="font-size: 18px"><strong>Repeat for User Story 2</strong>:</span></p><ul><li style="font-size: 18px">Similar process: Discuss, select cards, reveal, and reach consensus.</li></ul></li></ol>

Comments

Agile Software Development

Introduction