Scrum, today, has become the most popular framework. Naturally, the folklore around it also has grown over the course of time. Scrum was first published in 1995, and Scrum Alliance officially founded in 2001. During those times, the main source of Scrum was the creators of the framework. Naturally, word of mouth has its limitations… Continue reading Scrum: folktales, facts, alternate- facts, and other nonsense !!
You want to become a Scrum Master, but others who are hiring are looking for experienced Scrum Masters. If you are not a Scrum Master, this leads you into a vicious cycle where it becomes difficult for you to get hired as a Scrum Master. How do you break this cycle? Here are some ideas… Continue reading Catch 22: How do you get Started as a Scrum Master when you are not one…?
The concept of "undone" work does not exist in Scrum today, but nevertheless, it makes sense to understand this concept when Scaling Scrum . Most people confuse incomplete work and "undone" work. To understand the difference, please see here. Ideally, you should be able to get to a perfect definition of Done before your first… Continue reading Understanding “undone” Work
I very rarely play mobile games, but this one got me. I will save you the trouble of me explaining this game by letting you watch this video. But here are some of the insights I got Look for high leverage points - You very rarely target one brick at a time. Look for "gaps"… Continue reading Five Things that Bricks Breaker Quest taught me about Agile Coaching
Learn how seven habits can make you a better Scrum Master, Agile Coach or a leader
One PO per Development Team instead of one PO per Product Multiple PO for multiple smaller related "products" (e.g. PO for Android PowerPoint, PO for iPhone PowerPoint, PO for Windows Desktop PowerPoint, PO for Mac PowerPoint, PO for PowerPoint 365) There is only ONE product here - PowerPoint. Android, iPhone, Windows Desktop, etc are different… Continue reading Dysfunctional Product Owner Patterns
Every Sprint, the Development Team is responsible for building a "releasable" Product Increment. The Product Owner may choose to release it or may not choose to release the Increment at the end of the Sprint. Scrum does not prescribe a release frequency (i.e. PBIs can be released multiple, times a day, once a Sprint, once… Continue reading This is how you hit the ball out of the park in your first Sprint