We have few application and from the beginning, developers used one username and password for all the apps.
Now I have been assigned as a PM to change them all.
I was wondering if any of you worked on a similar project?
Thanks
Nahid Saving Changes...
Sort By:
VASUDEV NARAYANANProgram Manager| Pentapolis FoundationChennai, Tamil Nadu, India
Yes, I had the opportunity to work on a project that was part of Identity Management. Please do let me know how could I assist you? Saving Changes...
Yes, back when the HIPAA privacy & security regulations were first introduced in the U.S., I managed a few projects for the healthcare provider I was working for to migrate clinicians from generic credentials to named ones.
The technical aspects of the transition were fairly simple. The human change management ones were much more complex...
Depending on technical considerations this can either be the easiest project you ever work or a modestly engaging project at worst.
For tech projects I always prefer to start at the center and work my way out.
Start with the type of database: application embedded or standalone (SQLite or IBM DB2)
This, along with product documentation and input from the developers will guide your approach to the work.
Secondly: If you're lucky and the databases are housed in one infrastructure accessible by your IT department, then an administrator may be able to change the passwords using a script pushed out by Microsoft Group Policy or a similar method.
However if they are at individual client/customer sites then the hurdles to access each database may be more pronounced and your scheduling estimates will need to reflect that.
Lastly: Diagram and document! Documentation is worth it's weight in gold to IT.
Diagramming helps you to visualize what is/will be done and confirm with your developers what your goal is. Also, it enhances your documentation making it easier to follow for the next PM when your're off doing bigger and more challenging projects. Saving Changes...
