Over the past 20 years Agile, Lean, Scrum and Kanban have been steadily gaining popularity in various fields and industries, and rightly so.
According to the Project Management Institute and its Pulse of the Profession 2015: Capturing the Value of Project Management 2015, 75% of highly agile organizations met their goals/business intent, 65% finished on time, and 67% finished within budget, which is higher than what organizations with low agility achieve. The same research shows that agile organizations grew revenue 37% faster and generated 30% higher profits than non-agile companies.
Lean Startup principles have proven their effectiveness too. So thanks to lean approach, Dropbox went from 100,000 registered users to over 4,000,000 in 15 months; Wealthfront company now manages over $200M and processes over $2M a day; IMVU has reached 50 million registered users and a $40+ million annualized revenue run rate.
Although many companies are currently implementing or leaning towards these modern methodologies, usually there are only a few people in the company who understand the whole process from A to Z (Scrum Master or Lean Manager).
Other employees, especially if they are in big companies with complicated communication systems, follow the rules without deep insight. It doesn’t mean that they are bad at work, it could be just the opposite — they may be focused on their functional tasks (which is good).
But as long as they do not know the basic principles, do not share corporate philosophy, are not ready to challenge one another, or cannot distinguish between Agile, Lean, Scrum and Kanban, their company will not see any change in productivity.
Lack of knowledge among the staff leads to lower motivation and generally worse results. This is the reason why methodology basics must be learned and SHARED by every employee involved. We wrote this article to stop misunderstanding and explain in simple terms:
- why some methodologies became so popular;
- what are their basics;
- what are the differences between them;
- is it possible to choose which methodology is the best.