Original link
Author: Mark Levison
With the implementation of Scrum, if you want to achieve long-term success, you need more than a basic framework. Scrum is deliberately designed this way, it provides a framework structure as a starting point, and it is born to be combined with other effective patterns.
Just like the design patterns advocated in the late 1990s, a pattern can be used independently or in combination with other patterns. For example, command mode and memo mode can be combined to build an efficient undo/restore system. Scrum is just a model designed for a team. It gives you the minimum rules and regulations to ensure that you can run. However, in many cases, you need to absorb other tools or models to build a more effective system.
In addition to Scrum, you should consider:
l Effective agile engineering practices-such as unit testing, continuous integration, test-driven development, acceptance test-driven development (or behavior-driven development), pair programming, etc. Without these practices, the health of the code will get worse and worse over time!
l Kanban -a tool used to help communicate and improve workflow within the team and between organizational levels. If we do not have a good understanding of the internal workflow of the organization, we may make a change that is beneficial to the part but hurts the whole.
l Portfolio management -this is the art of overall decision-making-focus on business and determine the focus of work. Organizations need to use portfolio management to ensure that the product owner understands the main priorities and that the team is working in accordance with the priority order.
l Organizational improvement- Many problems found during the implementation of Scrum cannot be solved by the team or the Scrum Master. Organizations need to set up a dedicated team aimed at continuous improvement to solve these problems.
l Internal team collaboration -how do you coordinate work among multiple teams? Implementing a layer of Scrum on top of Scrum is the most commonly used pattern, but it may not be the best choice.
l Team organization -how would you organize a team? Divide the team according to components? Or set up a fully functional team? Or use the Spotify model (such as groups, tribes, guilds, etc.)?
Translator's Note : Spotify is the world's largest genuine streaming music service platform. Its specific approach is to divide the company's business into several small pieces, which are called squads internally. Each group is like a separate startup company and runs completely independently. Related groups will form tribes. Each tribe will try to maintain autonomy and autonomy. For more in-depth communication and collaboration, Spotify will form some larger groups called chapters and guilds. According to Spotify’s internal survey, this way of working keeps the team fresh and agile. While the company’s employees and business are growing rapidly, employee satisfaction continues to rise.
There is no best practice !
Scrum could have brought all of these into the norm, but that would run counter to an important point of Agile-there is no best practice! A practice of working well in other organizations (or in a specific environment), you may copy it but it may not work. This phenomenon is especially obvious when solving work efficiency problems in large organizations , and this type of organization has just emerged with some repeatable patterns. Even if some fixed patterns begin to take shape (such as large-scale Scrum, enterprise-level Scrum, etc.), the question is still unclear in which particular situation to adopt which model.
Finally, remember: Scrum was not born to adapt to your current organization and its existing structure. It intends to force us to consider: What works? What needs improvement?
Scrum is just a starting point!