Top Reasons Why Identity Management Projects Fail & How to Avoid Them
1 like615 views
The document outlines key reasons for the failure of identity management projects, identifying major issues such as scope creep, lack of role definition, and insufficient testing. It emphasizes the importance of adhering to the 80/20 rule and engaging business stakeholders throughout the process. Additionally, the document suggests strategies to avoid these pitfalls and improve project outcomes.
Top Reasons Why Identity Management Projects Fail & How to Avoid Them
- 1. Top Reasons Why Identity Management Projects Fail and How to Avoid Them Mali Vanamali CA Services Principal Services Architect North America Security and Compliance Practice
- 2. 2 © 2015 CA. ALL RIGHTS RESERVED. Agenda I n t r o d u c t i o n O v e r v i e w Q & A K e y R e a s o n s f o r I D M P r o j e c t F a i l u r e 4 1 2 3
- 3. 3 © 2015 CA. ALL RIGHTS RESERVED. Underlying business process Types of user population Defining entitlements to match job function Business rules for provisioning WHAT MAKES IDENTITY MANAGEMENT PROJECTS COMPLEX?
- 4. 4 © 2015 CA. ALL RIGHTS RESERVED. REASON 5 Not enough testing REASON 4 Trying to do more in less time REASON 3 Lack of role definition REASON 2 80/20 Rules not followed REASON 1 Scope creep- Moving target Key Reasons for IDM Project Failure
- 5. 5 © 2015 CA. ALL RIGHTS RESERVED. Key Reasons for IDM Project Failure 5 4 3 2 1 Trying to do more in less time Lack of role definition 80/20 rules not followed Scope Creep / Moving Target Not enough testing
- 6. 6 © 2015 CA. ALL RIGHTS RESERVED. Reason 5- Not Enough Testing TEST TEST AND TEST AGAIN. Scope of testing is narrow Real data is not used in testing Too much focus on negative testing Time allocated for testing is limited 5
- 7. 7 © 2015 CA. ALL RIGHTS RESERVED. Reason 4- Trying to do more with less DID YOU FORGET SOMETHING??? Overload Requirements Project end date too aggressive Underestimated functional requirements Lack of coexistence strategy 4
- 8. 8 © 2015 CA. ALL RIGHTS RESERVED. Reason 3- Half Hearted measures Engage the business Lack of automation Lack of birthright role definition Unwillingness to re-engineer business processes 3
- 9. 9 © 2015 CA. ALL RIGHTS RESERVED. Reason 2- 80/20 Rule not followed CLASSIC PARETO PRINCIPLE Don’t try to fit a square peg in a round hole Lack of business involvement Treated as a technical challenge not a business solution2
- 10. 10 © 2015 CA. ALL RIGHTS RESERVED. Reason 1- Scope creep, shooting a moving target New requirements added throughout project lifecycle Accommodating organization changes Accommodating UI/UX changes 1 Level set expectations
- 11. 11 © 2015 CA. ALL RIGHTS RESERVED. Questions?