We start by discussing why understanding technical aspects, and having a technical focus is a key asset for Scrum Masters and Agile Coaches. It all starts with the idea that teams should get software in front of their users as quickly as possible.
We discuss Trunk Based Development, and why understanding what that is will help Scrum Masters working with teams that have difficulty releasing on a regular cadence.
Agile is about adapting to change. Change is a reality, we can’t avoid it. How we react to change is what will make or break our product development efforts.
For us to be Agile and adaptable, however, we must be able to change direction quickly. Adjust the deliverables after we collect market/customer feedback. Many teams I’ve worked with were doing exactly the opposite!
Teams often get stuck in the “this story can’t be broken down any further” anti-pattern. They push themselves to deliver enormous User Stories, and therefore end up having to do a lot of upfront planning and estimation (both are needed when the work items are very large).
If teams were able to slice work down to very small increments – say, one day or less – then they would not need to spend so much time planning and estimating. They might even be able to adapt during a Sprint, instead of waiting for the end of the Sprint.
