Need explanation: why Initiation phase does not have phase of collecting requirements?
Hi,
can please somebody explain this dilemma: Why Initiation phase does not have phase of collecting requirements? Wy PMI classifies the process Collect requirements only into Planning phase (before phase Define Scope)?
Background of the question:
My question applies on situation buyer (customer) - seller. Durign initation phase, seller must define scope and requirements as exact and detailed as possible, in order to prepare contract. But PMI foresees the processes Collect requirements and Define scope only in Planning phase, which happens after Initiation phase. In 3rd edition of PMBOK there was a process of preparing preliminary scope statement, which as I understand, served for the purpose of defining the contract scope, but this process is no longer part of initiation phase in 4rd edition of PMBOK. Process Create project charter does not seem appropriate to me, considering it's description from PMBOK.
Example from praxis: I work in SW industry, we work for customers. We actually do phase of collecting requirements during planning phase (in SW, this is phase of Analysis in design), but we must off course define scope at least high level already during preparing contract and preparing the project (Initiation phase). Which process durign Initiation phase is this?
I hope that my question is clear enough...
KR and tnx for answers.


admin
Sat, 09/17/2011 - 04:42
Permalink
High level scope would be
High level scope would be defined at time of initiation. Even if entire requirement document is available during initiation, you would still have to validate it during planning phase.