Empowering Growth Through Education, Coaching & Development | Agile Coaching services
“Everything that is not a microservice architecture is a monolith!” That is utter nonsense, and I am tired of reading the comparison.
Framing the discussio…
Team composition and performance can be engineered. Thereby, the context can be designed so that a group of people can be led into a high-performing team. This context must focus on establishing shared experiences and responsibilities, rather than relying solely on team-building exercises.
This is the final article of this series.
his third article contains some Q&A that are commonly asked when dealing with velocity.
Second installement of the How to interpret Velocity to improve your agile team productivity.
This article will detail the information contained in each metric and how to use it to improve team productivity.
Velocity is a commonly used metric in agile teams. It is a great metric due to its apparent simplicity. However, I often see teams drawing the wrong conclusions for the metric, which results in decreased productivity.
This post is the beginning of a three-part series to convey my understanding of how to make sense of the information that velocity, as a metric, can provide to an agile team. And use this information to improve the team’s productivity.
Paper of the Month: Interpretative case studies on agile team productivity and management.
Three topics that affect productitivy:
* Developer turnover
* Team Design
* Inter-coordination factors
“Only variation can absorb variation”
Software is intangible, is the result of knowledge work, and is very much prone to variation. In this post, variation means anything that changes the nature of work.
“Intention is at the heart of every decision” Oprah Winfrey
The Software Coach is my new wee space on the internet. It’s a new beginning! A new start that is shaped by intention.