Scrum in management systems: streamline and improve your projects

Scrum is a framework that originated in the world of software, but today shows enormous potential to transform the way organizations manage complex projects of various kinds, including ISO management system implementation projects. In this sense, effective management of Scrum in management systems is a fundamental strategy for the success and efficiency of organizations in a business environment marked by competitiveness and dynamism.

What is Scrum?

Scrum is an agile framework that allows projects to be managed in an iterative, incremental, and collaborative manner. Instead of moving forward with large, rigid, linear plans, Scrum divides the work into short cycles, called sprints, where real value is delivered from the outset and lessons are learned with each iteration.

It is worth noting that Scrum originated in the world of software development, but its applicability has spread to a wide range of projects, including those related to the implementation of management systems, focusing on flexibility, collaboration, and incremental delivery of value.

In the Scrum methodology, projects are divided into iterations called “sprints,” which typically last 2 to 4 weeks. During each sprint, the team works on a set of priority tasks, known as “user stories,” which have been selected from the project backlog, which is an ordered and emerging list of all the work needed to improve a product. At the end of each sprint, a functional product increment is delivered that can be reviewed and evaluated by the customer or stakeholder team.

In the following video, you can complement your understanding of what the Scrum approach is.

Scrum roles

The Scrum framework is based on an intentionally non-hierarchical team structure, where success or failure rests with the Scrum Team as a whole. Unlike traditional models, there are no “bosses” or subordinate relationships. Instead, authority and decision-making power are distributed. This arrangement encourages self-organization among developers and ensures maximum flexibility in addressing the complexity of development.

The Scrum team is made up of:

Scrum Master

Facilitates the process, removes barriers, promotes best practices, and ensures that the team functions well. Is not a boss. Is an enabler, i.e., a servant leader for the Scrum Team. Their primary responsibility is to ensure that SCRUM is understood and applied, emphasizing:

• Facilitator: Helps the Scrum Team remove impediments (obstacles) that slow down their work.
• Coach: Trains the team, Product Owner, and organization in the values, principles, and practice of SCRUM.
• Process Guardian: Protects the team from external interruptions (unplanned work or distractions).
• Event Facilitation: Ensures that SCRUM events are carried out effectively and within their time limits (Time-Box).

Product Owner (PO)

Manages priorities, represents internal or external clients, and decides what adds the most value. Their role is key to maintaining focus. They are ultimately responsible for maximizing the value of the product resulting from the Development Team’s work. Their key responsibilities include:

• Product Backlog Management: Is solely responsible for managing the Product Backlog, including its content, order, and clarity.
• Prioritization: Decides which items are most important to the customer and the business, ensuring that the team works on the highest-value tasks first.
• Customer Representative: Serves as the voice of customers and stakeholders for the Development Team.
• Acceptance/Rejection: Accepts or rejects the Increment (the result of the Sprint) in the Sprint Review.

Development Team/Work Team/Developers

A multidisciplinary group that performs the technical work to deliver the Product Increment. In Scrum, the team is self-organizing, multidisciplinary, and results-oriented, not task-oriented. Its main responsibilities include:

• Transform requirements into functional increments.
• Self-organize to plan how to do the work.
• Comply with the Definition of Done (DoD).
• Collaborate daily to maintain agility and quality.
• Propose technical and process improvements.

The key to this system is the responsibility distributed among its three essential and complementary roles. Each role (Product Owner, Scrum Master, and Developers) has clear and exclusive responsibilities that ensure the flow of value. This makes the structure a cohesive unit that is collectively accountable for the delivery of the increment, ensuring product transparency and process efficiency.

Scrum artifacts: The pillars of transparency and commitment

Scrum artifacts are concrete representations of work and value. Their primary purpose is to maximize transparency of information so that the entire Scrum Team and stakeholders have a shared understanding of progress, product status, and remaining work. Each artifact contains an associated commitment (the Product Goal, Sprint Goal, and Definition of Done), which provides focus and encourages decision-making based on concrete facts rather than assumptions.

Product Backlog

The Product Backlog is the single, authoritative source of all work to be done for the product. It is a dynamically prioritized list, maintained by the Product Owner, that continuously evolves and refines as more is learned about the market and users. Its goal is to maximize value in each Sprint.

Sprint Backlog

