- When faced with many stakeholders (as we often are in the library), don't try to balance all the input yourself. Instead, select or ask users to select a representative for the group.
- All projects have 3 constraints which should be identified and balanced: time, budget (costs, staff time), performance. In my opinion, performance tends to be our highest priority (i.e. features), with both time and budget (staff time) as much lower. We tend to spend a lot of time and a lot of resources to get things working the way we want. It is helpful to identify that this is our usual top priority and to consider that it doesn't have to be.
- Identify a project sponsor--the person who has the authority for changes to this service or tool. Ask that project sponsor to sign off on a summary document explaining the project scope, priorities of the constraints, and measures of success. Come back to the project sponsor as changes arise, including changes that alter time, budget or performance.
- Create a Work Breakdown Structure (WBS) and PERT chart with the team rather than in isolation.
- Reliable time estimates for the PERT can be created with a formula using optimistic, pessimistic and most likely time estimates.
- Make contingency plans for the unexpected.
I plan to implement some of these standards for projects that I'm managing. If they work for me, then I plan to suggest for Digital Services projects and model for others in the organization.
