Reading List: Process
These resources helped shape my thinking on the software development process. I prefer developer driven, true agile (opposed to waterfall in scrum clothes) projects that are shipped early and often. Feedback is gathered quickly and the customer gets a larger say in the process.
Books #
- The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business
Blog Posts #
- Agile Manifesto
- If you have to have some sort of process (Yes, development can work without process) then this is it. It’s undefined, figure out what works for the team.
- Design by Committee
- FrequencyReducesDifficulty
- Why should you deploy often? The same reason you go to the gym often!
- Classic Mistakes: Steve McConnell
- Don’t (guess)timate your projects, forecast with confidence
- Products Over Projects
- Goodhart’s law
- You don’t need Scrum. You just need to do Kanban right.
- Technical Decision-Making and Alignment in a Remote Culture
- How a startup loses its spark
Videos #
Agile #
- A Retake on the Agile Manifesto
- Martin Fowler has a great take on the abbreviation S.A.F.E. in this video. It’s a terrible project management system to work under.
- The death of Agile – Allen Holub
SAFe #
SAFe is the worst process I’ve worked under. The amount of wasted time ($$$) in meetings and process was staggering. Make no mistake this is just another term for waterfall.
- Beware SAFe (the Scaled Agile Framework for Enterprise), an Unholy Incarnation of Darkness
- The SAFe Delusion
- Large Agile Framework Appropriate for Big, Lumbering Enterprises
Estimation #
I do not believe that estimation is a requirement in the development world. I have no problem with t-shirt sizing (dev days, dev weeks, dev months, etc) but even then I’ve had leadership “hold developers accountable” to the rough estimate. It causes more problems than it’s worth, corners are cut, teams get stressed and burnout, technical debt isn’t paid off, etc.