Facebook
LinkedIn
RSS Feed
NewsletterJoan managed a few projects for a couple of customers. In all cases the process looked pretty similar. With another implementation of the same system for a new client she was quite certain there won?t be huge differences. Unfortunately the client worked in a much formalized environment and enforced very long, waterfallish acceptance tests. This stage took 3 times more than it was planned. Slip had an impact on rest of schedule and as a result project was delivered way too late.
Creating Clear Project Requirements (1 of 5)
Differentiating “What” from “How” Requirements Definition: Through our experience working with project teams, in many industries, on hundreds of projects, we recognize that although Project Managers may understand the theory for developing project requirements they don’t have viable tools, techniques or processes for enabling project stakeholders to clearly define their needs and the expected outcomes for the project. On many projects, the requirements definition effort can take months or, in extreme cases, years to complete before any tangible benefits are realized by the project effort. In this case, it is not uncommon for the environment the project was originally established under to have changed.
Read more...
Constraints & Assumptions
Constraints are factors that may limit the project management team’s options, whereas assumptions are factors that for planning purposes may be considered to be true, real, or certain. Understand the differences between constraints and assumptions, and be able to recognize examples of both.
