Sorry, you need to enable JavaScript to visit this website.

Five Goals for Your Identity and Access Management Operations Software Factory: Part V

Five Goals for Your Identity and Access Management Operations Software Factory: Part V
October 16, 2019

In my post in June, which summarized three goals, I mentioned that in a medium to large identity and access management (IAM) operations environment, it becomes very expensive in the long term to not use standardized and reusable components. I also recommended artifacts and components that are reusable in extensible manner, because reusable components are the foundation for sustaining agile-based DevOps.

While growing your inventory of reusable artifacts and components in your IAM operations software factory, it’s essential to align them to their usage in your upcoming release. This brings me to the long-awaited goal #4: Make DevOps Agile. The release might include one or more of the following:

Make DevOps Agile: For Identity and Access Management, it’s smart to adopt agile methodologies over multiple iterations.

  • Data center migrations
  • Process enhancements
  • Digital transformation initiatives
  • Application onboarding or migration
  • Mergers, acquisitions, and divestments
  • Compliance and regulatory requirements
  • Core software component version upgrades
  • Changes in organizational policies and procedures
  • Upgrading virtual appliances

Experienced scrum masters and program managers know that not all aspects of IAM operations and their software factory follow agile methodologies and frameworks such as scrum, SAFe, LeSS, Kanban, etc. It’s fundamentally important that a release be closely coordinated by an experienced IAM architect who can identify, assign, and plan release features applicable to traditional waterfall project management techniques and to a new agile methodology of your choice.

Typically, organizations are cautioned against using agile methodologies for the initial IAM infrastructure setup and first deployment release of IAM integration such as application onboarding, process, and custom components. It is more efficient (and probably more cost effective) to adopt agile methodologies over subsequent iterations. Best of all, this can be accomplished in an operations environment in which applications follow their release train on your chosen agile methodology.

Here are some features that can be released easily, using most of the preferred agile methodologies:

  • Data analytics
  • Architecture documents
  • Runbooks and operational manuals
  • Enhancements to custom components
  • Simple web services and API-based integrations
  • UI enhancements to improve the user and customer experience
  • Enhancements to business processes such as workflow
  • Enhancements to existing IAM operations ETL and workload management

Taking inspiration from Elton John’s “This Train Don’t Stop There Anymore,” we need an agile train that keeps chugging and expanding to many applications, directories, and databases, and dealing with operational overheads like version control, upgrades, break fixes, enhancements, and releases.

Enterprise Studio offers a wide range of professional services that cater to your needs in managing the operation of solutions such as Broadcom’s Layer 7 Identity and Access Management with best-of-breed offerings and products such as Rally (formerly CA Agile Central) and Clarity PPM. If you’re looking at becoming agile, your train will have an edge over your competition when you have Enterprise Studio as your digital transformation partner.

The last aspect of an enterprise grade IAM infrastructure is automation – it permits collaboration of software in business support processes. You’ll hear from me soon on this topic. In the meantime, if you have questions or comments, or need help, please post your thoughts below.