On Requirements

“What obstacles do project managers face to successful completion of an Information Technology project?”

System Administrator; Financial Services firm

“REQUIREMENTS, well stated, and upfront is the key to successful completion of any project; not just IT projects. Creating requirements on the fly while in the midst of a project indicates poor planning, creates havoc with all team members and produces false positives as to when the project can or will be completed. It is important to recognize that IT projects are inherently complex and require a considerable amount of planning and forethought before exercising. But in order to plan and account for budgets, time and energy, one must fully grasp and tackle the REQUIREMENTS! Be wary, do not make them up as the project flows...”

MüTō Observation:

Requirements are tantamount. So, the PM's ability to LISTEN, and make certain that the business is 'winded', and that IT has no further exploratory questions is tantamount as well, eh?

One way for Requirements to be guaranteed is for PM's to accept the responsibility of making certain all parties are in agreement on 'what the project requires' before moving onto building it.

Funding changes happen, but they become easier when they are not surprises/scope changes. On that...the business is the business, and they reserve the right to change their minds...but SOMEONE has to hold them accountable for the issues that will raise on a project. Business folks appreciate it, if handled appropriately.