In addition to checking for solid requirements using the SMART methodology it is important to properly prioritize or categorize the project requirements. This can become especially critical in the large project or project with seemingly unrealistic expectations. There are many ways to categorize these; personally I like to apply the easily understood labels of must-have and nice-to-have.
My goal with the project example is to create a scenario that is similar to those faced in real projects. I find, too often, that textbook examples overly simplify scenarios to the point that the answer is so obvious that when faced with a real world example the less experienced project manager cannot distill the issue.
Mark is a project manager for Custom BoatBuilders, Inc. Bill manages the custom building of boats for private consumers. Consumers contract with Custom BoatBuilders (CBB) to build custom watercraft for personal use. Mark reports to Steven who is the Client Relationship Manager. Steven’s responsibility is to work directly with the customer and secure a contract for the building of a custom boat. After a new customer contract is signed, Steven involves Bill to execute on the project. Read the rest of this entry »