Multipart article

What's the Difference? Agile vs Scrum vs Waterfall vs Kanban

 

From Agile to Scrum to Waterfall to Kanban, there are a variety of different project management frameworks. Some, like Scrum, follow a more rigid, structured methodology. Others, like Kanban, are easier to introduce and implement on top of existing processes. They all have pros and cons, so how do you know which one to choose?

This article will cover the differences between Agile vs Scrum vs Waterfall vs Kanban. We'll talk about the advantages, disadvantages, stages, and when you should use each one.


Agile Methodology

What Is Agile?

Agile software development is based on an incremental, iterative approach. Instead of in-depth planning at the beginning of the project, Agile methodologies are open to changing requirements over time and encourages constant feedback from the end users. Cross-functional teams work on iterations of a product over a period of time, and this work is organized into a backlog that is prioritized based on business or customer value. The goal of each iteration is to produce a working product.

 

Agile refers to any process that aligns with the concepts of the Agile Manifesto. In February 2001, 17 software developers met in Utah to discuss lightweight development methods. They published the Manifesto for Agile Software Development, which covered how they found “better ways of developing software by doing it and helping others do it” and included four values and 12 principles. The Agile Manifesto is a dramatic contrast to the traditional Project Manager’s Body of Knowledge (PMBOK) guide and standards.

A better, more agile way to plan, track, and manage your projects with Smartsheet

Agile Project Management Dashboard

Smartsheet is a cloud-based platform that allows teams and organizations to plan, manage, and report on projects, helping you iterate more effectively and achieve more. See Smartsheet in action.

 

Watch a demo


12 Principles of Agile Methodology

The Agile Manifesto lists 12 principles to guide teams on how to execute with agility. These are the principles:

  1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
  2. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
  3. Deliver working software frequently, from a couple of weeks to a couple of months, with preference to the shorter timescale.
  4. Business people and developers must work together daily throughout the project.
  5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
  6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
  7. Working software is the primary measure of progress.
  8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
  9. Continuous attention to technical excellence and good design enhances agility.
  10. Simplicity -- the art of maximizing the amount of work not done -- is essential.
  11. The best architectures, requirements, and designs emerge from self-organizing teams.
  12.  

Advantages of Agile

 

Here are some of the top advantages of Agile:


  •  

  •  

  •  

  •  

  •  
  • Continuous improvement: Agile projects encourage feedback from users and team members throughout the whole project, so lessons learned are used to improve future iterations.

Tips and best practices for your next project using the Agile methodology.

Agile PM Ebook

 

Learn all there is to know about Agile project management and tips to help you start implementing Agile PM best practices.

 

Get the free e-book to implement my Agile best practices


Disadvantages of Agile

 

Here are some of the disadvantages of Agile:


  •  
  •  
     

  •  

  •  
  •  

The Agile Development Cycle

Agile development cycle


 

  •  
     

  •  

  •  

  •  

  •  
  • Deployment: After testing, the product is delivered to customers for them to use. However, deployment isn’t the end of the project. Once customers start using the product, they may run into new problems that the project team will need to address.

Methodologies That Are Used to Implement Agile

Agile is a framework and there are a number of specific methods within the Agile movement. You can think of these as different flavors of Agile: 


  •  

  •  

  •  
  •  
     

  •  

  •  

  •  
  • Scrum: Scrum is one of the most popular ways to implement Agile. It is an iterative software model that follows a set of roles, responsibilities, and meetings that never change. Sprints, usually lasting one to two weeks, allow the team to deliver software on a regular basis.

Other Practices in Agile

There are many other practices and frameworks that are related to Agile. They include:

  •  
     

  •  

  •  
  •  
     
  •  
     

  •  
  •  

How to Estimate Budgets in Agile

 

 

 

 

And lastly, you could use planning poker to estimate the effort required for development goals. Planning poker is a consensus-based, gamified technique for estimating the effort of development goals. Each team member makes estimates by playing numbered cards face-down on the table, instead of saying it out loud. The cards are then revealed and the estimates discussed with the whole team.


