Senior Software Engineer and Project Manager: Difference between revisions
From Future Worlds Center Wiki
Jump to navigationJump to search
No edit summary |
|||
| Line 4: | Line 4: | ||
# Work closely with upper management to ensure prioritization of work according to Board priorities | # Work closely with upper management to ensure prioritization of work according to Board priorities | ||
# Responsible for planning, processing and performing all jobs and tasks in an efficient manner with no need for assistance from the supervisor | # Responsible for planning, processing and performing all jobs and tasks in an efficient manner with no need for assistance from the supervisor | ||
Prioritization[edit] | |||
Main article: Requirement prioritization | |||
A key aspect of Product Management is the correct prioritization of enhancements. Here's a method that works well (borrowed and adapted from Joel Spolsky): | |||
Identify the panel, i.e. whose opinion you are going to seek | |||
Make a list of all items | |||
Estimate the effort required (either in days or in money) - this needs to be very rough and approximate | |||
Add up the total effort, call it E | |||
Give the panel members a budget of 0.5 × E each - they can place this any way they like, including all on a single item. You should disclose the rough estimates to the panel, as it may influence their vote. | |||
Rank the items in terms of the ratio Votes / Estimate | |||
Do as many of the items as the actual budget allows, respecting the sequence | |||
