WIP

The Agile coach training programme at my company has reached its second half. One of the training objectives was to teach the Agile coaches about unit testing and code refactoring. Naturally, the coaching programme expects the trainees to subsequently coach their teams on the same topics. As a mentor to two new Agile coach trainees working in different teams, I often allow them to choose their approach and evaluate it later on. Both teams had no prior knowledge of unit testing and code refactoring. After learning the basic techniques, Trainee A decided to ask everyone to try writing unit tests themselves simultaneously. They would then share and discuss their work during Code Review. On the other hand, Trainee B dedicated all his time to working with a single developer, allowing others to continue working as they had been. Once that developer had grasped everything Trainee B knew, they would split up and work in pairs with the other two developers. ...

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. ...