Agile and Pair Programming

Pair programming (also known as “pairing”) is part of the Extreme Programming (XP) practices. It is when two programmers share a single workstation, which includes sharing one screen, keyboard, and mouse. The purpose of this technique is to encourage better communication, clarification of the problem, and understanding of the solution. Pairing is often used in Agile projects to quickly deliver high-quality products, but is it always required? 

The answer depends on your programmers, company, and goals. For some projects and programmers, pairing might improve productivity. However, it may not always be appropriate for every project. The best thing to do is experiment and see if it works for you.


How Agile Addresses Software Requirements

Agile helps development teams focus on customers’ most important requirements as quickly as possible. With continuous feedback and frequent face-to-face interactions, the project team and stakeholders understand and prioritize the right requirements.

Agile teams use backlogs with user stories to manage requirements. Before an iteration begins, the team agrees on which requirements they should meet with the next delivery. This collaborative approach ensures that the most important features get prioritized. And, requirements are continuously updated throughout the project as new information is surfaced.


Can You Use Agile for Projects Outside of Software?

 

 

 

 


How to Get Started with Agile

A simple way to get started with Agile is to incorporate daily stand-up meetings into your project. Daily stand-up meetings are easy to incorporate into any other project methodology you may already be using (even Waterfall) and don’t require any training or knowledge transfer. Meet at the same spot every day for about ten minutes and have everyone talk about what they worked on the day before, what they’ll work on today, and any roadblocks.

 

Whichever route you choose, remember that Agile is flexible in its very nature. There is no wrong or right way to get started with Agile. Do what works for you and your team.

 

Experimente o Smartsheet gratuitamente

 


Scrum Methodology

What Is Scrum?

 

Scrum follows a set of roles, responsibilities, and meetings that never change. For example, Scrum calls for four ceremonies that provide structure to each sprint: sprint planning, daily stand-up, sprint demo, and sprint retrospective. During each sprint, the team will use visual artifacts like task boards or burndown charts to show progress and receive incremental feedback.

Jeff Sutherland created the Scrum process in 1993, taking the term “Scrum” from an analogy in a 1986 study by Takeuchi and Nonaka published in the Harvard Business Review. In the study, Takeuchi and Nonaka compare high-performing, cross-functional teams to the Scrum formation used by Rugby teams. The original context for this was manufacturing, but Sutherland, along with John Scumniotales and Jeff McKenna, adapted the model for software development.


Advantages of Scrum

Scrum is a highly prescriptive framework with specific roles and ceremonies. While it can be a lot to learn, these rules have a lot of advantages. The benefits of Scrum include:


  •  
  •  
     

  •  
  • Increased cost savings: Constant communication ensures the team is aware of all issues and changes as soon as they arise, helping to lower expenses and increase quality. By coding and testing features in smaller chunks, there is continuous feedback and mistakes can be corrected early on, before they get too expensive to fix.

Disadvantages of Scrum

 

Here are the disadvantages of Scrum: 

  •  
     

  •  

  •  
  • Poorly defined tasks can lead to inaccuracies: Project costs and timelines won’t be accurate if tasks are not well defined. If the initial goals are unclear, planning becomes difficult and sprints can take more time than originally estimated.

Roles in Scrum

Roles in scrum

There are three specific roles in Scrum. They are:

  •  
     
  •  
     
  •  

Steps in the Scrum Process

Scrum cycle



  •  

  •  

  •  

  •  
  •  
     
  • Sprint retrospective meeting: Also at the end of each sprint, the team reflects on how well Scrum is working for them and talks about any changes that need to be made in the next sprint. The team may talk about what went well during the sprint, what went wrong, and what they could do differently.

Tools, Artifacts, and Methods in Scrum

