you are here: Home Home Team

You're going Agile and you couldn't be more excited.  You've read about all of the benefits and want that for your organization and you want it now.  Slow it down a little bit Buddy; realize that not only will Agile change the way you work, it will possibly require organizational and cultural changes.  Your organization only has a certain amount of change it can consume successfully in any given period - you only have so much transitional velocity.

One of my partners in crime at VersionOne, Mike DePaoli, has started a series of posts regarding using Agile to scale Agile.  I couldn't agree more with the thread and chatted with Mike briefly about adding a topic I spoke about at Agilepalooza - the idea of transitional velocity.  We know what velocity is in terms of Agile - the rate at which a team is delivering value, usually measured in average points per sprint or iteration.  Transitional velocity is how much change we can successfully introduce and make sustainable in a given timeframe.

Del.icio.us!StumbleUpon!

Finding the right amount of detail and decomposition with stories takes agile teams a few iterations, possibly releases, to get comfortable with.  It is a tough balance - we want the stories to be large enoughBut is it Jeff Patton? that our product owner(s) understands what the story is for and the team understands the story contextually, yet we need the work small enough so that we can have confidence in estimating and so that we can get the story flowing through our feedback loop soon.  I want to outline briefly how I like to approach this in the hope that it may help some others.

Jeff Patton is one of my favorite people, an overall awesome dude, and his storymapping is such a beautiful tool that I wish more tools would naturally support it.  When I am working with companies, I use storymapping as means of helping people not only visualize their product but also as means of helping groups understand where and when to break down work.  If you haven't heard or used storymapping before, please do check out Jeff's blog posting on it.  Its ok, I will wait.

Del.icio.us!StumbleUpon!

Its a little known fact that google was built by 3 staplers, a set of paperclips, and a couple of 2 by 4s.  Yep, some smart dude with a great idea had someone look at his product and that person replied, 'We can do this.  We just need about 4 dev resources and a few qa resources.'The stapler is off to the side

As ridiculous as this sounds, we still see it regularly in software development.  Not only is it amazingly demeaning to call people 'resources,' it also leads to other fallacies, such as:

Del.icio.us!StumbleUpon!

Who's Online

We have 75 guests online

Advertisement

Featured Links:
Joomla!
Joomla! The most popular and widely used Open Source CMS Project in the world.
JoomlaCode
JoomlaCode, development and distribution made easy.
Joomla! Extensions
Joomla! Components, Modules, Plugins and Languages by the bucket load.
Joomla! Shop
For all your Joomla! merchandise.

Login Form