Novell IDENTITY MANAGER 3.6.1, Installation Manual

Page: 18 / 104

18 Identity Manager 3.6.1 Installation Guide
no
vd
ocx
(e
n)
17
Sep
te
m
be
r 20
09
2.1.3 Identifying the Key Business and Technical Stakeholders
Identifying all stakeholders involved in the Identity Manager solution is important for the success of
the solution. In most companies, there is not just one person you can contact who understands all
business and technical aspects of the business processes. You must identify which services and
systems are going to be affected by the Identity Manager solution, and you must also identify the
person who is responsible for that service or system.
For example, if you are integrating an e-mail system into your solution, you would need to list what
the e-mail system is, who the e-mail system administrator is, and what the contact information is.
You can add all of this information into the Designer project. Each application icon has a place
where you can store information about the system and the system administrator. For more
information, see “
Configuring Application Properties ” in Designer 3.5 for Identity Manager 3.6
Administration Guide .
After you have identified all of the people involved in each business process, the next step is in
Section 2.1.4, “Interviewing All Stakeholders,” on page 18 .
2.1.4 Interviewing All Stakeholders
Interviews with key business and technical stakeholders allow you to gather information needed for
a complete design of the Identity Manager solution. The interviews also allow you to educate each
stakeholder about the Identity Manager solution and how the solution affects them. Here is a list of
items to cover when you do the interviews:
Š
Define or clarify the business processes being addressed by the Identity Manager solution. The
person you are interviewing might have information that can change the current plan.
Š
Determine how the solution will impact the stakeholders and address any concerns they have.
Also ask the stakeholders how much time their part of the solution might take. They might or
might not have an estimate, but gathering this information helps to determine the scope of the
solution.
Š
Capture key business and systems information from the stakeholders. Sometimes a proposed
plan might adversely affect a business process or a system. By capturing this information, you
can make educated decisions about the Identity Manager solution.
After you have interviewed the key stakeholders, the next step is in Section 2.1.5, “Creating a High-
level Strategy and an Agreed Execution Path,” on page 18 .
2.1.5 Creating a High-level Strategy and an Agreed Execution
Path
After all of the information is gathered, you need to create a high-level strategy or road map for the
Identity Manager solution. Add all of the features you want to be included in the Identity Manager
solution. For example, new user accounts are generated from a request through a workflow, but the
type of user depends upon the resources the user is given access to.
Present this high-level strategy to all of the stakeholders in the same meeting, if possible. This
allows you to:
Š
Verify that the included initiatives are the most correct and identify which ones have the
highest priority.