Burndown chart


  •  
     

  •  
  •  
     

  •  

  •  
  •  
     
  •  
     
  • Lean vs Scrum: Scrum is a software development framework, while Lean helps optimize that process. Scrum’s primary goal is on the people, while Lean focuses on the process. They are both considered Agile techniques, however Lean introduces two major concepts: eliminating waste and improving flow.

How to Get Started with Scrum

Working with Scrum often means changing the team’s habits. They need to take more responsibility, increase the quality of the code, and boost speed of delivery. This level of commitment acts as a change agent; as the teams commit to sprint goals, they are more and more motivated to get better and faster to deliver a quality product.

 

Depending on how familiar your team is with Scrum, you may also want to look into training sessions. Certified Scrum Coaches and Trainers and Scrum Alliance Registered Education Providers can help your team learn and embrace Scrum.

 

See how easy it can be to use Smartsheet Card View during your next Scrum meeting.

Experimente o Smartsheet gratuitamente


Waterfall Methodology

What Is Waterfall?

Waterfall methodology follows a sequential, linear process and is the most popular version of the systems development life cycle (SDLC) for software engineering and IT projects. It is sometimes planned using a Gantt chart, a type of bar chart that shows the start and end dates for each task. Once one of the eight stages are complete, the development team moves onto the next step. The team can’t go back to a previous stage without starting the whole process from the beginning. And, before the team can move to the next stage, requirements may need to be reviewed and approved by the customer.

 


Advantages of Waterfall

 

The advantages of Waterfall include:


  •  

  •  
  •  

Disadvantages of Waterfall

 

Here’s more information on the disadvantages of Waterfall:

  •  
     

  •  
  • Gathering accurate requirements can be challenging: One of the first phases in a Waterfall project is to talk to customers and stakeholders and identify their requirements. However, it can be difficult to pinpoint exactly what they want this early in the project. Often times, customers don’t know what they want early on and instead, learn and identify requirements as the project progresses.

Stages of Waterfall

Waterfall


  1.  
  2. Initiation: Once the idea is formed, you need to hire the project team, and define objectives, scope, purpose, and deliverables.
  3.  
  4. Design: The design specifications created in this phase are used in the coding phase to actually write the code. The requirements are studied and evaluated, and the design of the system is prepared. The team’s goal is to understand what actions need to be taken and what they should look like.
  5. Implementation/Coding: The actual coding of the software begins. Any flowcharts or algorithms created in the design phase are translated into a programming language.
  6. Testing: Once the code is complete, the software needs to be tested for any errors. When the testing is finished, the software is delivered to the customer. Some teams may choose to include user acceptance testing (UAT), where users test the software before it is deployed to the general public.
  7. Maintenance: Once customers have been using the software in the real world, they may find additional problems. The development team will need to resolve, change, or modify the software to continue to be effective.

Iterative Waterfall Development

 

 


How Waterfall Deals with Software Requirements

Waterfall projects define all software requirements upfront. The project cannot proceed unless these requirements have been identified and documented.

Some Waterfall projects may have a dedicated team to capture, collect, and gather these requirements. They may use questionnaires, face-to-face or phone interviews, white boards, and modeling tools to capture stakeholder and customer requirements.

 


Kanban

What Is Kanban?

Kanban is Japanese for “visual sign” or “card.” It is a visual framework used to implement Agile that shows what to produce, when to produce it, and how much to produce. It encourages small, incremental changes to your current system and does not require a certain set up or procedure (meaning, you could overlay Kanban on top of other existing workflows).

Kanban was inspired by the Toyota Production System and Lean Manufacturing. In the 1940s, Toyota improved its engineering process by modeling it after how supermarkets stock shelves. Engineer Taiichi Ohno noticed that supermarkets stock just enough product to meet demand, optimizing the flow between the supermarket and customer. Inventory would only be restocked when there was empty space on the shelf (a visual cue).  And because inventory matched consumption, the supermarket improved efficiency in inventory management.

Toyota brought these same principles to its factory floors. Different teams would create a card (or Kanban) to communicate that they had extra capacity and were ready to pull more materials. Because all requests for parts were pulled from the order, Kanban is sometimes called the “pull system.” 

