Agile frameworks and practices
In the last few decades, numerous approaches to product development and service delivery have emerged. With the complexity of products and services on the rise, it can be confusing to determine which framework or method to use. In this article, we will explore three main Agile frameworks and methods: Scrum, Extreme Programming (XP), Kanban, and how they complement each other.
Scrum is a lightweight framework that allows teams to deliver value incrementally. It consists of a cross-functional Scrum team, with three accountabilities, five events, and three artefacts. Scrum emphasises the importance of maximising customer value, improving team effectiveness, and increasing product quality through continuous improvement, including regular retrospectives. However, it is not an approach to estimate and plan work.
Extreme Programming (XP) is an Agile framework that has roots in software development. XP is focused on iteratively and incrementally developing software while prioritising user needs. It is similar to Scrum but with shorter iterations, a more open approach to changes during iterations, and prioritisation by the customer. XP also suggests development practices such as user stories, spikes, pair programming, test-driven development, refactoring, and continuous integration.
Kanban is a method that helps organisations manage their professional services and respond better to customer needs. It is not a methodology or framework, but a method applied to an existing way of working to make it more effective. Kanban takes inspiration from Lean manufacturing and allows work to flow by limiting work in progress and establishing a pull system. It visualises work and helps operate the business effectively, enabling continuous improvement in an evolutionary way. Many Scrum or XP teams use Kanban to improve their work processes.
In conclusion, each framework and method has its unique features and benefits. Scrum provides structure and focus, XP emphasises development practices, and Kanban enables good flow. The choice of framework or method depends on the specific needs and goals of the team. Even better so – try tweaking the frameworks for your needs and combining elements from multiple frameworks and methods to get the best results for your context!
