The UW Madison has been doing IAM for a number of years with a mix of Open Source and custom development. Inflexible Meets current needs but does not provide the foundation and options for expansion that will allow for new services
Back track a minute. Your probably here because you have something in common with us One of the larger institutions in the US. If we can solve our problems, you probably can solve yours. One of the largest research institutions in the US. 42,000 students 16,000 faculty and staff More collaborative research Being asked to provide more services to groups not traditionally associated with the university
Though we got out to good start, we let things get a way from us. We were really doing most of this off the cuff. We lacked a plan.
So why should you listen to us? Well, we’ve retrenched, we’ve developed a plan and have high confidence we’re going deliver for our campus.
Where did we go wrong and why do we thing we’re back on the right track? Mostly not about IAM or IAM expertise, but about project management and planning. Not professional project managers, poor communication and documentation of goals and objectives. So… out with Larry, Moe and Curly and in with a structured approach. We formalized the process, it’s really now a project and assigned dedicated resources.
Lesson learned. This is taking too long. Lack of defined goals and objectives. The IT world changes a lot in 4 years..
Working under old assumptions we decided and continued to think we could build this thing.
Lesson, thoroughly investigate your options. If a lot of time goes by, reevaluate.
Don’t let what you like to do get in the way of what you should do. We all have biases. At some point you have to decide whether you want to deliver or you want to play.
It’s tough to track what actually happened as everyone it gone. Old decisions carry over. Poor documentation.
Nothing wrong with building it, but keep it simple at first. Deliver incremental value so you can keep people engaged.
The bottom line “a project” Identify stakeholders Communicate Have goals and objectives. This can’t just happen!
How did we get off our dysfunctional path? It’s the customers stupid. This isn’t about IT. Customers are demanding that progress be made in this area.
Back to communication. You must deliver or if not, communicate why.
Deliver something! It was time for a change (recognize and take advantage). New executive and new staff.
Fresh view. Someone who’s actually seen this thing work. Able to counter the excuses of the incumbents.
Cannot stress enough the value of a real project manager. This is not a sideline for a techie!
General direction. Start at a high level. Analysis. Start to gather data that can help you decide on a direction.
Fit very well with our culture. It would be exciting to be part of something like this.
Investigate. This is a big decision.
Investigate. Don’t over promise. Be relatively certain of what you can deliver.
Funding is a problem and will influence how you do this. But… you have to do it.
Look outside you borders. Who can you partner with. We all have the same problem!
Scope. We had been applying scope to the wrong level. Needs to be applied to what we actually do, not what we acquire.