These same ideas apply to software teams and IT projects today. In this context, development work-in-progress (WIP) takes the place of inventory, and new work can only be added when there is an “empty space” on the team’s visual Kanban board. Kanban matches the amount of WIP to the team’s capacity, improving flexibility, transparency, and output.

According to the Kanban blog, “Kanban is a technique for managing a software development process in a highly efficient way. Kanban underpins Toyota's ‘just-in-time’ (JIT) product system. Although producing software is a creative activity and therefore different to mass-producing cars, the underlying mechanism for managing the production line can still be applied.”

When looking at Kanban vs Agile, it’s important to remember that Kanban is one flavor of Agile. It’s one of many frameworks used to implement Agile software development.


About the Kanban Board

Kanban board

A Kanban board is a tool to implement the Kanban method for projects. Traditionally, this tool has been a physical board, with magnets, plastic chips, or sticky notes on a whiteboard to represent work items. However, in recent years, more and more project management software tools have created online Kanban boards.

A Kanban board, whether it is physical or online, is made up of different swim lanes or columns. The simplest boards have three columns: to do, in progress, and done. The columns for a software development project may consist of backlog, ready, coding, testing, approval, and done columns.

Kanban cards (like sticky notes) represent the work and each card is placed on the board in the lane that represents the status of that work. These cards communicate status at a glance. You could also use different color cards to represent different details. For example, green cards could represent a feature and orange cards could represent a task.


Advantages of Kanban

 

The advantages of Kanban include:

  •  
     
  •  
     

  •  

  •  
  • Minimizes cycle time: Cycle time is the amount of time it takes for work to move through the team’s workflow. In Kanban projects, the entire team helps to ensure the work is moving quickly and successfully through the process.

Disadvantages of Kanban

 

Here’s more on the disadvantages of Kanban:


  •  

  •  
  • Lack of timing: A frequent complaint about Kanban is that you don’t know when things will be done. The columns on the Kanban board are only marked by phase (to do, in progress, complete), there are no timeframes associated with each phase, so you really don’t know how long the to do phase could last.

Core Practices and Principles of Kanban

Every Kanban project should follow these core principles:


  •  

  •  

  •  

  •  
  • Continuously improve: The Kanban method encourages small, continuous changes that stick. Once the Kanban system is in place, the team will be able to identify and understand issues and suggest improvements. Teams measure their effectiveness by tracking flow, measuring cycle time, and increasing quality of work.

Common Questions About Kanban

 

 

 

You could also try a kaizen meeting, where you only invite people who are involved in the task at hand. Each person discusses problems and challenges, and how his or her job could be done more efficiently. Then, the whole group talks about solutions to those issues.

Kaizen also can include a kaizen facilitator, who encourages the team to openly discuss critical issues.


To some extent, Kanban trades predictability for efficiency. There are no timebox constraints or planning, however once a team has optimized the flow of work and can get a sense of how long certain tasks take, there will be some level of predictability.

If management still needs more defined predictability (which is not the Kanban approach), you may need to try managing expectations. In a traditional model, you have a predictable date of delivery, but in reality, no one is going to deliver a product by that date if it’s not complete. Management is always going to wait for the product to be complete, regardless of the original date set. In the Kanban model, the expectations need to be adjusted to focus on delivering the product when it’s ready and complete.


There are a couple different ways you can handle deadlines in a Kanban model. You can simply write the deadlines on the Kanban cards, making sure these deadlines act more as guidelines rather than hard-and-fast due dates (in Kanban, you shouldn’t sacrifice quality for timing).

 


 


Sim.


There is no formula for setting the right WIP limits. It’s very common for limits to be wrong in the beginning, but you just need to adjust them as the project progresses. A good place to start is 1.5 for available resource, but you should constantly be reevaluating this number and making changes as necessary.


Agile vs Scrum

Differences and Similarities Between Agile and Scrum

Scrum vs agile


 

 

