![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Evolution of a PM
Jul. 1st, 2004 04:45 pmThankfully, the process doesn't take the generations that Darwinian evolution does. In fact, we've seen changes akin to genetic mutation with our new PM already.
A few weeks ago, right after he started:
"Code freeze is just that. The code for the release is set, and the only check-ins which should happen are if there are new problems discovered in the code for the fixes."
Today, in our weekly Maintenance meeting:
"I'll defer to QA on this. If they're comfortable with it, we can squeeze it [some new change or other] in. What do you guys think about it?"
"Well, we're pretty much finished our testing for Wednesday's release, so we have the bandwidth to accomodate it, and, hey, if we can fix something that will make people in the company happy, bring it on."
So, now, in addition to being test complete, we're starting to go through our bug tracking application and finding all the old, crusty bugs which have been assigned to triage (aka The Place Where Bugs Go To Die) and figuring out what's still actionable. So far, of the stuff i've looked at from the triage bucket, over two-thirds no longer appear to be valid issues. Guess what group's bug numbers are going to look really impressive, not that anyone really cares here.
A few weeks ago, right after he started:
"Code freeze is just that. The code for the release is set, and the only check-ins which should happen are if there are new problems discovered in the code for the fixes."
Today, in our weekly Maintenance meeting:
"I'll defer to QA on this. If they're comfortable with it, we can squeeze it [some new change or other] in. What do you guys think about it?"
"Well, we're pretty much finished our testing for Wednesday's release, so we have the bandwidth to accomodate it, and, hey, if we can fix something that will make people in the company happy, bring it on."
So, now, in addition to being test complete, we're starting to go through our bug tracking application and finding all the old, crusty bugs which have been assigned to triage (aka The Place Where Bugs Go To Die) and figuring out what's still actionable. So far, of the stuff i've looked at from the triage bucket, over two-thirds no longer appear to be valid issues. Guess what group's bug numbers are going to look really impressive, not that anyone really cares here.
