Day 2 - Part I (Stakeholder Profiling)

Howdy! It's Day Two and we are working on Stakeholder Profiling (using a fictitious company). This is an important part of gathering Architectural Requirements...

Here's the process we are modeling from the EA perspective...

1. Identify Stakeholders (who will have a potential impact on architectural decision-making? Sometimes this includes 'boots on the ground' employees.)

2. For each stakeholder, identify the role of the stakeholder.

3. Identify Business Goals
(someone suggested SMART = Specific, Measurable, Attainable, Realistic, and Timely as a way to define goals)

4. Identify System Goals (more granular)

5. State the "value proposition" for each stakeholder.
(i.e. "Future development will work like clockwork...")

A few thoughts...

This seems to be a step we do informally (and incompletely) as a part of our "system development" at SLU, and I don't think I've seen these things formally documented anywhere in our environment...

There are 15 participants here, many from major companies, but I am the only Higher Education Rep here... it is interesting to hear some of the same development and challenges we see at the University level. There was an informal discussion this morning of how important it is to have a Project Management Office (with some control over resource planning) and a strong Change Control process. Someone mentioned "business change control" which I plan to research later.

More later...

:-)