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
Scott Hanselman, who has the excellent technology podcast HanselMinutes, wrote about meeting his idols, and how it sounds to an innocent bystander, in this case, his wife. I remember having this feeling coming off TechEd awhile back, after seeing Don Box on stage (in the great immediate post-COM days). It was easy to share the
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
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
I really like working with smart people. Especially, when I hired them. And that means I like being right. Moving on… Smart people identify bad things and propose changes. They sometimes stubborn to a fault doing that. But that’s OK. The stubborn ones are willing to fight the system, or at least try to prove
I continued updating the Excel template for supporting the metric collection since last time. What I though was a bug was not really a bug. I added a few test cases, but the tests kept passing without code change. Imagine the disappointment… I still had a feeling there’s something wrong. That I was not covering
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
It actually happened today and I’m sold. Due to installing the monthly Microsoft patches, IE decided to close whenever I opened it. A few hours later I isolated which patch actually caused it, and removed it and IE came back to life. But it was too late. In the mean time, I switched to Firefox,
So where do you put all the knowledge you collect? The easiest place is documents. The problem with those, is that the more knowledge you document, the less likely people are to read them. Today (another) argument I was involved in was regarding the use of dynamic/snapshot views in ClearCase. The methodology we have (due