Pair programming is sometimes the norm, and some developers really enjoy the collaboration, experiencing enhanced productivity. In other teams, pairing is shunned, avoided, or… faked. Angela Harms did a short survey about pairing attitudes and compared successful and unsuccessful pairing experiences.
An Agile team reset occurs when an Agile team take a step back to review and relearn the foundation principles and practices of Scrum. Justin Hennessy presents in this article how he did it when a team he was coaching had successfully implemented the practices for Scrum but didn’t really understand the values or principles behind it.
Continuous delivery allows teams to reduce dramatically the transaction cost of releasing high-quality software, so you can do it much more frequently, providing a much richer and faster feedback cycle from users back to product teams. But, in turn, you need to change the way you think about managing the flow of work through the software delivery process.
The Lean UX that eliminate the contractual obligations inherent with specification documents and other deliverables is presented by Jeff Gothelf in this podcast. He defines Lean UX as “a rethinking of the software design philosophies and methodologies, moving away from the contractual obligations of spec documents and focusing really more on validating your designs through building products and experiments.
The Agile Karlskrona test is a simple self-assesement test that tries to answer the “How agile are you?” question. With 11 questions, this test should help you find where “on the road” from waterfall to agile your software development team is at the moment.
Analyzing the bottleneck faced by a Scrum team, Mark Levison introduces in this blog post the concept of Skills Matrix. The Skill Matrix is a visual management tool that shows at a glance how much cross-training you have in your organization between different people and different tasks.
In this article, Elton Gao starts by giving us the definition of a good ScrumMaster: someone who knows Scrum well. He or she understands the do’s and don’ts and is familiar with related artifacts and tools. He or she knows how to run a daily Scrum, a planning/review/retrospective meeting and how to take advantages of related tools and so on. But is this enough?
Scrum Expert Copyright © 2009-2026 Martinig & Associates