No, it’s not over yet, and we are in preparations for the follow-up meeting. We’ve compiled a few more charts, and fixed a few mistakes, and will be ready to show those, as well discuss the topics we haven’t covered last time. We can dig through these numbers a lot, and pull out a lot
And I presented the different statistics and everyone asked for forgiveness and changed their way immediately. Not. (Did you expect otherwise?) There’s a general feeling that things are not going well (discussing the results with the PMs prior to the meeting helped alleviate “unpleasant” surprises, and everyone knew what’s going to be displayed). The mood
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
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
One of the things I did as part of the metric collection was look at the number of open bugs in the first release of a version (which should be the Release Candidate, but unfortunately, lately it isn’t) and the final release of a version. What causes extra releases? Bugs. Last minute changes from the