Agile Scrum Method

Agile is an iterative and incremental approach to software development that emphasizes flexibility, collaboration, and customer feedback. It involves breaking projects into small increments called "sprints," which typically last from one to four weeks. This methodology prioritizes delivering working software frequently, often every few weeks, and encourages adaptability to changing requirements throughout the development process. Agile teams collaborate closely with stakeholders, continuously refining and improving the product based on feedback and evolving needs.

Scrum is agile framework for managing and organising work especially in software development. It provides a way for team to collaborate and deliver high value product iteratively.

Key concepts

  • Sprint
    • Development cycle in scrum are called sprint. Those are short periods (mostly two week ) where shippable product increments are created.
  • Artifacts
    • Product Backlog: A prioritised list of features, enhancements and bug fixes that represent the requirements for the product.
    • Sprint Backlog:  The Sprint Backlog is a subset of the Product Backlog, consisting of the Product Backlog items selected for the current sprint, plus a plan for delivering the product increment and achieving the sprint goal.
    • Increment: The increment in Scrum is a visible and tangible outcome of the team's work during a sprint.        
  • Role
    • Product Owner: Represents the customer, defines the product backlog and ensures that the team works on the most valuable feature. 
    • Scrum Master: Facilitates the scrum process, helps the team to remove any obstacles and ensures scrum practises are followed. Sets up the meetings and monitor the work being done and facilitates the release planning.
    • Development Team: Responsible for delivering the product increment iteratively and incrementally through collaboration, cross functional and self organisation.
  • Events
    1. Product Backlog Refinement: The Product Owner collaborates with stakeholders to create and prioritize a Product Backlog, which is a prioritized list of all desired features, enhancements, and fixes for the product.
    2. Sprint Planning: At the beginning of each Sprint, the Scrum Team holds a Sprint Planning meeting. During this meeting, the Product Owner presents the highest-priority items from the Product Backlog to the Development Team. The team then selects the items they believe they can complete during the Sprint and commits to delivering them.
    3. Sprint Execution: The Development Team works on the selected items from the Product Backlog during the Sprint. They collaborate closely to design, code, test, and integrate the features incrementally.
    4. Daily Standup (Daily Scrum): Each day during the Sprint, the Development Team holds a Daily Standup meeting. This is a short, time-boxed meeting where team members provide updates on what they've done since the last meeting, what they plan to do next, and any impediments they're facing. The focus is on coordination and identifying any obstacles to progress.
    5. Sprint Review: At the end of the Sprint, the Scrum Team conducts a Sprint Review meeting. They demonstrate the completed work to the stakeholders and gather feedback. The Product Owner reviews the Product Backlog and may adjust priorities or add new items based on feedback.
    6. Sprint Retrospective: Following the Sprint Review, the Scrum Team holds a Sprint Retrospective meeting. During this meeting, the team reflects on their performance during the Sprint and identifies opportunities for improvement. They discuss what went well, what could be improved, and any action items to implement in the next Sprint.
    7. Incremental Delivery: Throughout the Sprint, the Development Team works to deliver a potentially shippable product increment. At the end of each Sprint, this increment is reviewed and potentially released to customers.
    8. Adaptation: Scrum emphasizes inspection and adaptation. Based on feedback from stakeholders, the team may adjust their approach, refine the Product Backlog, and make changes to improve future Sprints.

Burndown Chart

These are a valuable tool for Scrum teams and stakeholders to visually track progress, make informed decisions, and ensure that the work is on track to be completed within the sprint or project timeline. These help teams track their velocity, which is the rate at which they are completing work. This information can be valuable for future sprint planning and improving the team's estimation accuracy.

Comments

Post a Comment

Popular posts from this blog

Transform values with a stream

The goal is to transform an array of numbers into a comma-delimited string using functional programming. The code snippet you provided has a minor issue: String.join(",", strings[0]) is incorrect because it tries to join a single element ( strings[0] ) rather than all elements in the strings array. Here's the corrected code for the transformValues method: import java.util.Arrays; class Answer {     // Change these boolean values to control whether you see      // the expected answer and/or hints.     static boolean showExpectedResult = true;     static boolean showHints = true;     // Transform an array of numbers into a comma-delimited list     // using functional programming.     static String transformValues(int[] numbers) {         // Convert the int array to a stream of integers         // Map each integer to its String representation         // ...
Read more

Collections Framework

 The Java Collections Framework provides a comprehensive set of interfaces, implementations, and algorithms to work with collections of objects in Java. It offers a unified architecture for representing and manipulating collections, making it easier to work with data structures in Java programs. The Collections Framework is a fundamental part of Java programming and is widely used in various applications ranging from simple data manipulation tasks to complex algorithms and data processing pipelines.  Key components of the Collections Framework: Interfaces Collection : The root interface of the Collections Framework hierarchy. Represents a group of objects, known as elements. Subinterfaces include List , Set , and Queue . List : Represents an ordered collection of elements where duplicate elements are allowed. Allows elements to be accessed and inserted by index. Implementations include ArrayList , LinkedList , and Vector . Set : Represents a collection of unique elements ...
Read more

Inspect a collection

Calculate the cart total  import java.util.List; import java.util.concurrent.atomic.AtomicReference; public class Main {     public static void main(String[] args) {         List<Item> items = List.of(             new Item("Item1", 10.0f, 2),             new Item("Item2", 5.0f, 4),             new Item("Item3", 20.0f, 1)         );         float total = getCartTotal(items);         System.out.println("Cart Total: " + total);  // Output: Cart Total: 60.0     }     static float getCartTotal(List<Item> items) {         AtomicReference<Float> total = new AtomicReference<>(0.0f);         items.forEach(item -> {             total.updateAndGet(v -> v + item.getQuantity() * item.getPrice())...
Read more