Add to Google
Archive of Team Practices
Practices that enable component teams to meet their objectives
-
A Scalable Definition of Done
Posted on June 27, 2012 by Dean Leffingwell in SAF Content, Team PracticesRecently, one of our clients was struggling a bit to finalize a complete, scalable and yet achievable, Definition of Done for a specific program. It will likely serve as a template for other programs as well. They asked me to...
Continue reading this entry → -
Efficacy of the Progressive Agile Estimating Scale
Posted on May 17, 2012 by Dean Leffingwell in Metrics, Team PracticesEver wonder why using the Fibonacci (Or Cohn's Modified) sequence relative estimating scale seems to work so well for agile teams? (Ok, me neither, really). But if you are interested in the mathematical roots of why "a little estimating (on...
Continue reading this entry → -
Splitting Epics, Features and User Stories
Posted on April 4, 2011 by Dean Leffingwell in Team PracticesIt will come as no surprise to any agilist that one of the hardest parts of agile development is the ability to split valued, useful work into stories small enough to fit in a sprint. Indeed, team after team has...
Continue reading this entry → -
Refactoring and Software Complexity Variability: A Whitepaper
Posted on January 13, 2011 by Dean Leffingwell in Team PracticesMy friend and colleague, Alex Yakyma, from Kiev, Ukraine, wrote this interesting whitepaper which describes how, based on the underlying mathematics, software complexity tends to be inherently higher than one might think. He also describes how refactoring, our key weapon...
Continue reading this entry → -
Resource Flexibility in The Agile Enterprise
Posted on December 2, 2010 by Dean Leffingwell in Enterprise Rollout, Feature Vs Component Teams, Release Planning, Team PracticesI received this interesting email from a colleague (who allowed me to share it) a few days back. “I currently lead a project on how to increase our resource fluidity so that we can effectively assign sufficient manpower to where it matters...
Continue reading this entry → -
Scrum of Scrum Ground Rules
Posted on November 19, 2010 by Dean Leffingwell in Agile Release Train, Enterprise Rollout, Team PracticesIn the last post, I described an impressive Scrum of Scrums meeting I attended this week. It's a pretty big Agile Release Train that has 14 cooperating teams. After just a few months of agile, this program really...
Continue reading this entry → -
On “Ba” at a Scrum of Scrums
Posted on November 18, 2010 by Dean Leffingwell in Agile Release Train, Enterprise Rollout, Team PracticesI was a “chicken” today at one of the more effective Scrum of Scrums for an Agile Release Train that I have witnessed. Big program. 14 teams. The uberScrumMaster (Release Team Manager) started the meeting at 9 am, facilitated...
Continue reading this entry → -
Organizing at Scale: Feature Teams vs. Component Teams – Part 1
Posted on July 15, 2009 by Dean Leffingwell in Agile Executive, Distrib. Development, Enterprise Rollout, Feature Vs Component Teams, Team PracticesWhile continuing my work with a number of larger enterprises facing the cultural change, new practice adoption and organizational challenges of a large scale agile transformation, the topic has again come up as to how to organize large numbers of...
Continue reading this entry → -
The Simple Math Behind TDD?
Posted on November 25, 2008 by Dean Leffingwell in Team PracticesFor those who have followed this blog or read the book, you might know that I called Chapter 13 of SSA "Concurrent Testing" and not TDD (Test-Driven Development). I talked about TDD in the book, but I didn't specifically...
Continue reading this entry → -
Jeff Sutherland’s Sprint Emergency Landing Procedure
Posted on October 19, 2008 by Dean Leffingwell in Team PracticesLast week, I gave a talk on Scaling Agility at Agilis 2008 in Reykjavik, Iceland. Yes, Iceland has an active agile community within their population of some 300,000-400,000. A local consultancy Sprettur, hosted this conference and invited guest...
Continue reading this entry →