How Does Scrum Fit with Agile?

 


When to Use Scrum

We recommend using Scrum if: 

  • The project requirements will change and evolve 
  • Continuous feedback is required
  • You have to figure out how to do a large part of the work because you haven't done it before
  • You don’t need to commit to a fixed release date
  • The project team wants autonomy
  • You need to deliver software on a regular basis



When to Use Agile

The line between when to use Agile versus when to use Scrum is blurry. Scrum is one framework in the Agile process, so they both have a lot in common. A good place to start is to first understand if you should use Agile in general. Then, if an Agile methodology seems like it would work for you, you could choose which framework of Agile to use (Scrum being one framework).

We recommend using Agile if: 

  • The final product isn’t clearly defined
  • The clients/stakeholders need to be able to change the scope
  • Changes need to be implemented during the entire process
  • The developers are adaptable and can think independently
  • You need to optimize for rapid deployment

Hybrid Approach

If a pure Scrum approach doesn’t work for your project, you can also try a hybrid model. There are several methodologies that combine the principles of Agile or Scrum and adapt the framework to scale more effectively.

For example, Disciplined Agile Delivery (DAD) builds on the practices of Agile, Scrum, and Lean to provide a solid foundation from which to scale. DAD was developed to provide a more cohesive approach to Agile, taking strategies from Scrum, Kanban, Extreme Programming, and others. Rather than taking the time to learn one of these existing frameworks and cobble them together as needed, DAD already combines all relevant techniques.

 


Kanban vs Scrum

Differences and Similarities: Scrum vs Kanban

Scrum vs kanban


  • Scrum requires specific roles whereas Kanban has no required roles.
  • Scrum is based on timeboxed iterations, combining planning, process improvement, and release. In Kanban, you can choose to do these activities on a regular cadence or whenever you need.
  • Scrum limits work in progress (WIP) in each iteration, whereas Kanban limits WIP in each workflow.
  • Scrum resists change, whereas Kanban easily accommodates and embraces change. In Scrum, once the team has committed stories to a sprint, you can’t add additional stories later on. In Kanban, you can add or change stories as you please, assuming that it’s within WIP limits.
  • A Scrum board is reset after each sprint. A Kanban board is continuously used.
  • A Scrum team is cross-functional and one team owns the Scrum board. In Kanban, teams don’t need to be cross-functional and anyone can own the Kanban board.
  • Scrum teams require estimation, whereas Kanban doesn’t.


  • They are empirical. You have to experiment with the process to see what works for you.
  • Both allow team members to work on multiple products at once.
  • They are Lean and Agile.
  • They both limit WIP (although the way they each limit WIP is different)
  • They use pull scheduling
  • They focus on delivering software early and often
  • Both use transparency to improve process

How Do Kanban and Scrum Relate to Each Other?

 

While both Kanban and Scrum are very adaptive, Scrum is more rigid than Kanban. Scrum has more constraints, whereas Kanban is more flexible.


Scrum Board vs Kanban Board

 

To create a Scrum board, the Scrum team must first create sprints, assign points to user stories, and plan which stories go into which sprint. Then, the Scrum board visualizes the sprint, showing which stories are in plan mode or work mode. The Scrum board is reset between each sprint and is owned by one specific team.

A Kanban board has the same column-based layout as a Scrum board, but it requires no upfront planning. You can start working and moving through the flow of the Kanban board without having a structured plan. The Kanban board can be shared by multiple people and is persistent; you don’t need to reset the board. And, unlike the Scrum board, the Kanban board has a maximum number of stories allowed in each column at one time. This will continue to flow as long as the project continues, with new stories added and completed stories being reevaluated if needed.


When to Use Kanban

We recommend using Kanban if:

  • You need to add stories or change sprints on the fly
  • You don’t need iterations
  • Estimation isn’t necessary
  • You want the ability to release at any time
  • Continuous improvement is already emphasized
  • Your team doesn’t respond well to big changes
  • You want to improve delivery flow
  • The system needs to be easy to understand


 


