Scrum is simple to understand. The Scrum Guide is just 19 pages. Over the years, I've met many Scrum practitioners who have never read the Scrum Guide or they have read it once and once only. I believe there's something special about the Scrum Guide and because of this, it's important that we consider reading the Scrum Guide as an empirical process itself.
This is the truth. If we turn things upside down organizations can't truly embrace Agility.
I would be lying if I said that we can improve our product delivery process even more.
A small poem about Agility & Scrum
Ahhh... the never-ending debate. What's the value of (Scrum) certifications? Is there any value? Why should you get certified? Is it even necessary? In this blog, Chee Hong gives his opinion about the value of certifications and the reasoning behind getting certified.
Over the years, I've seen countless Scrum adaptions, and I thought perhaps it would be interesting to sum up some of the common misinterpretations. I would love to hear about the misinterpretations that you have faced, so feel free to participate in the comment section.
Just a thought on architecture in a complex environment. What is the value of a perfect architecture? Is there something as a perfect architecture? Perhaps more importantly, when is the architecture perfect?