In my role as scrum master for a product development team in a large organization, I am encountering situations day by day that may appear regular to me. Through a series of blogposts that stem from this role, I will be elaborating on these situations and our team. Explicitely not mentioning people by name, and am posting these from a personal title, but hoping that describing these situations may help other scrum masters or other software engineers.
Based on earlier sprints our team so far has delivered, we have an ambition to grow and improve our performance. With a small team of two developers, tester and an agile designer, there should be some room to improve. We all have a thorough understanding of the scrum values and of the agile principles.
For our next two-week sprint, our plan is to focus on the tenth agile principle:
Simplicity, the art of maximizing the amount of work not done, is essential
During a next refinement and planning session, the plan is to identify and actually note down the things that will fall outside scope as part of the acceptance criteria. In the past, we have done this, but all in our heads. The plan – that is carried by the team – is that by making those fences explicit, we can focus more on delivering the basic needs defined in stories. Thus increasing our performance in delivering new functionality, and decreasing the time it takes before customer issues are solved.
P.S. If you’ve enjoyed this article or found it helpful, please share it, or check out my other articles. I’m on Instagram and Twitter too if you’d like to follow along on my adventures and other writings, or comment on the article.
Buffer
Tweet
Share