![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
Feb. 4th, 2004 07:12 pmAfter two days of playing proto-PM, i've figured out the way to get stuff done at work.
Just make a list of stuff you're not going to do, and *bang* the magic of having it categorized onto that list means that it's irresistable to developers.
My boss still owns the Big Bug List. I own the support request list and the 'excludes' list. Neither of my lists have been subject to PM assignment to our various maintenance releases. There are probably ten to fifteen items on the support request list which aren't closed with one sort of resolution or another. In general, there are four to six which get opened each week, and three to eight which get resolved. The 'excludes' list are bugs or suggestions which belong to one of several side projects or features at various stages of implementation. When i got it, there were two hundred items on it. I'm halfway through it, and of that two hundred, eighty-nine are already resolved. Meanwhile, Al's list- of things which are ranked and allegedly prioritized- grew by three bugs over the last week.
So, for the time being, i'm getting to set policy for my lists. I get to ask the business stakeholders who own the various components to make their suggestions right to me, and get to assign them priority and get them into releases. I got to dictate eight fixes which will be in our mid-month release too. Wheeee.
So essentially what i'm doing is building a case to demonstrate why the maintenance group needs a real PM of its own, as well as doing the job. Hopefully this will translate into there being such a position created, and it'll be logical to let the person who's doing the job keep doing it. So.... anyone interested in a testing job an indefinite period down the road? It'd be testing a web-based application, much of which is a .Net front end with a SQL background, the rest of which is presently Cold Fusion. There'll be some CMS stuff coming within about three months. Experience with automated testing is helpful, but not required; LoadRunner familiarity a plus.
Just make a list of stuff you're not going to do, and *bang* the magic of having it categorized onto that list means that it's irresistable to developers.
My boss still owns the Big Bug List. I own the support request list and the 'excludes' list. Neither of my lists have been subject to PM assignment to our various maintenance releases. There are probably ten to fifteen items on the support request list which aren't closed with one sort of resolution or another. In general, there are four to six which get opened each week, and three to eight which get resolved. The 'excludes' list are bugs or suggestions which belong to one of several side projects or features at various stages of implementation. When i got it, there were two hundred items on it. I'm halfway through it, and of that two hundred, eighty-nine are already resolved. Meanwhile, Al's list- of things which are ranked and allegedly prioritized- grew by three bugs over the last week.
So, for the time being, i'm getting to set policy for my lists. I get to ask the business stakeholders who own the various components to make their suggestions right to me, and get to assign them priority and get them into releases. I got to dictate eight fixes which will be in our mid-month release too. Wheeee.
So essentially what i'm doing is building a case to demonstrate why the maintenance group needs a real PM of its own, as well as doing the job. Hopefully this will translate into there being such a position created, and it'll be logical to let the person who's doing the job keep doing it. So.... anyone interested in a testing job an indefinite period down the road? It'd be testing a web-based application, much of which is a .Net front end with a SQL background, the rest of which is presently Cold Fusion. There'll be some CMS stuff coming within about three months. Experience with automated testing is helpful, but not required; LoadRunner familiarity a plus.
