Information Technology Reference
In-Depth Information
Initially, I was in a systems engineering role on DART and one of my tasks
was to develop the Scope document. I did this by developing System-Level
Use Cases, then having those reviewed and agreed to by the major stake-
holders on the project.
On both Agile and traditional projects, one of the most difficult tasks is elicit-
ing the real needs and expectations of customers and getting them agreed to
by major stakeholders. 10 By building a Scope document and actively engag-
ing the key stakeholders early in a review and approval cycle, a basis for
project success is established.
So the question remains:
Since I developed this key document, and since the stakeholders agreed to it,
why did we run into trouble with Al doing extra work based on his collabo-
ration with Mike?
The answer is that while I developed the Scope document and major stake-
holders agreed to it, I didn't train Al, or Mike, how to use it.
I didn't get to all the stakeholders (both up and down the chain). 11
How could I fail to meet this responsibility?
8.12 More on the DART Case Study
Besides being responsible for the Scope document on DART, I helped the
Project Manager plan the project, and was responsible for developing the test
procedures. The Project Manager I was working closely with, Carl, unexpect-
edly resigned one month into the project. To maintain the aggressive
schedule I accepted the additional responsibility of Project Manager, as well
as fulfilling my Systems Engineering responsibilities. In taking on the Project
Manager role along with the Systems Engineering tasks, every day I had to
make priority decisions as to where to spend my time.
10. This relates directly to Specific Practice 1.1 of the Requirements Development (RD) Process Area of
the CMMI model: “Elicit stakeholder needs, expectations, constraints, and interfaces for all phases of the
product lifecycle.”
11. Generic Practice 2.7 of the CMMI Model, “Identify and involve the relevant stakeholders of the [ fill in
relevant process area ] process as planned,” provides a continual reminder of the need to involve all stake-
holders.
 
Search WWH ::




Custom Search