At the request of our Product Manager, I recently took over ownership of the internal identity and access management application for SPH Analytics. My first action as PO was to understand the “state of the world” with the app, and then work towards a SWOT analysis that would ultimately form the product’s roadmap.
My research took me to all the standard places; interviewing developers, researching standards and security. I covered a-lot of ground learning how and why we got to where we are today.
Here’s where it gets a bit interesting, when I got to the external Threats part of the SWOT, my research continuously exposed the question of ROI when creating an identity and access management from scratch. Why do we need a team of people in-house reinventing the wheel, and scrambling to stay current on difficult things like:
- Server Configuration / Security
- Penetration testing
- Support for Single Sign On
- Platform agnostic support
When there are world class solutions out there with teams of people dedicated and up-to-date on the really difficult stuff. SPHA’s core specialty is doing analytics heavy lifting to enable healthcare professionals the means to Take Action with distilled pertinent information.
Conclusion: It’s going to be a bit of a wait, but our next version of identity and access management app will use AWS
or something that looks a-lot like it. Leaving us again to focus on our analytics game and empowering our users. I’m excited to see how different it will be to manage a product on an outside system.
This entry was posted in Interactive Conversation
and tagged Cloud
, Cloud Apps
. Bookmark the permalink