So, I had lunch yesterday with an old colleague of mine. I’d link to his blog, but he’s too much of a coward to put his good ideas in front of the masses *nudge* *nudge*.
Anyway, it hit me how much I missed just talking about the theory and practice of software process. It’s been six weeks or so since I left my previous company, and I’ve been responsible for bootstrapping an entire software process into a company for a new development effort. I still remember, but it’s a bit more distant. On the other hand, I AM living and breathing the practical implementation of all the theories we’ve looked at over the last three years, and I’m starting to really appreciate the work that’s gone into the Lean and Agile approaches to software development. It all just fits with common sense AND productivity.
I’ll probably talk more about specific details as time goes forward, but right now we’re “doing”:
- Agile planning (rolling wave + plan to plan)
- Automated builds
- Automated testing (more so every day, Test First is still eluding us)
- Measuring progress by business value produced (not much yet)
- Some degree of Managing Capacity vs. Available Resources.
Keep in mind that we’re doing this in a pretty small setting… we’ve got three full time and three part time developers and one guy doing some good analysis work to feed the development team. Two of the full timer’s are mostly VB6 experts that are currently learning .NET, and they also have responsibilities sustaining the existing version of the product.
So… there’s the raw materials and the approaches… time to go make it work