Another agile methodology is Kanban, XP (Extreme Engineering, Lean thinking).

Let us compare the Kanban and Scrum Approach.

Similarities 

•  Both are Lean and Agile 
•  Both use pull scheduling 
•  Both limit WIP 
•  Both use transparency to drive process improvement 
•  Both focus on delivering releasable software early and often
•  Both are based on self-organizing teams 
•  Both require breaking the work into pieces 
•  In both, the release plan is continuously optimized based on empirical data (velocity/lead time)

Scrum Board:

Kanban Board: 

Now the whole workflow is on the same board. In the example above the “Backlog” column is just a general Wishlist, in no particular order. The “Selected” column contains the high priority items, with a Kanban limit of 2.

The “Dev” limit of 3 is shared among the two sub-columns. Why? Let’s say there are 2 items in “Done”: 

That means there can only be 1 item in “Ongoing”. That means there will be excess capacity, developers who could start a new item but aren’t allowed to because of the Kanban limit. That gives them a strong incentive to focus their efforts and helping to get stuff into production, to clear the “Done” column and to maximize the flow. This effect is nice and gradual – the more stuff in “Done”, the less stuff is allowed in “Ongoing” – which helps the team focus on the right things.

Scrum is less prescriptive than XP since it doesn’t prescribe any specific engineering practices. 

XP (Extreme Programming) is pretty prescriptive compared to Scrum. It includes most of Scrum + a bunch of fairly specific engineering practices such as test-driven development and pair programming. 

The five values of XP are communication, simplicity, feedback, courage, and respect.

1. Extreme Programming empowers your developers to confidently respond to changing customer requirements, even late in the life cycle.
2. Extreme Programmers constantly communicate with their customers and fellow programmers. They keep their design simple and clean. 
3. They get feedback by testing their software starting on day one. They deliver the system to the customers as early as possible and implement changes as suggested. 
4. Every small success deepens their respect for the unique contributions of each and every team member. 
5. With this foundation, Extreme Programmers are able to courageously respond to changing requirements and technology.

Lean Thinking:

The principles of Lean thinking are:

Lean says to relentlessly eliminate anything that isn’t adding value and only work on what we absolutely need to be doing at this moment in time. Eliminating waste means eliminating useless meetings, tasks, and documentation.

Lean says to respect that the people doing the work are the ones that best know how to do it. Give them what they need to be effective and then trust them to do it. Software development is about learning, so structure the work to ensure we’re continuously learning. Finally, develop in a way that builds quality into our product, because there’s no way to continuously deliver fast if we have to keep going BACK to clean up our messes.