High Velocity Flashcards by Clifton Hinnant

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- Kanban

How well did you know this?

Not at all

Perfectly

Fast development technique based on lean methodology of a highly visible pull base workflow that manages and improves work across human systems.

Kanban

How well did you know this?

Not at all

Perfectly

Fast development technique where testing is performed throughout the software development life cycle.

Continuous Testing

How well did you know this?

Not at all

Perfectly

Fast development technique that are central concepts to Lean and Agile software deployment.

CI/CD

How well did you know this?

Not at all

Perfectly

Fast development technique used for gathering information/feedback to decide direction of a product or service development process.

Continuous Business Analysis

How well did you know this?

Not at all

Perfectly

Fast development technique based on principle of progressing iteratively w/feedback to learn lessons, improve and correct, while not slowing down or adding too much control.

Reviews

How well did you know this?

Not at all

Perfectly

Fast development technique that feature small, independently developed components.

Loosely Coupled Information System Architecture

How well did you know this?

Not at all

Perfectly

Fast development technique that uses machine readable definition files for IT infrastructure and platforms.

IAC

How well did you know this?

Not at all

Perfectly

What are 5 practices that contribute to achieving fast development

1- Architecture Management
2- Business Analysis
3- Deployment Management
4- Service Validation and Testing
5- Software Development and Management

How well did you know this?

Not at all

Perfectly

What are 4 techniques for Valuable Investments

1- Prioritization
2- Minimal Viable Product
3- Product or Service Ownership
4- A/B Testing

How well did you know this?

Not at all

Perfectly

Valuable investment technique that demonstrates just enough features for an early assessment and feedback to pursue iterative and full development.

Minimal Viable Product

How well did you know this?

Not at all

Perfectly

Valuable investment technique required due to variable demand for services consideration such as cost delay and buy, sell, hold decisions.

Prioritization

How well did you know this?

Not at all

Perfectly

Valuable investment technique that relates to product owner.

Product/Service Ownership

How well did you know this?

Not at all

Perfectly

Valuable investment technique that helps decide which version of a feature is most valuable.

A/B Testing

How well did you know this?

Not at all

Perfectly

practices that support Valuable Investment

1- Portfolio Management
2- Relationship Management

How well did you know this?

Not at all

Perfectly

7 techniques for Resilient Operations

1- Technical Debt Management
2- Chaos Engineering
3- Definition of Done
4- Version Control
5- AIOps
6- ChatOps
7- Site Reliability Engineering

How well did you know this?

Not at all

Perfectly

6 ITIL practices that support resilient operations

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

How well did you know this?

Not at all

Perfectly

Resilient Operations technique that consists of checklist of agreed upon criteria for proposed product or service.

Definition of Done

How well did you know this?

Not at all

Perfectly

Resilient Operations technique that consists of administrative management of sources and artefacts of information systems, products and services.

Version Control

How well did you know this?

Not at all

Perfectly

Resilient Operations technique that applies machine learning to IT Operations to receive continuous insights which provide continuous fixes and improvements via automation.

AIOps

How well did you know this?

Not at all

Perfectly

Resilient Operations technique that connects people, tools, processes and automation in a transparent flow, facilitating collaboration and control of pipelines.

ChatOps

How well did you know this?

Not at all

Perfectly

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

How well did you know this?

Not at all

Perfectly

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

How well did you know this?

Not at all

Perfectly

Resilient Operations technique that consists of total backlog accumulated by choosing workarounds instead of system solutions that would take longer.

Technical Debt Management

How well did you know this?

Not at all

Perfectly

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 that is a combination of technical output of a service and human perception of that service.

Service Experience

3 practices that help achieve Co-Created Value

1- Relationship Management 2- Service Design 3- Service Desk

Assured Conformation techniques

1- DevOps Audit Defense ToolKit 2- DevSecOps 3- Peer Review

Assured Conformation technique that consists of a set of 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 professional work by others in the same field or profession.

