So now we’re after the second (and final) part of the management review. The second meeting was different than the first one. On the first one, the PMs were active (in a defensive way, mind you). This time they were more quiet. I know the feeling from past meetings like this: I want out, the
This number surprised me. In all 3 projects (every project has a different size, complexity and team) there’s a 75% rate of open non-reproducible bugs. What does this mean? I know we’re not doing enough to reproduce bugs. I take that as a given. I also think that since it’s more easy to fix reproducible
I almost cried when I read this. It’s via Scott Hanselman’s blog. Patrick Cauldwell wrote down a list of commandments for the developer. While it is a bit .Net centric, it can be modified to suit everyone. As long their into TDD, continuous integration, refactoring and patterns.
During the management review, we discussed the fact that although there’s extensive testing, critical bugs slip through. One of the PMs, who is a big proponent of exploratory testing, said we’re concentrating too much on writing test procedures, and less on testing. I did actually produce the numbers, thanks to the newly implemented MS Project
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
Guy Kawasaki, of former Apple fame and currently a VC person, who is very famous, raised a website called Truemors. This site get people to post and discuss rumors about everything. But that’s not important. The important stuff is how he did it. And how much it cost – 12K$. With all the difference of
I guess this would be the second favorite, following Manager-Tools. How do I rate them? I guess it’s how long I wait from publish to when I listen. Scott Hanselman is a Boy Wonder. He’s the chief architect in his company, works with Microsoft .Net technologies, but dabbles with many other technologies on the side.
I listen to podcasts on my commute which is currently ~1.5 hrs a day. In addition, another 3 hours during workout. A small calculation I did a few weeks ago – In the year and a half I’ve been doing this, I learned the equivalent of a very stacked semester! That’s a lot. First and
I’m finally done with extracting bug information. All projects show a runaway bug train trend. 2 of the teams have ~250 bugs accumulated over the last year, the 3rd has 90. These usually end up as an extra cost to the customer and us, moving on with subsequent releases. And there’s the cost of find-fix-retest