This is the commitment of the Developers for the current Sprint. It consists of the set of items selected from the Product Backlog, plus the detailed plan to deliver the Increment and meet the Sprint Goal. This artifact is owned by the Developers, who have the autonomy to modify their work plan to achieve the goal.

Increase

The Increment is the sum of all Product Backlog items completed during a Sprint, along with the value of all previous Increments. It must be in a usable and potentially releasable condition, even if the Product Owner decides not to release it immediately. It represents a tangible step toward the Product Goal.

Scrum in ISO management systems

Applying SCRUM to the implementation of ISO management systems focuses on treating regulatory requirements as value elements to be delivered iteratively. The management system is built through short development cycles (Sprints), prioritizing the delivery of the documentation, processes, and tools necessary to achieve compliance. The following are key aspects to consider:

Mapping ISO requirements to the Product Backlog

The heart of this integration begins with the Product Backlog.

• Product Objective: This could be defined as certification, optimal functioning, and successful documentation of an ISO Management System process.
• Backlog Elements: Each requirement, clause, or mechanism for controlling the standard becomes an item in the Product Backlog.
• Prioritization: The Product Owner (often the Champion or Quality Manager) prioritizes these elements based on risk (which is most critical for certification) and value (which will provide the greatest early operational benefit).

Iterative delivery (Increment)

In each Sprint, the team commits to implementing a set of prioritized requirements.

Definition of Done: DoD is crucial. An ISO requirement is considered “Done” not only when it is documented, but when the associated process or policy is implemented, communicated, and ready for internal audit. This ensures that the increment at the end of each Sprint is a usable segment or portion of the Management System.

Tangible Increment: Increments may include the approved security or quality policy, the operational risk register, or the validated document control procedure, the purchasing process sheet, among others.

Adapted roles and responsibilities

The SCRUM roles maintain their purpose, but focus on the requirements of the ISO management system:

• Product Owner: The ISO expert or senior management representative responsible for the vision and prioritization of regulatory requirements.
• Scrum Master: Facilitates the adoption of SCRUM and removes impediments to the implementation of Scrum in the ISO project.
• Developers: The multifunctional team from management or the related department that designs, documents, and implements the processes and controls that comply with the standard.

This approach allows organizations to adapt quickly to implementation challenges, ensuring that the management system not only complies with the standard, but is also practical and adds real value to the business in an incremental manner.

Common challenges in integrating the Scrum methodology

Despite the benefits it offers, integrating this agile methodology into management system implementation projects can present several challenges. It is important to identify and address these challenges to ensure successful implementation. Some of the most common challenges include:

• Organizational culture change: Adopting Scrum often requires significant cultural change within the organization. This can involve challenges such as resistance to change from team members or senior management, and the need to promote a culture of transparency, collaboration, and self-organization.
• Alignment with existing processes and regulations: In some cases, existing processes and regulations within the organization may not be compatible with the agile principles of Scrum. This can lead to conflicts and obstacles in implementing the methodology, especially in projects that require compliance with specific regulations.
• Stakeholder and expectation management: Managing stakeholders and their expectations is essential to the success of any project. In management system implementation projects, there may be a wide range of stakeholders with divergent interests, which can hinder decision-making and consensus-building during project development.
• Project complexity: These projects are often complex and multifaceted, with multiple stakeholders and specific requirements. This can make it difficult to implement Scrum, especially if the team lacks prior experience with the methodology or if the project is too large or complex to be managed in an agile manner.
• Change management and resistance: The implementation of Scrum may encounter resistance from some team members or stakeholders who are accustomed to more traditional working methods. Change management and effective communication are essential to address this resistance and encourage the adoption of the agile methodology.

Overcoming challenges when implementing the SCRUM methodology

In the previous section, we identified some challenges that may arise when implementing the Scrum approach in the management of management system implementation projects. These challenges can be overcome if we consider aspects such as:

Backlog prioritization and management

One of the first steps when implementing Scrum in management system projects is creating and managing a work backlog. This backlog may include items such as drafting policies, procedures, forms, and other documents related to ISO 9001 requirements. It is crucial to prioritize these items based on their importance to compliance with the standard and business needs, allowing the team to focus on the most critical tasks in each sprint.

Iterations and incremental deliveries

