Identity and Access Management, Identity Governance

ITSM is  (1) Best Practices (2) Non-prescriptive (3) Non-proprietary Best practices - compiled experiences and success factors from various organizations over decades In the end ITSM provides a framework that is descriptive This framework has to be adopted by an organization and accordingly adapted to the particular organization. How it is adapted is left to the organization - It is NOT a HOW TO DO. HOW TO DO is actually implementing Adopting is NOT implementing ITIL. (because ITIL is a set of best practices) Adopt is about governance required to manage IT services. Now to implement governance your require policies, and this results to an organization adapting to ITIL. ITSM is a management system. Comparison with COBIT The process focus of COBIT is modelled via a process model that subdivides IT into four domains PBRM Plan Build Run Monitor Plan and Organize Acquire and Implement Deliver and Support Monitor and Evaluate and its Governance...

DevOps as the name suggests is composed of two words, Dev and Ops, i.e. Development and Operations. Development as in Application or Software development and Operations as in IT Operations. Traditionally these two streams have been distinct with a strict boundary between the two work streams. DevOps is a melding of these two work streams to bring in cohesion between the Development and IT Operations teams for better and transparent communication and collaboration. Even though these are two different streams (Development and IT Operations) with specific skill set, DevOps (Dev and IT Ops) brings in faster and smooth deployment cycles. Earlier or traditional Development handing off to Operations was slow and had rigid deployments. If things broke in production, the version is sent back to Development for a fix with a bug report, Development would reproduce the issue, provide a fix and send to Operations for deployment. This traditional cycle from Application Development, to testing an...