Empowering Growth Through Education, Coaching & Development | Agile Coaching services
Browsing Tag
The post reflects on the evolution of software development, highlighting three key eras: the Age of Process, the Age of People, and the current Age of Tools. It emphasizes the importance of discipline and a balanced approach, combining people, processes, and tools, to navigate challenges and achieve high-quality software development effectively.
Timeboxing is a vital practice in Agile methodologies, enhancing productivity and predictability. It structures work within iteration-based frameworks like Scrum and XP, creating urgency and facilitating planning. In continuous methodologies like Kanban, it maintains focus and allows for efficient process improvements. Overall, timeboxing drives measurable outcomes and sustainable productivity across various environments.
Extending deadlines in software projects often reduces productivity, as evidenced by the ‘Beginning, Middle, and End’ cycle. Adopting shorter two-week? iterations enhances focus, feedback value, and engagement, while maintaining a sense of urgency. This approach stabilizes team velocity and promotes effective breakdown of tasks, ultimately optimizing workflow and delivering quality outcomes.
This post presents Brook’s law as a systemic issue, and how to interpret it for agile projects.
Planning Poker has become the de facto estimation technique in agile teams. Like many agile practices, it elegantly packages theoretical concepts into a practical, easy-to-follow process. This post explores the hidden foundations of Planning Poker by combining three powerful ideas: measurement theory, research on cognitive anchoring effects, and the Delphi estimation technique. Understanding these underlying principles helps teams move beyond just following the process to truly mastering the art of collaborative estimation.
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.