Abstract
So what happens when the project goes live and people start rolling off? Is all that knowledge lost? How do you stop the “I didn’t write this crap” mentality from setting in. I can’t even count how many times I’ve heard that phrase. I’ve heard so many developers use the “I wasn’t involved in that decision, so I’m just going to follow what they did” excuse instead of refactoring a bad piece of code. This doesn’t fall into a single clean Agile category, but it affects things like code quality, morale, and ultimately the productivity of teams, so I thought it would be good idea to cover it in this book.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2015 Tim Brizard
About this chapter
Cite this chapter
Brizard, T. (2015). Long-Run Plan for Success. In: Broken Agile. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-1745-0_5
Download citation
DOI: https://doi.org/10.1007/978-1-4842-1745-0_5
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-1744-3
Online ISBN: 978-1-4842-1745-0
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)