Agile vs. Waterfall vs. Kanban vs. Scrum IXD301/302

While these methodologies have major differences, each project management methodology has the same goal: to further the completion and success of projects. Therefore, each methodology helps manage a team’s working processes with structure and communication. Where they differ is the implementation. For the purposes of my IXD 301 work I will be using the Agile methodology due to it’s iterative nature and ability to move backwards and forwards throughout the project

What is Waterfall?

In Waterfall project management, projects are broken down into linear and sequential stages and laid out on what’s referred to as a Gannt chart. Every piece of the project relies on the completion of the previous stages before the project can progress, and waterfall has two unique stages, the discrete stage, and the terminal stage. It can be used in software development and television production, also for short projects

 

When running the waterfall methodology any change during the project requires restarting the entire process. The Agile methodology allows for alterations throughout the process this is a major difference between Agile and Waterfall.

 

As Waterfall does not allow going back to a prior phase, project requirements need to be clear and well defined from the beginning. This methodology begins with gathering and documenting requirements and then making these requirements accessible to team members.

 

Team members also document their work as the project continues through each phase. Ideally, team members can exit or enter a project without disrupting workflow, making Waterfall a good solution for teams expecting changes in bandwidth.

What is Agile?

The Agile methodology is used in software of web development settings (anything that requires iterations or testing on the final product) it is a collaborative, self-organizing, cross-functional approach to completing a project.

 

Whilst Agile is referred to as a distinct methodology,  An Agile project is an umbrella term that includes Scrum and Kanban. Still, there are differences between an Agile and Waterfall project management system. 

 

Each Agile methodology will have the following characteristics.

Simultaneous, incremental work

This trait is the most discernible when comparing Waterfall and. Agile methodology. Agile methods divide projects into small iteration periods, which work extremely well for products that require user testing and revision (like branding).

Adaptability

Due to the fact that Agile methods work incrementally, teams can adapt their process frequently. However, Waterfall uses a set, rigid process, whereas Agile methodologies encourage teams to refine and adjust workflow as required.

 

The adaptability of Agile is well suited to projects in which constraints can change. Whilst such change should be avoided where possible, Agile methodologies cater to a project that changes by nature and allows teams to adapt their process to compensate for such changes.

 

Agile vs Waterfall

As discussed above waterfall is a rigid methodology and is used where iterations of the project are rare(Film, Television)

Whereas Agile would be used more prominently within the design industry (graphic design, web design, software dev)

 

What is Kanban? 

Kanban methodology is accurately specified as a type of Agile methodology. Kanban exists to try to better coordinate and find balance between capacity and bandwidth among team members. It uses the same Agile principles discussed but implements them in a unique way.

Kanban board

Kanban’s board visualizes the workflow of the team. The board is split into categories of the work to be completed, the work in progress, and the work which has been completed, and teams can include more categories as necessary to help visualize their workflow. 

Each task is written on a Kanban card, which moves from column to column on the board as it moves through the team’s process.

The board helps teams identify where processes require improvement. It makes problems such as bottlenecks stand out, helping the team to make corrections where needed. With this in mind the process is highly adaptable allowing the team to maneuver through a project more easily than holding all the stages in their heads leaving room for obvious human error as the project moves forward.

WIP limits

The Kanban methodology requires the team to set strict limits on the quantity of Work In Progress (WIP) at any one time. Teams assign the limit to the number of tasks in any column. When the limit is reached, no new work can begin column until a task is completed and moved to the next column. Again, helping teams identify bottlenecks, and encouraging individual team members to work together to fix them.  

 

Continuous improvement

The goal of the Kanban method is improvement of the team’s process. The team meets frequently enough to discuss any changes that are to be made, the data displayed on the Kanban board creates parameters for these discussions.

When held regularly meetings help the team to course correct and adjust the process where required. 

 

What is Scrum?

The final methodology I’ll cover is Scrum. It is also an Agile methodology that uses incremental steps in order to complete projects more quickly, speed is the aim. It began in the software industry and is also used in universities, the military and the automotive industry. Scrum methodology is great for tackling complex knowledge work, like software development also. Kanban vs. Scrum, Kanban is primarily used with process improvements in mind, whilst Scrum is concerned with getting more work done at speed through the use of something called sprints.

Sprints

Scrum uses two-week sprints to get work done. The sprints are planned in advance, performed, and then reviewed at the end of the two-week sprint period. During planning, the team will create a sprint backlog. The team completes the backlog tasks during the sprint, managing the workload among the team.

The team holds a 15-minute Scrum meeting for each day the sprint continues. During this time, contributors discuss any possible roadblocks interfering with the project’s success. A review of the previous day’s work and plans for the following day’s tasks are also discussed. The meeting ensures the team works together and are in sync.

Scrum Master

A Scrum master is the bridge between the team and the product owner. Before beginning a project, the Scrum master works with the client to define requirements. They then facilitate the creation of sprints with the team. Once a sprint begins, the Scrum master helps remove any roadblocks that become visible.

It’s important to point out that a Scrum master is not a typical project manager,A scrum master facilitates rather than managing it. The Scrum methodology encourages teams to manage their own productivity and efficiency; the Scrum master merely helps them do so, like the coach of a sports team rather than the manager.

 

Waterfall software.

Smartsheet is a project management and collaboration software available online. It has a familiar interface similar to a spreadsheet that provides multiple grid-like views, calendar, and Gantt. Project plans and schedules can be created quickly, increase the visibility of tasks, monitor progress, and track budgets. It also has waterfall project management templates.

 

Agile and Scrum software

Jira allows the management of a project’s iterations all in one place, visualizes the project with simple color-coded layout, and also stays on top of whatever sprints are taking place. The software is online allowing every team member to live update and communicate easily.

Kanban Software

Trello is a well known piece of online software used for production of Kanban Boards allowing the visualizing of projects in a colour-coded way. This software also updates live and can also be used for waterfall projects but by definition on the Trello site itself, its is primarily used for Kanban boards.

 

 

Leave a Reply

Your email address will not be published. Required fields are marked *