Heather Wilcox, NWEA
Agile is a very effective method to develop high quality applications quickly and accurately. However, extended use of Agile development methodologies can result in the development of interesting side effects: Marketing and Sales teams become addicted to a constant stream of new features, fixes, and upgrades. Customers start asking for more and better software and begin to expect near-instant gratification. In response to the demand, Engineering teams crank out release after release which, slowly and quietly takes a toll that often goes unrecognized and can have very destructive results.
Fatigue is only just now being recognized as a problem within Agile organizations and the greater software community. It is something that may be experienced by many Agile-based teams, but very few recognize it for what it is. Even fewer groups are able to respond to it in a useful way.
This paper uses anecdotal and published evidence to explore the signs and symptoms of Agile Fatigue and suggests multiple strategies (both proven and unproven) for fighting it.
Target Audience: Intermediate
2016 Technical Paper, Heather Wilcox, Paper, Slides, Notes, Video.