Peer Review

The purpose of this practice is to move changed or new hardware, software, documentation, processes and other components 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 or 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 changed 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

3 SuccessFactors for Availability Management practices

1- Identifying service availability requirements 2- Measure, assessing and reporting service availability (MTBF and MTRS) 3- Treating service availability risks

2 Practice SuccessFactors for Service Validation and Testing

1- Defining and agreeing on approaches to the validation and testing of the organization's products, services and components in line with the organization's requirements for speed and quality of service changes 2- Ensuring that new and changed components, products and services meet agreed criteria

2 SuccessFactors for Deployment Management

1- Establish and maintain effective deployment approaches for services and components 2- Ensure effective deployment in context of organization's value streams

2 SuccessFactors for Software Development and Management

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

2 Service Design success factors

1- Establishing an organizational wide approach to service design 2- Ensuring that services are fit for purpose (utility) and fit for use (warranty) throughout their lifecycle

2 Practice success factors for Architecture Management

1- Ensuring organization's strategy is supported with a target architecture 2- Ensuring organization's architecture is continually evolving to the target state

2 Practice success factors for Service Desk

1- Enabling and continually improving effective, efficient and convenient communication between provider and users 2- Enabling integration of user communications into value streams

2 Practice success factors for Problem Management

1- Identifying and understanding the problems and their impact on services 2- Optimizing problem resolution and mitigation

3 Practice success factors for Monitoring and Event Management

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

3 Practice success factors for Relationship Management

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

3 Practice success factors for Risk Management

1- Establishing governance of risk management 2- Nurturing a risk management culture and identifying risks 3- Analyzing and evaluating risks

3 Practice success factors for Capacity and Performance Management

1- Identifying service capacity and performance requirements 2- Measuring, assessing and reporting service performance and capacity 3- Treating service performance and capacity risks

4 Practice success factors for Information Security Management

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

3 Practice success factors for Service Continuity Management

1- Developing and managing service continuity plans 2- Mitigating service continuity risks 3- Ensuring awareness and readiness

2 Practice success factors for Infrastructure and Platform Management

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

2 Practice success factors for Portfolio Management

1- Ensuring sound investment decisions for programs, projects, products and services within organization's resource constraints 2- Ensuring continual monitoring, review and optimization of organization's constraints

Six forms of loss as proposed by FAIR

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 Management

The ability of an IT service or other configuration item to perform its agreed function when required.

Availability

The purpose of this practice is to ensure the organization has the right mix of programs, projects, products and services to execute its strategy within funding constraints

Portfolio Managment

The purpose of this practice is to reduce the likelihood and impact of incidents by identifying actual and potential causes of incidents and managing workarounds and known errors

Problem Management

The purpose of this practice is to systematically observe services and service components, and record and report selected changes of state identified as events

Monitoring and Event Management

The purpose of this practice is to manage communications for service requests and incidents and capture their demand. It is also the entry point and single point of contact with all users

Service Desk Practice

The purpose of this practice is to ensure that software development aligns with business needs, delivering high-quality software products in a cost-effective and efficient manner. This practice encompasses the entire software development lifecycle, from planning and design to deployment and maintenance.

Software Development and Management

The purpose of this practice is to establish and nurture the links between the organization and its stakeholders at strategic and tactical levels

Relationship Management

The purpose of this practice is to explain different elements that form an organization. Explains how elements are interrelated to enable organizations to achieve its objectives

Architecture Management

The purpose of this practice is to analyze part or entirety of the business, define its needs and recommend solutions to address those needs or solve a problem

Business Analysis Practice

The purpose of this practice is to protect information needed by the organization to conduct its business

Information Security Management

The purpose of this practice is to ensure the organization understands and effectively handle risk

Risk Management

The purpose of this practice is to oversee the infrastructure and platforms used by an organization to

Infrastructure and platform management

