Prioritization
At one of the clients I work at, they prioritize their tasks by “Must”, “Should”, “Could” and “Want”. Using this system, I’ve prioritized my items (italicized items are new items):
So I guess I’m tackling the photos section first!
At one of the clients I work at, they prioritize their tasks by “Must”, “Should”, “Could” and “Want”. Using this system, I’ve prioritized my items (italicized items are new items):
So I guess I’m tackling the photos section first!
Ok – so it’s totally the product manager in me but before you put priority levels on things shouldn’t you have a goal that you’re mapping against?
In the projects that I work on, that’s what drives the prioritization.
So really – what are you trying to accomplish with you blog?
Posted by Claw on 23 July 2003 @ 6pm
Good point but then you can go one step further and say I lack user cases which drive the requirements which THEN drive the task list, the estimates and the prioritizations. Luckily, I’m the business owner, the developer, the project manager and the HCI guy so I communicated them, but only to myself. I just happen to document the project plan on the blog
Posted by KC on 23 July 2003 @ 8pm
Okay claw&KC,
I was reading Claw’s comment, and laughed. Then I read KC’s comment, and laughed even harder, funny funny funny.
Then H. heard me laughing and said “What’s so funny” and I got about 3 seconds into the explanation and realized that we’re all really badly geeked out because there was no way I was going to be able to explain it to H. and get her to laugh along (though she might laugh at).
Posted by Wyatt on 26 July 2003 @ 4pm
I’m with Wyatt. You guys are geeks — well-organized geeks, but geeks nonetheless.
Posted by mfk on 31 July 2003 @ 7pm
4 Comments