Agile methodology: Kanban VS Scrum

After a very comprehensive intro on Project Management methodologies where we explored Agile VS Waterfall, in today's post we are going to deep dive on some of the differences between Kanban and Scrum, two of the frameworks within the Agile framework.

While there are some clear differences between both practices, the principles are largely the same.

Scrum is a tool used to organise work into small, manageable pieces that can be completed by a cross-functional team within a prescribed time period called a “sprint” (generally 2-4 weeks long). To plan, organise, administer, and optimise this process, Scrum relies on at least three prescribed roles: 

-  The Product Owner, responsible for initial planning, prioritising, and communication with the rest of the company

- The Scrum Master, responsible for overseeing the process during each sprint.

- The Team Members, responsible to carry out the purpose of each sprint, such as producing software code.

Kanban is also a tool used to organise work for the sake of efficiency, and like Scrum, Kanban encourages work to be broken down into manageable chunks, however, where Scrum limits the amount of time allowed to accomplish a particular amount of work, by means of sprints, Kanban limits the amount of work allowed in any one condition as only so many tasks can be ongoing.

 In the table below you can find the main differences between Scrum and Kanban:

Finally the video below illustrates very clearly the differences and points out how the Scrum and Kanban boards work.

Until next time!

Project Management: Waterfall VS Agile

In today´s post we are going to focus on Project Management. More and more, we see in Supply Chain the need to step back from the operational day to day task and focus on a specific project with a clear starting and end date. However there are several methodologies that can be followed to ensure the best outcome for any given project. We will be focusing on the two most common: Waterfall and Agile.

The Waterfall method is the most traditional project management approach that uses sequential phases to define, build, test, and release project deliverables. Each phase is completed and approved before the team moves on to the next phase. The project can't move backwards to previous phases.

On the other hand, Agile is an umbrella term covering several newer project management approaches that use iterative work cycles, called sprints. Each sprint uses 'mini-phases' to define, build, test, and release the project deliverables.

The main difference between waterfall and agile methods is in the goals; the waterfall method wants to get everything right the first time, and agile methods want to get things released quickly.

Pros of the waterfall method

- Potential issues that would have been found during development can be researched and bottomed out during the design phase.
- The development process tends to be better documented since this methodology places greater emphasis on documentation.
- Because the waterfall process is a linear one it is perhaps easier to understand. Often teams feel more comfortable with this approach.

Cons of the waterfall method

- Often it´s not known exactly what it´s needed up front or what’s possible with the technology available.
- Changes to requirements can’t easily be incorporated with the waterfall method and there are often laborious change control procedures to go through when this happens
- The process doesn’t have its own momentum

Pros of Agile methods

- Much more quicker, and successive iterations can be delivered frequently, at a consistent pace.
- There is closer collaboration between project managers and the business.
- Changes to requirements can be incorporated at any point of the process.
- It gives the opportunity for continuous improvement for live systems.
- It is highly transparent.

Cons of Agile methods

- Agile methodologies are often more difficult to understand than linear, sequential ones.
- Because of the emphasis on working software there can be a perception that documentation can sometimes be neglected.
- When implemented badly Agile can introduce extra inefficiencies in large organizations or can be working against long standing organizational processes.

Project Management humor

So true!