What Is Scrumban?

Scrumban combines the principles of Scrum and Kanban into a pull-based system. The team plans out the work that was established during initiation and continually grooms the backlog. The same Scrum meetings should take place, but the frequency can change depending on context and need. The most important part of Scrumban is making sure that work in progress limits (WIP limits) are followed.

 

Scrumban can look more like Scrum on the technical level, but at the cultural level, it will more closely resemble Kanban. Instead of big changes all at once, Scrumban encourages incremental changes. If your team is looking to migrate from Scrum to Kanban, Scrumban can provide a gentle transition.


Which One Is Best? Kanban vs Scrum

When comparing Kanban versus Scrum, there is no definitive winner. The best framework depends on your project, team, and your goals. Because both Kanban and Scrum are flexible Agile methodologies, you could easily take principles from each and apply them as you see necessary.

 

As a general rule of thumb, if your team or organization is really stuck and needs a big change, Scrum may be more appropriate. If you already have a process in place that you’re happy with, but want to implement some small changes, Kanban might be a better choice.


Agile vs Waterfall

Differences and Similarities: Waterfall vs Agile

Waterfall vs agile


  • Waterfall is a structured process, where you can’t start on a new phase until the previous one has been completed. On the other hand, Agile is a flexible process, allowing you to move through the project as you like.
  • Waterfall is sequential and Agile does not enforce a linear process.
  • Waterfall projects usually include defined requirements in advance, whereas requirements are expected to change and evolve in Agile projects.
  • In Waterfall projects, you can’t change things that were done in previous stages, whereas Agile is very accommodating to changes.



When You Should Use Waterfall and When to Use Agile

We recommend using Waterfall if: 

  • You don’t expect changes in scope and you’re working with fixed-price contracts
  • The project is very simple or you’ve done it many times before
  • Requirements are very well known and fixed
  • Customers know exactly what they want in advance
  • You’re working with orderly and predictable projects


  • The final product isn’t clearly defined
  • The clients/stakeholders need the ability to modify the scope
  • You anticipate any kind of changes during the project
  • Rapid deployment is the goal



Which One Is Better? Agile vs Waterfall

Agile and Waterfall are such opposites that it’s hard to say which one is better. It really depends on the project, the level of clarity around requirements, and how flexible you can be.

If you have a clear picture of what the final product should be, you have fixed requirements that won’t change, and you’re working on a relatively simple project, some argue that Waterfall is a better choice than Agile. If you don’t expect to deal with change, Waterfall is a straightforward, efficient process. The issues with Waterfall come when you have to accommodate changes.

If you don’t have a clear picture of the final product, you anticipate changes, and you’re working on a complex project, Agile is superior. Agile is designed to accommodate new, evolving requirements any time during the project, whereas Waterfall does not allow you to go back to a completed phase and make changes.


Hybrid: Agifall or WAgile

If you’re still wondering about Waterfall versus Agile, you could always combine principles of both and use a hybrid model.

Agifall, for example, increases speed and quality by adding Agile methodologies to the Waterfall process. In an Agifall project, you would break out the research, strategy, and planning phases into tasks and proceed with sprints to complete them. The development phase would be just like any other Agile project, with more information up front. You also don’t need to wait for one phase to end to start the following phase, which is traditional in pure Waterfall. With Agifall, when the project can begin, it should begin.

Wagile has a more negative connotation than Agifall. The definition of Wagile on Wikipedia is, “a group of software development methodologies that result from slipping from Agile back into Waterfall, doing a lot of short Waterfalls and thinking it is Agile, Waterfall model masquerading as Agile software development.”

Wagile adopts Agile practices like short iterations, daily stand-ups, or continuous integration on top of the Waterfall model, without really changing the traditional Waterfall model.


Kanban vs Agile

Differences and Similarities: Agile vs Kanban

