The purpose and framework of this blog is to provide a counter-intuitive statement about the Scrum software development process or about software in general, and then provide some tongue-in-cheek response and/or explanation. It is my attempt at humor and sharing, and I hope that – at the least – it is a fun blog to read. Even better would be if it helped me to crystalize my thoughts on software development. An ideal situation would be if it helped you to understand Scrum in a unique and fun way.
I plan to drive directly into the details of Scrum and software development from the very first blogs. Because of this, I must assume that you – the reader – already have a good working knowledge of both areas. Therefore this blog is for “advanced” readers only.Unfortunately, since every software environment is different, every development team has a different cadence and need, and every organization has different drivers and goals, no purely proscriptive approach will work in all scenarios. Because of this, no one is “advanced” enough in software development to be considered an expert in every aspect of Scrum for every environment. Learning how to use Scrum in the world of software development is an ongoing processes. To me, this is the Zen of Scrum. This is why Scrum focuses on “responding to change over following a plan.” Get done what is needed to deliver great software.
Because we are all novices in some areas of Scrum and software development, here are a few learning resources:
- Manifesto for Agile Software Development
- A great video to learn Scrum in 10 minutes
- Scrum guides from Scrum.org
- The Agile Alliance Scrum learning page
- Mountain Goat Software Scrum topics
