# data[].attributes.body
Kanban is all about visualizing your work, limiting work in progress, and maximizing efficiency. Kanban teams focus on reducing the time it takes to take a project from start to finish. They do this by using a Kanban board and continuously improving their flow of work.
Scrum teams commit to ship working software through set intervals called sprints. Their goal is to create learning loops to quickly gather and integrate customer feedback. Scrum teams adopt specific roles, create special artifacts, and hold regular ceremonies to keep things moving forward.

# data[].attributes.body
1) There are no deadlines for delivering products. This leads to long discussions between the Product Owner/Scrum Master and the Project Manager as PMs keep demanding new functionality.

2) The chances of project failure are high if individuals are not very committed or cooperative.

3) Adopting the Scrum framework in large teams is challenging.

4) The framework can be successful with experienced team members.

5)  Quality is hard to implement until the team goes through an aggressive testing process.

# data[].attributes.body
1. Outdated Kanban board can lead to issues in the development, can make the board overcomplicated, and lack of timing is another disadvantage because there is no timeframes associated with each phase.

2. Kanban methodology is a less structured methodology than Scrum.

3. If any work done is unsatisfactory for the customer or the company, it would require a rework that could worsen the situation as it will require more time and resources to get completed.  The implementation of the system may result in poor quality outputs. Kanban acts like a monitoring structure that makes the flow of tasks smoother.

4. Kanban will become very difficult to apply if too much activities or tasks are interrelated in a system.

# data[].attributes.body
Scrum framework is highly perspective and has specific roles and ceremonies. With Scrum, some of the advantages include :-
1. more transparency and visibility than any other methodology
2. increase in team accountability
3. accommodates change
4. is a cost saving development methodology
5. never changes the schedule and can estimates are much easier

# data[].attributes.body
Kanban methodology is designed to meet minimal resistance. So it allows continuous small incremental and evolutionary changes to the current process. It also helps to achieve improvements regarding throughput, lead time and quality.

Kanban boards allow visual management of software development project work. This helps team members to see work in progress. It also helps them to understand complex information like processes and risks associated to complete work on time.

Kanban boards prove effective as it helps team members to become more productive while reducing the amount of workload stress that project managers and team members feel during a project lifecycle.

Kanban software development method should be implemented if the team has a process which works fine but still needs some optimization. Kanban process allows them gradually improve all their tried and tested process.