The Power of Scrum Methodology: How to Organize Projects and Deliver Value Continuously

What is the Agile Scrum Method?

Scrum is an agile methodology used to manage projects, primarily in software development. It stands out for being flexible and able to quickly adapt to changes while continuously delivering value to the customer. Instead of following a fixed plan, Scrum allows the team to adjust the project based on feedback received, keeping the customer at the center of the process.

I. Key Characteristics of Scrum

1. Iterative and Incremental: Work is divided into cycles called Sprints, lasting from 15 days to a month. Each Sprint produces a functional part of the product that can be tested and used.
2. Transparency and Continuous Feedback: Progress is constantly reviewed, and feedback from stakeholders is incorporated into each Sprint, ensuring that the final product meets customer needs.
3. Clearly Defined Roles and Responsibilities: Scrum defines three main roles, each with clear functions: Scrum Master, Product Owner (PO), and Development Team.
4. Structured Meetings: Scrum has regular events such as the Daily Scrum, Sprint Review, and Sprint Retrospective, which encourage communication and continuous improvement.

II. Difference from Traditional Approaches

• Traditional Approach (Waterfall): The project is planned in detail from start to finish, with no flexibility for changes.

• Scrum: Instead of following a rigid plan, Scrum works in short cycles and allows for continuous adjustments based on feedback and new information.

III. Roles in Scrum

• Scrum Master: The Scrum Master is the team facilitator, ensuring everyone follows Scrum practices correctly. He is not a boss but a "servant leader," whose main goal is to help the team be efficient. He removes obstacles that may hinder progress and promotes a collaborative environment.
• Product Owner (PO): The Product Owner is responsible for defining what will be developed. He prioritizes functionalities and ensures that the Product Backlog (task list) is always updated according to business priorities. His main function is to ensure that the development team focuses on the most important tasks.
• Development Team: The Development Team is the group of professionals that performs the technical work of transforming ideas and functionalities into a real product. They organize themselves autonomously to carry out tasks within each Sprint and deliver a product increment at the end.
• Human Resources (HR): Human Resources plays a crucial role in supporting the Scrum team by facilitating the hiring and development of skilled individuals. They help ensure that team members have the necessary training and resources to succeed in their roles. Additionally, HR may assist in resolving interpersonal conflicts and fostering a positive team culture that aligns with Agile values.
• Senior Management: Senior Management is responsible for providing the necessary support and resources for Scrum teams to operate effectively. They set the strategic vision and goals for the organization and ensure that Scrum initiatives align with business objectives. Senior management also plays a key role in removing organizational impediments and fostering an environment that encourages Agile practices.
• Business Group: The Business Group includes stakeholders from various departments who have an interest in the project's outcome. They provide insights and requirements that help shape the Product Backlog and ensure that the development aligns with business needs. Their involvement is critical during Sprint Reviews, where they can provide feedback on the product increment and help prioritize future work.

IV. Collaboration in Scrum

Collaboration among the Scrum Master, Product Owner, and Development Team is essential for Scrum's success. The Scrum Master ensures the team is flowing well, the Product Owner defines what needs to be done, and the Development Team performs the technical work, delivering results.

V. Key Artifacts of Scrum

1. Product Backlog: The Product Backlog is a list of everything that needs to be done in the project, including functionalities, fixes, and improvements. This list is prioritized by the Product Owner so that the team always works on the most important tasks.
2. Sprint Backlog: The Sprint Backlog is a selection of the highest-priority tasks from the Product Backlog that the team has decided to work on in a specific Sprint. It is the team's action plan for the upcoming weeks.
3. Increment: The Increment is the final result of the Sprint: a functional part of the product that can be tested or used by the customer. At the end of each Sprint, it is expected that there will be a usable increment.

VI. Difference Between Top and Bottom Backlog Stories

Stories at the top of the Product Backlog have higher priority and are more detailed, as they are closer to implementation. Stories at the bottom have lower priority and may still need more details and refinements before they are worked on.

VII. Key Events in Scrum

• Sprint: The Sprint is the heart of Scrum, a work cycle lasting from 15 days to a month. During the Sprint, the team develops a product increment.
• Sprint Planning Meeting: In the Sprint Planning Meeting, the team meets to define which tasks from the Product Backlog will be included in the next Sprint and how they will be executed.

• Daily Scrum: The Daily Scrum is a short meeting (15 minutes) where each team member answers three questions: What did I do yesterday? What will I do today? What are my obstacles?

• Sprint Review: In the Sprint Review, the team presents the product increment to the Product Owner and other stakeholders, who can provide feedback and approve the developed functionalities.

• Sprint Retrospective: The Sprint Retrospective is a meeting where the team discusses what went well and what needs improvement, always with the goal of enhancing the work process.

VIII. Contributions of the Daily Scrum and Sprint Retrospective

The Daily Scrum helps improve communication, ensuring that everyone on the team is aligned and ready to solve problems quickly. The Sprint Retrospective allows the team to assess what can be improved, promoting continuous improvement.

Who Am I?

I am Gabriel Lopes de Albuquerque, a student in the 3rd semester of Software Engineering at the University of Pernambuco (UPE). Focused on sharing the knowledge acquired during my course and implementing best practices in software development projects, I am always exploring new methodologies and technologies to enhance my skills. Here, I share my experiences and learnings on my academic journey.