Agile Coaching

These blogposts are my opinions from reflections on topics relating to my current area of interest - Enterprise Agility, Leadership, Entreprenuership, Personal Development and Complexities of Africa.

The Many Faces of Micro Management

You assign tasks to subordinates and chase up for updates as soon as you feel they should have been done. Regardless of what your subordinates are currently doing, you believe they should be working on something else. You have just assigned task to a subordinate and immediately you follow up with instructions on how they should be doing it. You are so bothered about how they spend their time; and you just need to ensure that they have enough work for 40 hours a week, that’s what their contracts says anyways.

Dynamics of privileges in a Scrum Team

An autonomous and self-managing team thrives when hierarchies take a backseat, allowing Scrum accountabilities to drive the ways of working. While organizational hierarchies persist, especially during the formation of Scrum Teams, it’s crucial to discuss privileges and their impact on a team’s ability to self-manage. Hierarchical Privilege: This explicit form of privilege arises when a Scrum Team comprises employees with varying levels of seniority. Senior employees wield influence, sometimes making unilateral decisions that affect the entire team.

Is the Scrum Master role extinct?

With the recent news about Scrum Masters and Agile Coaches being laid off in organizations, the question that comes to mind is whether we are at the end of the road with regard to these roles that have in the past focused on building agile capabilities in organizations on a full time basis. My opinion is that organizations will continue to have a need for people who are focused on helping teams to continuously improve their ways of working, improving team and organizational effectiveness.

Developers Really Hate Scrum? No!

Increasingly, I encounter developers who don’t seem to enjoy using the Scrum Framework to deliver software, and this is a cause for concern because I have fond memories from my days as a developer working on a Scrum Team. I relished the collaborative atmosphere within the team, where everyone supported each other in development, testing, deployment, and held a shared sense of accountability. However, nowadays, I hear developers express their discontent with Scrum for various reasons, including:

What Happens in a Product Refinement Session

The Product Backlog Refinement session is not an official Scrum event, but it is a crucial activity that helps Scrum teams to achieve a shared understanding of the product backlog items in preparation for the sprint planning. Teams that adopt the product backlog refinement as a complimentary practice tend to have smoother sprint planning events. The number of refinement sessions within a sprint depends on various factors such as the state of the product backlog, the maturity of the product, the Scrum team’s availability and experience.

How to improve the Scrum team effectiveness with the sprint goal

The commitments contained in the Scrum Artifacts are arguably one of the important element of the Scrum Framework; these commitments when deployed as per the intentions of the scrum framework contributes to increasing the effectiveness of the scrum team. I was asked to help out a Scrum Team that did not see much value out of a well-crafted Sprint Goal for their Sprints. In the sprint planning, the team would rollover every product backlog item (PBI) that was not completed in the last sprint, and the team would add a few more PBIs from their backlog on the ask of the team manager, who also attended the Sprint Planning regularly.

Is the Product Backlog Management Tool Serving or Hindering the Scrum Team

Selecting a product backlog management tool can be a daunting task, as there are a plethora of options available on the market. Some of the most popular tools include Jira, Azure Dev Ops, Kanbanize, Trello, and Rally, to name a few. As a Scrum Master, it’s important not to view yourself as an administrator for the chosen product backlog management tool, but rather to focus on understanding how the tool can support the Scrum team to be an effective team.

Should Agile Teams Estimate Defects?

Should agile teams estimate defects? This a one question that teams often find themselves debate and my perspectives has changed over the years on this. The short answer is … it depends on your team context and what you are trying to achieve with estimation. Estimation is a practice that helps Agile Teams forecast the effort that is required to get a task done e.g. deliver a feature and as such, it contributes to capacity planning for the team.

Passing the PSM 1 Assessment After a Professional Scrum Master Class

Passing the PSM 1 assessment could be considered an indicator that you understand the Scrum theory and the principles that underpin Scrum. I always tell students in my PSM class, that my intention is not to make them pass PSM 1 but understand Scrum theory and principles. There are a number of exercises that Professional Scrum Trainers invite students to partake in the course of the PSM 1 class; these exercises have been designed on practical experiences of Professional Scrum Masters and these exercises create a solid foundation for you as you commence your Scrum Master career.

Getting Started as a New Scrum Master

You have just passed your PSM 1 assessment; however you would like to get some working experience as a Scrum Master. In my time as a Professional Scrum Trainer with scrum.org, the people that share this concern with me fall in 2 categories: People that have self studied for the PSM and achieved the 85% score for the PSM1 assessment People that attended a Professional Scrum Master class and achieved the 85% for the PSM1 assessment You must realise and accept that passing the PSM 1 assessment is not the end of the learning process; the journey to being an experienced Professional Scrum Master is a life long learning experience.