What is Scrum?

Although it is one of the agile practices more adopted in the world, not many know that Scrum earned its name from the term rugby.

When you consider everything that Scrum and rugby have in common, it makes sense. Both the framework Agile as the game focus on team work. The team structures consist of a small group of people, and all have a crucial role to play in the achievement of a goal that is understood by both parties, either win the match or deliver a functional application of Low-Code.

The best way to succeed with Scrum is to sort the composition of his team. Continue reading to see who is on the team Scrum, how must you assign the job to the team on a project, the best practices of the team in Scrum, the recommended size of a team Scrum and general advice on the structure of the team Agile.

What is Scrum?

Scrum is a framework for agile team in the development of products. Gartner explains that the teams Scrum used an approach iterative and incremental framework for solving complex problems by working in short periods of time of approximately 2 weeks, also known as sprints.

As project management framework, Scrum is hugely popular due to its lightweight nature. Gartner has even topped the practical as the framework Agile dominant.

The ideal structure of the team Scrum

There are three main roles that play a role in the team in Scrum: product owner, teacher of scrum and developer. Stakeholders and commercial specialists are also involved to varying degrees with the majority of the projects Agile. In larger companies, there are usually several members of the sales team involved in the development process.

What is the recommended size for a team is scrum?

Tip: Keep the equipment simple and consistent. Do not make up new roles or add temporary members to the team.

For projects of large companies, the ideal size of the team in Scrum is 7 people (product owner, teacher of scrum and 5 developers).

The smaller projects usually consist of 4 team members (product owner, teacher of scrum and 2 developers). The smaller teams that this technically would not be Scrum, since there would be many overhead with all the activities.

Ultimately, a team Scrum must consist of at least 9 people.

How must you assign the job to the team on a project Scrum?

Owner of the product

The product owner is responsible for defining the direction of a project. Have a clear understanding of what the company and the users are in need of the product being developed, and translate these needs to the team of Scrum.

The owners of the products ensure that the product is being developed to provide the maximum value to the company and the users. This role also prioritizes the work and manages the accumulation of products to advance the production.

Master of Scrum

The master of Scrum ensures that the team follow the best agile practices and is responsible for addressing and remove any blockage of productivity that may arise. Essentially, the master Scrum is the authority on Agile and Scrum.

The Scrum Masters should be the leaders of support. Help the product owner to define the value of the product and to plan the work and manage the build. They also help the developers to self-organize.

the development team

The development team is a group of people with the skills necessary to build the product as intended by the product owner. The computer does not always include only developers: architects, writers, designers, and other specialized roles are also considered to be part of the development team.

Developers are self-organized and are the authorities of their domain when it comes to determining how the work will be done and planning the build. As a general rule of Scrum, the collaboration is involved in their daily functions. Determine how to perform the work to create the product and work autonomously to manage and complete their work.

The business

Many companies work in close collaboration with the commercial team to collect and clarify the organisational requirements for the product in development. The commercial team has the experience and knowledge that can be extremely useful for a development project, but they are not considered an official part of a team Scrum. In contrast, a representative of the commercial team, sometimes called a business owner, acts as the sponsor of the team Scrum.

Subject matter experts (SMES)

From the perspective of the team in Scrum, an SME is a person who possesses knowledge crucial that the team needs for the successful delivery of the product. For example, if you are creating a new application to automate the billing process, your SME could be an authority in the billing department or finance. You will learn the ins and outs of the billing process and can offer their expertise to ensure that the new application meets the needs of both the company and the users.

The team of Scrum may need to Smes for different purposes and at different times, and Smes are responsible for responding to questions and perform tasks to improve the product. During the planning meetings, the SMES need to know when it is waiting for information or action from them. A team member, Scrum can do a follow-up with SMES to complete the action in time to avoid any delays in the delivery of the product.

Smes are also considered to be stakeholders but not all stakeholders are smes. A team member of a team Scrum can even be a SME for the other team Scrum. But remember: an sme does not form part of the team Scrum. And as such, this person may not be held liable for any work done for the team.

5 characteristics of a team Scrum successful

Below, is a list of features that it is important to keep in mind when creating your team Scrum.

1. Self-management

The members of each team Scrum decide how they will group together. Each member is equally important (without hierarchy), but the responsibilities are clearly defined. This means that each member of the team should have the same opportunity to express their opinion. Together, they can reach a solution.

In the last instance, the product owner has the final word on the prioritization and the master Scrum guide everyone to agree on a solution.

2. Communication

Scrum is a close collaboration. Ideally, the entire team would be sitting in the same room without communication barriers. But remote work has made things a little more difficult.

Remote teams need to stay connected and committed. For a team Scrum successful, create channels of communication open with scheduled check-ins, weekly meetings and a channel in Slack.

3. Dedicated

Each member of the team should be assigned to the project full-time. Any distraction will only delay the work. The work focused on is much more effective than switching between tasks or to split your attention between two projects. To be dedicated to a single project is also the best way to take ownership and responsibility, which allows a better self-management.

4. Long life

Avoid making frequent changes in the structure of your team Scrum. The new equipment Scrum need time to learn to work together. Even the changes between projects will require time for the team to adapt.

5. Multifunctional

The team must possess the specialized knowledge required to deliver a working product. This includes team members with experience in development, quality control, user experience, integrations, and other aspects.

However, it is not always realistic that the members of the team Scrum have a detailed knowledge about the integrations with other systems. In this case, make sure that your computer has access to all the knowledge you need. Depending on the size and complexity of the project, it might make sense to include the expert in integration, QA-er or UX-er as a team member, Scrum full-time. But if you're working in a small team of Scrum, submitting to these experts would generate too much overhead. In such cases, you need an SME.

Do you wonder how it fits in the development of Low-Code? Watch this video to see how the platform Low-Code of Mendix incorporates the tools that teams Scrum need to be successful.

Please contact us to request information from Mendix