As a Scrum Master of the team, I often raise questions to stimulate the team’s discussion and improve their understanding of Scrum and other frameworks or practices we use. “It’s Thursday and the fourth day of our 5-day Sprint,” I said, “If I pull a Product Backlog Item from the Backlog, I have to finish it by tomorrow, or else the Work Item Age will be increased by 2. Should I pull it or slice it to guarantee I can finish it by tomorrow?” ...
Last month, I wrote a blog post about why I have refrained from using Story Points and capacity estimation in my team since day one. I have been delving deeper into Kanban and immersing myself in the materials, and I have started implementing it. After introducing Kanban and Flow Metrics to my team, I received a lot of questions and feedback from them. Kanban is a strategy for optimizing the flow of value through a process that uses a visual, pull-based system. There may be various ways to define value, including consideration of the needs of the customer, the end-user, the organization, and the environment, for example. ...