We had a strategic meeting today, where I was asked to present how we can sell our software process expertise to clients within the company. This means that we would consult how to build a software development process in one of the departments in the global company. I presented the basic agile process as a
Oren writes about what’s needed to develop a real application today, in regards to using just the CLR. Although my personal development are very small projects, I can’t live without TestDriven.Net or Reflector. I haven’t used IoC, but I expect this is something I’m going to use from now on. There is something to be
Continuing with the metric fest, we calculated that throughout the last year, one of the projects accumulated more than 250 open bugs. That means that after removing the fixed new bugs, and fixed all bugs from the count, the team is far behind in catching up the runaway train. What’s the solution? There’s not one
We’re working on collecting metrics for the upcoming Management Review, and I’m currently collecting bug information of the different project releases. The data is exported from the database to Excel, and there I do most of the math. At some point, I was sure I was making mistakes, because the formulas became complicated, and if
Roy wrote about tips for a successful team lead. These are things you can start implementing tomorrow morning. I think the Demo is great to create a constraint for the team. James Shore talked about that in his pre-published agile book. I would also add time-boxing with short iterations. When the time to release is