Kanban vs agile


  • Kanban advocates for continuous flow, while Agile works in iterations.
  • Kanban can work equally well for any type of work, whereas Agile may be better suited for some projects rather than others.
  • Anyone can pick up Kanban, but some Agile methodologies require knowledge or training.
  • Kanban requires a visual representation of workflow, while Agile does not.
  • Some Agile projects require cross-functional teams, whereas Kanban does not.
  • Agile is a philosophy whereas Kanban is a method.


  • They both break down projects into smaller chunks.
  • They emphasize continuous improvement.
  • They place high value on transparency.
  • Neither of them require a lot of upfront planning.
  • They work toward faster delivery.

When You Should Use Kanban and When to Use Agile

We recommend using Kanban if:

  • Your project doesn’t require iterations
  • You want the ability to release at any time
  • Your team prefers incremental change
  • Your team works well with visuals
  • You want to improve delivery flow
  • You’re looking for an easy-to-understand system


  • The final product isn’t clearly defined
  • Changes need to be implemented during the entire process
  • The developers are adaptable and can think independently
  • You’re looking to make a substantial change

Which One Is Better? Agile vs Kanban

Like with any project management methodology, there isn’t one framework that is better 100% of the time. You may choose Kanban for some projects, but want to implement Agile for others.

 

 


Resources and Related Posts

Download a free Excel waterfall chart template or learn how to create a waterfall chart from scratch. We'll also share when to use a waterfall chart and the features of a waterfall chart in Excel.

Find eight Agile project management templates in Excel, ranging from Agile product backlog template to Agile project charter template. You'll also learn how to use Agile templates in Smartsheet

Courses:

  • PMI Agile Certified Practitioner (PMI ACP): Offered by the Project Management Institute (PMI), this certification covers the many different approaches to Agile, like Scrum, Kanban, Lean, Extreme Programming (XP), and Test-Driven Development (TDD). Prerequisites include 2,000 hours of general project experience working on a team, 1,500 hours working on Agile project teams, and 21 contact hours of training in Agile practices.
  • Certified ScrumMaster (CSM): This certification from Scrum Alliance helps teams properly use Scrum, understand the values, and protect the team from distractions. As a CSM, you will be able to fill the role of Scrum Master or Scrum team member. To earn your CSM certificate, you must take a CSM course from a Scrum Alliance Authorized Trainer and demonstrate progress with an online test.
  • Certified Scrum Product Owner (CSPO): A Certified Scrum Product Owner learns Scrum terminology, practices, and principles to fulfill the role of Product Owner on a Scrum team. He or she is closest to the business side of the project, maintains the product backlog, and ensures everyone knows the priorities. To earn this certification from the Scrum Alliance, you must attend an in-person, two-day CSPO course taught by a Certified Scrum Trainer.
  •  
  • Certified Scrum Professional (CSP): Certified Scrum Professionals challenge their Scrum teams to improve the way Scrum is implemented for every project. To apply for a CSP, you must currently hold a CSM, CSPO, or CSD credential, have a minimum of 36 months of Agile/Scrum experience, and gather and submit 70 Scrum Education Units from the past three years.
  • Accredited Kanban Practitioner (AKP): Accredited Kanban Practitioners are professionals who have proven knowledge and expertise in Kanban implementation for software development. The certification is offered by the Agile Certification Institute, Inc. and requires that you have prior training in Agile practices and that you pass an AKP certification exam.

Manage Any Project Your Way with Smartsheet

 

Its pre-built project management templates make it even easier to track project requirements, store documents, create timelines, and organize key details. You can make real-time updates and alert your team about the new changes, and share your plan with internal and external stakeholders to increase transparency and keep everyone on the same page.

Plus, with our newest view, Card View, teams have a more visual way to work, communicate, and collaborate in Smartsheet. Card View enables you to focus attention with rich cards, give perspective with flexible views, and prioritize and adjust work more visually.

Altere as raias intuitivametne e filtre os cartões para ver o fluxo de trabalho a partir de várias perspectivas.  

 

If you found this post helpful, visit our Resources page for more agile project management tips and best practices.


