High Velocity IT Flashcards
ITIL HVIT Certification
What are 7 techniques for fast development
1- IAC
2-Loosely Coupled Information System Architecture
3- Reviews
4- Continuous Business Analysis
5- CI/CD
6-Continuous Testing
7- KanBam
fast development technique based on lean methodology of a highly visible pull base workflow that manages and improves work across human systems
Kanban
fast development technique where testing is performed throughout the software development life cycle
Continuous Testing
fast development technique that are central concepts to Lean and Agile software deployment
CI/CD
fast development technique used for gathering information/feedback to decide direction of a product or service development process
Continual Business Analysis
fast development technique based on principle of progressing iteratively w/feedback to learn lessons, improve and correct, while not slowing down or adding to much control
Reviews
fast development technique that feature small, independently developed components
loosely coupled information system architecture
fast development technique that uses machine readable definition files for IT infrastructure and platforms
IAC- infrastructure as a code
Practices that contribute to achieving fast development (5)
1- Architecture Management
2- Business Analysis
3-Deployment Management
4-Service Validation and testing
5-Software development and management
Techniques for Valuable Investments (4)
1- Prioritization
2- Minimal Viable Product
3- Product or service ownership
4- A/B Testing
Valuable investment technique that demonstrates just enough features for an early assessment and feedback to pursue iterative and full development
Minimal Viable Product
Valuable investment technique required due to variable demand for services consideration such as cost delay and buy, sell, hold decisions
Prioritization
Valuable investment technique that relates to product owner
Product/Service Ownership
Valuable investment technique that helps decide which version of a feature is most valuable
A/B testing
Practices that support Valuable investment (2)
1- Portfolio Management
2- Relationship Management
7 Techniques for Resilient Operations
1- Technical Debt management
2- Chaos Engineering
3- Definition of Done
4- Version Control
5- AIOps
6-Chat Ops
7- Site Reliability Engineering
ITIL practices that support resilient operations include (6)
1- Availability Management
2- Capacity and Performance Management
3- Monitoring and Event Management
4- Problem Management
5- Service Continuity Management
6- Infrastructure and Platform Management
Resilient Operations technique that consists of checklist of agreed upon criteria for proposed product or service
Definition of Done
Resilient Operations technique that consists of administrative management of sources and artefacts of information systems, products and services
Version Control
Resilient Operations technique that applies machine learning to IT Operations to receive continuous insights which provide continuous fixes and improvements via automation
AIOps
Resilient Operations technique that connects people, tools, processes and automation in a transparent, flow, facilitating collaboration and control of pipelines
ChatOps
Resilient Operations technique that incorporates software engineering aspects and applies them to infrastructure and operations problem with the goal of creating scalable and reliable software systems
Site Reliability Engineering
Resilient Operations technique that is the discipline of experimenting on a system in order to build confidence in the system’s capability to withstand turbulent conditions in production
chaos engineering
Resilient Operations technique that consists of total backlog accumulated by choosing workarounds instead of system solutions that would take longer
Technical Debt Management
Four steps in chaos engineering
1- Define steady state (normal behavior)
2- Assume steady state will continue (hypothesize what will happen)
3-introduce variables that reflect real world events
4-Try to disprove the assumption (verify and learn)
Technique for Co-created value
Service experience
Co-created value technique that is a combination of technical output of a service and human perception of that service
Service Experience
Practices that help achieve Co-Created Value (3)
1- Relationship Management
2-Service Design
3- Service Desk
Assured Conformation techniques (3)
1- DevOps Audit Defense ToolKit
2- DevSecOps
3- Peer Review
Assured Conformation technique that consists of a set if tools, processes and best practices designed to help prepare and respond to DevOps related audits
DevOps Audit Defense ToolKit
Assured Conformation technique that integrates the security into daily work and uses/supports the concept of integration of duties
DevSecOps
Assured Conformation technique that uses/incorporates the judgement of profession work by others in the same field or profession
Peer Review
The purpose of this practice is to move changed of new hardware, software, documentation, processes and other component to live environments or to staging, testing development of other environments
Deployment Management
The capability of the service provider to continue service operation at acceptable predefined levels following a disaster event of disruptive incident
Service continuity
The purpose of this practice is to design products and services that are fit for purpose and use, and can be delivered by the organization and its ecosystem
Service Design
The purpose of this practice is to ensure new or change products and services meet requirements
Service Validation and Testing
Performed in earlier stages of the product and service lifecycle (ideation and design)
focused on confirming proposed service design meets agreed service requirements
Service Validation
Three phases of problem management
1-problem identification
2-Problem Control
3-Error Control
SuccessFactors for availability management practices (3)
1-Identifying service availability requirements
2- measure, assessing and reporting service availability (MTBF and MTRS)
3- Treating service availability risks
Practice SuccessFactors for Service Validation and Testing (2)
1- defining and agreeing on approaches to the validation and testing of the organization’s products, services and components in line w/the organization’s requirements for speed and quality of service changes
2- Ensuring that new and changed components, products and services meet agreed criteria
SuccessFactors for Deployment Management (2)
1- Establish and maintain effective deployment approaches for services and components
2-Ensure effective deployment in context of organization’s value streams
SuccessFactors for Software Development and Management (2)
1- Agree and improve organization’s approach to development and management of software development
2-Ensure software continuously meets organization’s requirements and quality throughout its lifecycle
Service Design success factors (2)
1- Establishing and organizational wide approach to service design
2- Ensuring that services are fit for purpose (utility) and fit for use (warranty) throughout their lifecycle
Practice success factors for architecture management (2)
1-Ensurning organization’s strategy us supported with a target architecture
2-Ensuring organization’s architecture is continually evolving to the target state
Practice success factors for Service Desk (2)
1-enabling and continually improving effective, efficient and convenient communication between provider and users
2-Enabling integration of user communications into value streams
Practice success factors for Problem Management (2)
1- identifying and understanding the problems and their impact on services
2- optimizing problem resolution and mitigation
Practice success factors for Monitoring and Event Management (3)
1- Establishing and maintaining approaches and models that describe various types of events and monitoring capabilities needed to detect them
2- Ensuring availability of timely, relevant, and sufficient monitoring data to everyone concerned
3- Ensuring events are detected, interpreted and acted on as quickly as possible as needed
Practice success factors for Relationship Management (3)
1- Establishing and continually improving an effective approach to relationship management practice across the organization
2- Ensuring effective and healthy relationship within the organization
3- Ensuring effective and healthy relationships between the organization and its external stakeholders
Practice success factors for Risk Management (3)
1- Establishing governance of risk management
2- Nurturing a risk management culture and identifying risks
3- Analyzing and evaluating risks
Practice success factors for Capacity and Performance Management (3)
1- identifying service capacity and performance requirements
2- measuring, assessing and reporting service performance and capacity
3- Treating service performance and capacity risks
Practice success factors for Information Security Management (4)
1- developing and managing information security management policies and plans
2- mitigating information security risks
3- Exercising and testing information security management plans
4- Embedding information security into all aspects of the SVS
Practice success factors for service continuity management (3)
1- developing and managing service continuity plans
2- mitigating service continuity risks
3- ensuring awareness and readiness
Practice success factors for Infrastructure and platform management (2)
1- establishing an infrastructure and platform management approach to meet evolving organizations needs
2- ensuring that infrastructure and platform solutions meet the organizations current and anticipated needs
Practice success factors for Portfolio Management (2)
1- Ensuring sound investment decisions for programs, projects, products and services within organization’s resource constraints
2-ensuiring continual monitoring, review and optimization of organization’s constraints
Six forms of loss as proposed by FAIR (factor analysis of information risks)
1- Productivity
2-Response
3-Replacement
4-SLA fines and regulatory judgments
5- Competitive Advantage
6- Reputation
The purpose of this practice is to ensure that services deliver agreed levels of availability to meet the need of customers and users
Availability Management
The purpose of this practice is to ensure that the availability and performance of a service are maintained at sufficient levels in case of a disaster
Service Continuity Managment
the ability of an IT service or other configuration item to perform its agreed function when required
Availability
