Project Management Approaches

Us software development geeks use many different project management styles when crafting software; Scrum, Kanban, Waterfall and the hybrid Scrumban are some of the most common types, so we thought we’d break them down for you!

Mindera doesn’t have a favourite framework when partnering with our clients; every business has different goals and objectives. But, we are Agile, and we like our practices to reflect that from the start of the product roadmap right the way through each milestone until we have a completed product.

So let's start to introduce them!

Scrum Agile Framework

Scrum is an iterative and incremental agile framework. It is probably the most used framework in Mindera. It focuses on delivering value in short iterations called Sprints, which typically last for two to four weeks. The development team works in a self-organising manner, and we do love that!

The project backlog is prioritised and broken down into manageable units called user stories. User stories are used to capture a description of a feature from a user's perspective.

Scrum encourages frequent communication, collaboration, and adaptation throughout the development process.

We find that Scrum really works, but it does require experienced team members and a dedicated Scrum Master. Sometimes, the emphasis on self-organisation can lead to ambiguity in some places, but at Mindera, we encourage and adopt self-organisation.

Scrum may not be suitable for projects with fixed deadlines or well-defined requirements. Still, it is easy to follow and flexible in adapting to changing needs and delivering value in short iterations.

Scrum Analogy

Working with the Scrum framework is like embarking on a road trip with a group of your best friends. You start with a general idea of the destination and the major cities you'll pass through. However, the route can be adjusted based on real-time conditions, the weather and the group's preferences. During the trip, you hold regular discussions with your friends to decide the next leg of the journey, the places to explore, and any necessary adjustments. This collaborative and iterative approach allows for flexibility and adaptation to changing circumstances.

Kanban Model In Software Engineering

Kanban is another agile framework that we love in Mindera. It is a visual workflow management methodology focusing on continuous delivery and minimising work in progress (WIP). It originated in lean manufacturing but has since been applied successfully in software development.

In Kanban, work items are represented as cards or sticky notes on a Kanban board, and they move through different stages of the workflow, from "to-do" to "in progress" to "done." Kanban limits the number of work items in each stage, enabling teams to focus on completing tasks before starting new ones.

We love Kanban as it provides transparency and visibility into the workflow, and it is easy to start and adapt without significant process changes. But requires a well-defined workflow and clear policies and may not be suitable for projects with time-sensitive deliverables.

Kanban Analogy

Working with the Kanban framework is very similar to taking a spontaneous road adventure trip! You have a general idea of the starting and ending cities, but the specific route is not predetermined. Instead, you keep an eye on road signs and decide your direction based on current road conditions, traffic, budget and your preferences. You maintain a flexible approach, choosing the most efficient and enjoyable route as you go. The focus is on minimising congestion, maintaining a smooth flow, and making continuous progress towards your destination. Quite simple, right?

What is Scrumban?

If you like Scrum and Kanban, you will love Scrumban! Scrumban is a hybrid framework that combines practices from Scrum and Kanban. It is often used by teams transitioning from Scrum to Kanban or looking for a more flexible approach.

Scrumban incorporates:

• Kanban Board: Similar to Kanban, Scrumban utilises a visual board to represent the workflow stages and track the progress of work items.
• Sprints and Iterations: Scrumban retains the concept of sprints from Scrum but with more flexibility. The team may choose to have longer or variable-length sprints based on the nature of the project.
• Continuous Flow: While Scrumban allows for sprints, it encourages a more continuous flow of work by limiting work in progress and allowing tasks to move across the board as soon as the team is ready to start them.
• Regular Reflection: Scrumban emphasises frequent retrospectives to identify bottlenecks, improve the workflow, and refine processes.

Scrumban Analogy:

The Scrumban methodology can be likened to a road trip where you start with a rough plan, but you have an open mind to adjust your journey along the way. You have a general route in mind but don't adhere strictly to a predefined schedule. Instead, you embrace a mix of Scrum and Kanban principles. You regularly assess the progress, collaborate with your travel friends to make decisions, and make necessary modifications to the route based on real-time conditions and preferences.

Waterfall Model For Software Development

The Waterfall model can be pretty linear in how things progress. The process flows downward (like a waterfall!) through each development phase. A key benefit of the Waterfall model is its clear structure, making it easier to track progress and set those goals.

The Waterfall model has some setbacks (like any model!). As each phase must be completed before the next can start, it can be hard to make changes once things have progressed to the next stage.

Additionally, as the project is planned out in advance, adding new features or information can be challenging as things progress, making this model less suited to complex projects that can change rapidly.

Even though the model has its setbacks, it is still popular in software development projects; it's good to use if you know the product's specific features and have a solid understanding of the problem at hand! It is always wise to really assess which project management approach you go with when starting any new project!

Waterfall Analogy

The Waterfall methodology is quite like following a strict step-by-step plan. You start by gathering all the necessary information about the route, including the distance, road conditions, and points of interest, as well as having an idea of what the weather might be! Once you have a detailed plan, you drive from one city to the next, following the predetermined route without deviating (or at least try to!). Of course, this approach assumes that the conditions and requirements will remain relatively stable throughout the journey. And, as you can imagine, this might be hard in real life!

So, in Summary

• Scrum is an agile framework and is used in the software development process; in this method, small teams work closely together to deliver increments of a product spec. Teams follow a series of steps and events known as sprints. A massive benefit of Scrum is its flexibility and adaptability - teams can respond quickly to changes.
• Kanban is an approach based on the principles of ‘Lean.’ It helps teams visualise their work and optimise tasks and steps. In Kanban, teams use a Kanban board to track product development progress. But, like Scrum, this is flexible and adaptable.
• Scrumban, as a hybrid approach, combines elements of Scrum and Kanban. It allows for flexibility in terms of sprints and continuous flow. Scrumban suits teams transitioning from Scrum to Kanban or seeking a more adaptable methodology.
• Waterfall is usually linear, and projects are set out in a downward flow that highlights the phases of a product from beginning to end. Each stage must be completed before the next step can start. There isn’t much overlap between phases, and there’s a clear structure.
• The choice of framework depends on factors such as the project's nature, requirements, and the desired level of flexibility and adaptability. In Mindera, we know and try our best to work on the methodology that best suits a project and a team. And we are proud of it!

If you’re a Scrum, Kanban, or Waterfall (or all of them!) expert and you’re looking for a new challenge, check out our vacancies!