People and team member management for Agile project management and Scrum software development teams.
The notion of coaching is specific to Agile approaches in the software development world. There has always been consultants, but they were seen as a different role. Here are some resources about Agile coaching, starting with some quotes from the Agile Coaching book written by Rachel Davies and Liz Sedley.
As you advance in your career, your responsibilities evolve from being a junior to a senior, manager, architect, or scrum master. How does this transformation affect your daily duties, and what value do you bring to the team? Can your team function efficiently without you?
How do you get people to work effectively as a team? Instead of reorganizing every two weeks, maybe we should focus on what makes teaming work. Books and blogs focus on psychological safety, communications, trust, personal growth, and a shared purpose.
Sizing an Agile team is not an easy task. In this article, Mark Haynes discusses some of the factors (control, the nature of the work, optimal communications) that will influence the decision for the size of a Scrum team.
Implementing Agile and Scrum in software development organization means a big change. In her book “The Great ScrumMaster“, the Agile coach Zuzana Šochová recommends an eight steps journey for a successful transformation to the Scrum approach.
Successful initiatives to change software architectures are directed at achieving an outcome, rather than producing output. Objectives & Key Results (OKRs) provide an accessible mechanism for Scrum teams to set and track desired outcomes as goals.
We all know that there are three roles in Scrum teams : product owner, scrum master, and the development team. Modern software development can sometimes require a high level of specializations that could be beyond the capabilities of the Scrum team members.