Member-only story
Difficulties of Being Agile
Common mistakes of transition to the Agile workflow and why you should care about them
As a reputed coach and consultant James Schiel said, a lot of agile organizations instead of being truely agile just using right words. The cause of that is general misunderstanding of the idea of what the Agile method actually is. This leads to a set of mistakes in organizing software development process. In this blogpost I tell about six ones I’ve been coming across most often and of which I think as of the most common and yet crucial.
1. Misinterpretation
People who got used to work with exhaustive requirements often interpret the word Agile wrongly. Programmers think that they are allowed to do anything. Testers are sure that they will need to re-write test cases every day because requirements will also change every day. But in fact Agile methodologies teach us how to get by under volatility: to respond to changes and to re-arrange plans, to meet user’s needs and to deliver product in small chunks. In other words, it teaches us to exist in the real world.
The Agile methodologies teach us to exist in the real world.
