I believe agile methodologies are a major cause of developer burnout. This "always on" mindset takes it's toll after a while, the constant pressure to implement, bugfix and deploy, resolve production issues and start all over again ad infinitum. While there is no doubt agile is better for the customer, sometimes I yearn for the waterfall model where you have long uninterrupted periods of development where the pressure is off.
Hi, I'm Gregory Brown.
My goal is to help software developers get better at what they do, whether they've been at it for five weeks or fifty years.
(he/him)
I feel the same way about Agile-as-practiced in most places. It has its use case, but making it the standard and sole process of development can turn things into an endless grind.
For the discovery and design process, I appreciate things like Basecamp's Shape Up method:
I believe agile methodologies are a major cause of developer burnout. This "always on" mindset takes it's toll after a while, the constant pressure to implement, bugfix and deploy, resolve production issues and start all over again ad infinitum. While there is no doubt agile is better for the customer, sometimes I yearn for the waterfall model where you have long uninterrupted periods of development where the pressure is off.
I feel the same way about Agile-as-practiced in most places. It has its use case, but making it the standard and sole process of development can turn things into an endless grind.
For the discovery and design process, I appreciate things like Basecamp's Shape Up method:
basecamp.com/shapeup
We use Shape Up philosophy at DEV and it's been really solid.