The purpose of this practice is to ensure that service achieve the agreed and expected levels of performance and satisfy current and future demand in a cost-effective manner

Capacity and Performance Management

HVIT objective described as effective interaction between service provides and service consumers

Co-created Value

Closely related service value chain activities for Co-created value objective

Engage, deliver and support, improve

HVIT approach that improves throughput and reduces waste

Lean

HVIT objective achieved through DevSecOps, SRE and Rugged Software Development

Resilience

HVIT approach that adds close and iterative collaboration with others

Agile

systems that are dynamic and can change or adapt in response to the behavior of the agents within them. The boundaries and rules within such systems are not rigid but are influenced and modified by the interactions and decisions of the agents (such as individuals, organizations, or components) operating within the system.

Complex Adaptive Systems

A mental model of economic exchange in which stake holders co-create value by applying their competencies and other resources

Service Dominance Logic

5 Steps of Digital Product Lifecycle

1. Exploration 2. Onboarding 3. Co-Creating value 4. offboarding 5. Retiring

A mental model and behavior pattern for scientific thinking and routines for practice and coaching

Toyota Kata

5 Key Behaviors of High Velocity

1- Accept Ambiguity 2-Trust and be trusted 3- Continually raise the bar 4- Help get the customer's job done 5- Commit to continual learning

when a back log item is ready to be worked on

definition of ready

a percentage and meant time between failures and mean time to restore. difficult to measure and usually unreliable

Availability

number of breaches, maturity of control monitoring, ability to analyze logs to identify risks as breaches, etc.

security

time to load a webpage, to execute a date query or complete batch process, etc

performance

Agile acronym used a definition for ready: INVEST

Independent: The user story should be self-contained. Negotiable: User stories are not fixed contracts; they can be discussed and changed. Valuable: The user story must deliver value to the end user. Estimable: The user story should be able to be estimated in terms of effort. Small: The user story should be small enough to be completed within a single iteration . Testable: The user story must have clear acceptance criteria to be testable.

Continuous Techniques (5)

1- small frequent batches 2- Continuous Integration 3 - Continuous delivery 4- Continuous deployment 5- Great collaboration and automation

Lean techniques (3)

1- Break large pieces into smaller items 2-Reduce WIP to improve throughput 3- Theory of constraints (identify weakest link, reduce load on it, organize around it

Resilient Techniques (4)

1- SRE 2- Rugged Software Development 3- DevSecOps 4-Proactive monitoring

Agile Techniques (3)

1- working software is delivered in frequent increments 2-information/feedback is gathered quickly 3- decision are delayed as long as possible

The cognitive and practical process by which design concepts are developed

Design Thinking

a climate in which people are comfortable being (and expressing themselves)

Safety Culture

work environment where trust, respect, curiosity, inquiry, playfulness and intensity all coexist in a plasma of learning and discovery

Lean Culture

System of principles which define what is good for individuals and society

Ethics

Closely related service value chain activities for Fast Development objective

Engage, Design and Transition, Obtain Build, Improve

Closely related service value chain activities for valuable investments

Engage, Plan, Improve

Closely related service value chain activities for Assured conformance

All value chain activities

Closely related service value chain activities of Resilient Operations

Engage, deliver and support, improve

objective involves identifying and justifying digital investments that would contribute significantly to business strategy.

Valuable Investments

objective involves realizing new and improved digital products and services frequently, quickly, and reliably.

Fast Development

objective involves ensuring that digital products are available for use whenever needed.

Resilient Operations

A tool that tests the resilience of IT systems by intentionally disabling components in production to test how remaining systems respond to the outage

Chaos Monkey

objective involves co-creating value from digital products through the close collaboration of the service provider and the service consumer.

Co-Created Value

objective involves ensuring that service provision and service consumption comply with corporate and regulatory directives with respect to governance, risk, and compliance

Assured Conformance

Having a task that is prone to fraud or error performed by one person because other controls have been applied.

Integration of Duties