Log in

No account? Create an account

Previous Entry | Next Entry

Apr. 1st, 2008

I give shit to project managers, mostly because they're in a bad place, having to try and extract information on herding cats while herding cats and reporting the extracted cat-herding metrics to management. Since I'm usually one of the cats, it's fun.

Today I got an e-mail from my manager that he wants me to manage the bug fix project* for our ongoing software development process.

So now I get to ride herd over the cats. While extracting information on the cat herding. While being one of the cats.

You may now proceed to point and laugh.

*The bug fix project has no end, it's managing all of the bug fixes for our software.



( 9 comments — Leave a comment )
Apr. 1st, 2008 06:11 pm (UTC)
Um, congratulations? Do you get a pay raise?
Apr. 1st, 2008 06:27 pm (UTC)
Nope. It's not even really a title. It will look good for next year's review though.
Apr. 1st, 2008 06:11 pm (UTC)
Apr. 1st, 2008 06:29 pm (UTC)
Apr. 1st, 2008 06:13 pm (UTC)
Get yourself into a nice monthly release cycle for the bug fixes (anything less is chaotic and hard to scope) and you'll be golden. Once you get a couple cycles ahead it's easier to manage because the cats can estimate better what the fix will cost you time-wise, so you can see if it slots into the resource plan for this release, or the next (or the next, or the next...).

I don't envy you; have fun!
Apr. 1st, 2008 06:29 pm (UTC)
We're shooting for a monthly release, and week-scope task breakdowns. Just what I needed.
Apr. 1st, 2008 09:01 pm (UTC)
If you do not already, you should take a look at tracking bugs/fixes in something like bugzilla. I also agree with the monthly release approach. I have a client that is actually moving from bugzilla to Remedy, so that all bugs/fixes across multiple product lines are in a single tool and can be cross-referenced.

If your organization has adopted ITIL, setup a meeting with the process architect for Release Management, or if that practice has not been implemented or started, Change Management. The idea is to use whatever process/technology is used by the rest of business. This gives you two benefits - you are adopting existing standards (increasing efficiency/leveraging existing) and it pushes support of said tool/process back on the owning group (focus on core competencies).

I have a couple of spreadsheet templates that I could share with you, if you are interested. I would need to cleanse them, but I could do that fairly quickly.
Apr. 2nd, 2008 03:14 am (UTC)
Sharing is good. We use TrackWEB for the issues database, but I really need something that I can do task subdivisions from that.

We're doing a modified Scrum, so it's pretty much new to everyone in the place. Should be interesting.
Apr. 2nd, 2008 01:37 pm (UTC)
I'd laugh, but I have too much empathy for your situation. Far, far too much empathy.

Good luck.
( 9 comments — Leave a comment )

Latest Month

April 2012


Powered by LiveJournal.com
Designed by Tiffany Chow