Tags: Agile, Automation, estimating, Planning, Sprint
This entry was posted
on Monday, July 27th, 2009 at 6:41 am and is filed under Agile, Outformations, Productivity, by Scott.
You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
If you haven’t yet, you might look into Lean and Kanban approaches to Agile software dev. We’re implementing more and more of these concepts into our development on my current team.
For example, some concepts in this realm include “Release per Feature” and “Branch per feature”. Rather than iterations, the focus is on work flow and minimization of waste. When a feature is begun, the source code is branched. Developers do not work directly on the trunk, but instead work on a branch.
I’m a bit more reticent on the “Release per Feature” idea. I have a sneaking suspicion that it can become a way for devs to say “it will take as long as it will take” rather than committing to any sort of timeframe for delivery of working software. There are ways to mitigate these issues which we are exploring.
In the mean time, I’d characterize our workflow as a sort of scrum/agile/kanban hybrid, something like “Scrumban”.
P.S. If you want a great example of a clean web application and a simple introduction to Kanban, check out http://agilezen.com