Instead of trying to address all documents and processes at once, Scrum proposes working in iterations (sprints) to develop a portion of the backlog items in each cycle. For example, one sprint could be dedicated to drafting documented information management procedures, while another sprint could focus on job descriptions for the purchasing unit. This incremental delivery allows the team to obtain early feedback and adapt its approach as necessary.

Sprint planning and review meetings

At the beginning of each sprint, the team meets to plan which items from the backlog will be addressed during the sprint and how the work will be carried out. During these planning meetings, sprint goals are set and tasks are assigned to team members. At the end of each sprint, a sprint review is held to examine the completed documents and processes in order to provide feedback for future increments, thereby helping the team to continuously improve and adapt as the project progresses.

Collaboration and communication

Scrum encourages collaboration among team members and transparent communication about work progress. This is especially important in ISO 9001 or other ISO standard implementation projects, where coordination between different departments and functions is essential to ensure compliance with the standard’s requirements. Daily meetings (Daily Scrum) provide an opportunity for the team to stay aligned in their efforts and resolve any obstacles that may arise.

Continuous adaptation

One of its strengths is its ability to adapt as the project progresses and more information is gathered about the organization’s specific requirements and challenges.

How to effectively integrate Scrum into management system implementation projects

Effectively integrating Scrum into management system implementation projects requires a careful and strategic approach. Here are some strategies and best practices for successful integration:

Senior management commitment

It is essential that senior management supports and promotes the adoption of Scrum in the project. This may include allocating adequate resources, defining clear objectives, and setting realistic expectations about the benefits and challenges of the agile methodology.

Education and training

Providing adequate training and education in Scrum is essential to ensure that all team members understand the principles and practices of the methodology. This may include participation in training courses, hands-on workshops, and mentoring by subject matter experts.

Definition of roles and responsibilities

It is important to clearly define the roles and responsibilities of each team member within the Scrum framework. This includes roles such as the Scrum Master, Product Owner, and Development Team, as well as identifying key stakeholders and their involvement in the process.

Planning and prioritization

Proper planning and prioritization of project activities are critical to the success of SCRUM. This includes creating a prioritized product backlog, defining clear objectives and deliverables for each sprint, and holding sprint planning meetings to establish goals and scope of work.

Communication and collaboration

Effective communication and collaboration are fundamental pillars of the methodology. It is important to establish open and transparent channels of communication between all team members, as well as to encourage active collaboration and the exchange of ideas and knowledge.

Iteration and continuous improvement

Scrum aligns with the principle of continuous improvement. It is important to review and reflect on the work process after each sprint, identify areas for improvement, and make adjustments as necessary to optimize team performance and maximize the value delivered.

By following these strategies and best practices, teams can effectively integrate Scrum into management system implementation projects and maximize the benefits of the agile methodology.

Conclusions

The integration of the Scrum methodology into management system implementation projects offers a series of tangible and intangible benefits for organizations, enabling more agile, efficient, and effective project management. By adopting Scrum, organizations can improve their ability to respond to changes in the business environment, accelerate value delivery, and remain competitive in an ever-evolving market.

Its implementation can provide organizations with a significant competitive advantage by improving the agility, efficiency, and effectiveness of their projects. Incorporating and leveraging its principles and practices allows organizations to maximize the value delivered, minimize risk, and achieve their objectives more successfully.

References

1. Beck, K. et al. (2001). Manifesto for Agile Software Development. Agile Alliance. Cohn, M. (2005). Agile estimating and planning. Prentice Hall.
2. Denning, S. (2018). The age of agile: How smart companies are transforming the way work gets done. AMACOM.
3. Highsmith, J. (2009). Agile project management: Creating innovative products (2nd ed.). Addison-Wesley.
4. ISO. (2015). ISO 9001:2015 – Quality management systems — Requirements. International Organization for Standardization.
5. Project Management Institute. (2017). Agile practice guide. Project Management Institute.
6. Schwaber, K., & Sutherland, J. (2020). The Scrum Guide: The definitive guide to Scrum: The rules of the game. Scrum.org. 
7. Serrador, P., & Pinto, J. K. (2015). Does agile work? — A quantitative analysis of agile project success. International Journal of Project Management, 33(5), 1040–1051. 
8. Sutherland, J. (2014). Scrum: The art of doing twice the work in half the time. Crown Business.