Scrum Basics for Beginners

Introduction to Scrum

Scrum is an agile framework primarily used for managing software development projects, though its principles can be applied to various fields. The term “Scrum” comes from rugby, where it refers to a formation where team members work closely together to move the ball forward. Similarly, in project management, Scrum emphasises teamwork, accountability, and iterative progress towards a well-defined goal.

What is Scrum?

Scrum is designed to help teams work together. It encourages teams to learn through experiences, self-organise while working on a problem, and reflect on their wins and losses to continuously improve. Scrum is structured around the principles of transparency, inspection, and adaptation, providing a robust framework that helps teams address complex adaptive problems while delivering products of the highest possible value.

Key Components of Scrum

Scrum comprises several essential elements:

• Roles: Product Owner, Scrum Master, and Development Team.
• Artefacts: Product Backlog, Sprint Backlog, and Increment.
• Events: Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.

Roles in Scrum

1. Product Owner: The Product Owner represents the stakeholders and the voice of the customer. They are responsible for defining the features of the product and prioritising the work to be done. They ensure that the team delivers value to the business.
2. Scrum Master: The Scrum Master serves as a facilitator for the team, ensuring that the Scrum process is followed. They help remove obstacles that impede the team's progress and foster an environment conducive to completing the project.
3. Development Team: This is a group of professionals who do the work of delivering a potentially releasable increment of "Done" product at the end of each Sprint. Development Teams are structured and empowered by the organisation to organise and manage their own work.

Artefacts of Scrum

1. Product Backlog: This is a dynamic list of features, requirements, enhancements, and fixes that acts as the team's to-do list. It is constantly refined and prioritised by the Product Owner to meet the project's needs.
2. Sprint Backlog: This is a list of tasks identified by the Scrum Team to be completed during the Scrum Sprint. It represents a commitment by the team to deliver a set of product functionality within a Sprint.
3. Increment: This is the sum of all the Product Backlog items completed during a Sprint and all previous Sprints. At the end of a Sprint, the new Increment must be "Done," meaning it must be in a usable condition and meet the Scrum Team's definition of "Done."

Events in Scrum

1. Sprint: The heart of Scrum is a Sprint, a time-box of one month or less during which a "Done," usable, and potentially releasable product Increment is created. Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint.
2. Sprint Planning: This event initiates the Sprint by laying out the work to be performed. The plan is created collaboratively by the entire Scrum Team.
3. Daily Scrum: A 15-minute time-boxed event held every day to synchronise activities and create a plan for the next 24 hours. It improves communication, eliminates other meetings, identifies impediments to development, highlights and promotes quick decision-making, and improves the Development Team's level of knowledge.
4. Sprint Review: Held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint. Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on the next things that could be done.
5. Sprint Retrospective: This is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. The purpose is to plan ways to increase quality and effectiveness.

Different Versions of Agile

Agile

Agile is an umbrella term for several iterative and incremental project management methodologies. The core principles are outlined in the Agile Manifesto, which emphasises:

• Individuals and interactions over processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan

Kanban

Kanban is a visual workflow management method that helps teams visualise their work, maximise efficiency, and improve continuously. It is based on the following principles:

• Visualise work
• Limit work in progress
• Focus on flow
• Continuous improvement

Kanban uses a board (physical or digital) to visualise the flow of work. Work items are represented by cards on the board, and the board is typically divided into columns that represent different stages in the workflow.

Scrumban

Scrumban is a hybrid methodology that combines elements of Scrum and Kanban. It is designed to help teams transition from Scrum to Kanban or to use both methodologies concurrently. Scrumban retains the structure of Scrum with roles, events, and artefacts but incorporates Kanban's visualisation and continuous flow principles.

Basics for Each Role in Scrum

Product Owner

• Define and prioritise the product backlog
• Ensure that the backlog is visible, transparent, and clear to all
• Make decisions regarding the product and its features
• Work closely with stakeholders to gather and communicate requirements

Scrum Master

• Facilitate Scrum events and ensure they are productive and within time-boxes
• Remove impediments to the Development Team's progress
• Coach the team in self-organisation and cross-functionality
• Ensure that the Scrum framework is followed

Development Team

• Deliver increments of potentially releasable functionality at the end of each Sprint
• Self-organise to accomplish the work in the Sprint Backlog
• Collaborate with the Product Owner to clarify requirements
• Participate actively in Scrum events

How Roles Work with a Program and/or Project Manager

In traditional project management, a Project Manager is responsible for defining, planning, tracking, and managing the project. However, in Scrum, these responsibilities are distributed among the Product Owner, Scrum Master, and Development Team.

• Product Owner takes on the role of defining and prioritising work.
• Scrum Master ensures that the Scrum process is followed and removes obstacles.
• Development Team is responsible for delivering the work.

In a larger context, such as a program involving multiple teams, a Program Manager might work to ensure that the various Scrum Teams are aligned with the broader objectives of the program. They may coordinate between teams, manage dependencies, and communicate progress to stakeholders.

Program Manager's Role

• Oversee multiple projects or teams to ensure alignment with the program's goals
• Manage interdependencies between teams
• Facilitate communication and collaboration among teams
• Ensure that each team's output aligns with the program's objectives

Project Manager's Role in Agile

In an Agile environment, the traditional role of a Project Manager may evolve into more of a facilitative and supportive role. The role helps to coordinate efforts across multiple teams and ensures that each team has the resources and support they need to succeed. They may also work closely with Product Owners and Scrum Masters to ensure that the overall project objectives are being met.

Conclusion

Scrum provides a robust framework for managing complex projects by emphasising teamwork, accountability, and iterative progress. By understanding the roles, artefacts, and events in Scrum, teams can improve their efficiency and deliver high-quality products. Agile methodologies like Scrum, Kanban, and Scrumban offer various approaches to managing work and can be tailored to fit the needs of different projects and organisations.

As a Program Manager, embracing Scrum can lead to more effective project delivery, improved team dynamics, and greater satisfaction among stakeholders. Whether you are new to Scrum or looking to deepen your understanding, the key to success lies in continuous learning, adaptation, and collaboration.

References:

1. McCarthy, R. (n.d.). Lean Methodology: A Guide to Lean Six Sigma, Agile Project Management, Scrum, and Kanban for Beginners.
2. Malakar, S. (n.d.). AGILE in Practice: Practical Use-cases on Project Management Methods including Agile, Kanban, and Scrum.
3. The Academy, Gross, E., & Stanley, J. (n.d.). The Project Management Handbook: Simplified Agile, Scrum, and DevOps for Beginners.