Seven Identity Management Implementation Risks
I taught a class today addressing best practices in Identity Management implementation. Part of the presentation was entitled “Seven Common Risks.” I lobbied to call this “Seven Deadly Risks,” but some folks thought that title was a bit over the top. Nonetheless, here are seven risky behaviors that could kill your Identity Management project.
- Poor Pre-Project Preparation
- Poor Requirements Definition
- Large Initial Scope
- Inexperienced Resources
- Poor Project Methodology
- Scope Creep
- Not Using Available Support
I’ll elaborate on each in the next few weeks – discussing why each is important and what you can do to migitate the risk.
I am really sorry for being rude but wouldn’t something like this be applicable to any implementation without being specific to identity management. Given the Sun’s experience in IAM space, hopefully you would be covering the specifics of IAM projects w.r.t. specific instances (obviously without the client’s name) and I would love to see you tying them back to one or more of above points discussed above. Any specifics on how the product either helped or hindered (more than what any vendor would like to share :)) in achieving the result.
This should really help us the guys in trenches to learn from vendor experiences.
Thoughts!!
You are right – each of these items could be applied to other entgerprise software implementation projects. But I’ll give some examples as I discuss each topic that will tie directly to Identity Management.
I posted a link to your post on my blog, and someone posted the following:
“Would have been cool if you videotaped it and allowed folks to download. The problem space of project management in general is not honestly talked about…”
I agree.
“Inexperienced Resources.” I remember this term from my IT consulting days. Is there anything quite as dehumanizing as being called a “resource?”