Resources and Related Posts

How to Create a Waterfall Chart in Excel

Download a free Excel waterfall chart template or learn how to create a waterfall chart from scratch. We'll also share when to use a waterfall chart and the features of a waterfall chart in Excel.

Best Agile Project Management Excel Templates

Find eight Agile project management templates in Excel, ranging from Agile product backlog template to Agile project charter template. You'll also learn how to use Agile templates in Smartsheet

Agile Planning: Best Practices for Project Managers

Agile One-Stop Project Management Resource

Courses:

  • PMI Agile Certified Practitioner (PMI ACP): Offered by the Project Management Institute (PMI), this certification covers the many different approaches to Agile, like Scrum, Kanban, Lean, Extreme Programming (XP), and Test-Driven Development (TDD). Prerequisites include 2,000 hours of general project experience working on a team, 1,500 hours working on Agile project teams, and 21 contact hours of training in Agile practices.
  • Certified ScrumMaster (CSM): This certification from Scrum Alliance helps teams properly use Scrum, understand the values, and protect the team from distractions. As a CSM, you will be able to fill the role of Scrum Master or Scrum team member. To earn your CSM certificate, you must take a CSM course from a Scrum Alliance Authorized Trainer and demonstrate progress with an online test.
  • Certified Scrum Product Owner (CSPO): A Certified Scrum Product Owner learns Scrum terminology, practices, and principles to fulfill the role of Product Owner on a Scrum team. He or she is closest to the business side of the project, maintains the product backlog, and ensures everyone knows the priorities. To earn this certification from the Scrum Alliance, you must attend an in-person, two-day CSPO course taught by a Certified Scrum Trainer.
  • Certified Scrum Developer (CSD): Certified Scrum Developers learn specialized Agile engineering skills and demonstrate their knowledge through formal training and a technical skills assessment. The CSD course is geared toward software developers who are working in a Scrum environment. To earn a CSD from the Scrum Alliance, you must have five days of formal training taught by a Scrum Alliance Registered Education Provider and a Scrum Alliance Authorized Instructor. 
  • Certified Scrum Professional (CSP): Certified Scrum Professionals challenge their Scrum teams to improve the way Scrum is implemented for every project. To apply for a CSP, you must currently hold a CSM, CSPO, or CSD credential, have a minimum of 36 months of Agile/Scrum experience, and gather and submit 70 Scrum Education Units from the past three years.
  • Accredited Kanban Practitioner (AKP): Accredited Kanban Practitioners are professionals who have proven knowledge and expertise in Kanban implementation for software development. The certification is offered by the Agile Certification Institute, Inc. and requires that you have prior training in Agile practices and that you pass an AKP certification exam.

Manage Any Project Your Way with Smartsheet

Smartsheet is a work management tool with powerful collaboration and communication features. By providing a broad range of smart views – Grid, Calendar, Gantt, Dashboards – Smartsheet helps you manage projects the way you want to. 

Its pre-built project management templates make it even easier to track project requirements, store documents, create timelines, and organize key details. You can make real-time updates and alert your team about the new changes, and share your plan with internal and external stakeholders to increase transparency and keep everyone on the same page.

Plus, with our newest view, Card View, teams have a more visual way to work, communicate, and collaborate in Smartsheet. Card View enables you to focus attention with rich cards, give perspective with flexible views, and prioritize and adjust work more visually.

Display information on cards including custom fields, images, and color coding to better focus your team’s attention. Categorize cards into lanes to organize your work more visually. Intuitively change lanes and filter cards to see the flow of work from multiple perspectives. Act on tasks and change status of work by dragging and dropping cards through lanes to immediately share decisions with the entire team. Start with a pre-built Card View template or import existing projects directly from Trello. 

Manage Your Agile Project in Smartsheet

Want more project management tips and best practices? Don't miss our Project Management Resource Hub for the latest articles, templates, videos, and more.


*The PMBOK Guide is a registered mark of the Project Management Institute, Inc.