Transformation from start-to-finish
These days identity management is pervasive and becoming increasingly mission-critical for businesses. Organizations are looking for a reliable, flexible, simple and cost effective ways to implement Identity Management solution. IdentityNest’s experience and best practices will guide you through the entire life of a successful Identity Management project.
The right approach
We use a multi-phased approach so as to gain some return on investment (ROI) advantage early in the project. The content of each phase is decided by analyzing the priorities of the and mapping these through their to Identity Management product capabilities. The earlier phases are dedicated to satisfying those requirements associated with high-priority business requirements and low-cost Identity Management capabilities.
Our goal is to produce a plan containing a phased set of implementation steps where the end result satisfies the functional requirements, and therefore also satisfies the original business requirements. While business and functional requirements are the main parts of the security design objectives, we also must consider other and constraints.
To produce an implementation plan:
- Prioritize the requirements.
- Map the requirements to Identity Management features
- Define the tasks involved to satisfy the requirements
- Estimate the effort required for each task
- Divide the tasks into phases.
Prioritizing the requirements is important because the priorities are one of the primary factors used to decide which implementation tasks will be done in which phase of the project. It is rare that an identity management solution can be created as a single deliverable satisfying every requirement. It is far more likely that it will be delivered in phases, and the highest priority requirements should be addressed in the earliest phases. Assigning priorities to the requirements is often difficult because they are all important. You can more easily compare the priorities of requirements by asking questions that gauge the positive and negative impacts of the requirements:
- How much money will be saved when the requirement is met?
- Are there penalties if the requirement is not met?
- Is there a date by which the requirement must be met?
- Are there other requirements with dependencies on this one?
- If this requirement is not met, is the company any worse off than it is now?
After mapping the requirements to Identity Management features and creating a list of implementation tasks, the requirement priorities and the effort of each task can be used to decide how to break up the project into phases. The goal of breaking the project into phases is to quickly deliver solutions to some high-priority requirements. This allows the company to begin seeing a return on their investment, while lower priority and more difficult tasks are still being executed. Project phases Based on the priorities of its business requirements and the levels of effort of the different implementation tasks, IdentityNest split the project into four phases, as follows: