Agile Scrum Activities

The Scrum framework is based on principles, values, and practices that provide a foundation for teams to implement specific approaches and engineering practices to realize Scrum practices. The outcome is a version of Scrum that is specific and unique, tailored to create a process that works effectively for the team.

Scrum Activities

Let's explore the main activities that make up the Scrum process:

1. Sprints

  • Work in Scrum is performed in cycles or iterations called Sprints, which can last up to 4 weeks.
  • Each Sprint aims to produce a potentially shippable product increment that delivers tangible value to the customer.
  • Sprints are time-boxed with fixed start and end dates, and typically, all Sprints have the same duration.
  • This iterative approach allows teams to adapt to changes and continuously improve the product.

2. Sprint Planning

  • Sprint Planning involves the Product Owner, Scrum Master, and Development Team collaborating to determine the most important subset of product backlog items to build in the next Sprint.
  • The team agrees on a Sprint Goal that defines what the upcoming Sprint is supposed to achieve.
  • The Development Team reviews the product backlog and determines the top priority items to accomplish in the next Sprint while maintaining a sustainable pace.
  • They break down targeted features into a set of tasks, forming the Sprint Backlog.

3. Sprint Execution

  • Once Sprint Planning is complete and the Sprint content is accepted, the Development Team, guided by the Scrum Master's training, performs all the task-level work required to get the features "Done."
  • Team members define their own task-level work and self-organize in the way they feel is best to achieve the Sprint Goal.
  • This autonomy empowers the team to manage their work effectively and adapt as needed.

4. Daily Scrum

  • Every day of the Sprint, typically at the same time, the Development Team holds a time-boxed Daily Scrum or Daily Stand-up.
  • Each team member answers three questions:
    • What did I accomplish since the last Daily Scrum?
    • What do I plan to work on by the next Daily Scrum?
    • What are the obstacles or impediments preventing me from making progress?
  • This meeting ensures everyone on the team understands what is occurring and helps manage the flexible, fast flow of work within a Sprint.

5. Definition of Done

  • In Scrum, the output of a Sprint is referred to as a potentially shippable product increment, meaning that whatever the Scrum Team has agreed to do is completed according to the Definition of "Done."
  • The Definition of Done is a shared understanding of what it means for work to be complete, ensuring transparency and quality.

6. Sprint Review

  • The Sprint Review is an event where the Scrum Team and stakeholders inspect the increment and adapt the product backlog if needed.
  • The main objective is to inspect and adapt the product being built.
  • Participants, including stakeholders, customers, sponsors, and the Scrum Team, discuss the completed features in the context of the overall development effort.

7. Sprint Retrospective

  • The Sprint Retrospective is the final meeting in the Sprint, where the Scrum Team reviews what could be improved for future Sprints and how to implement those improvements.
  • The purpose is to combine learnings from the last Sprint regarding people, relationships, processes, and tools.
  • The team identifies major items that went well and potential improvements, creating a plan to implement changes that increase product quality.