01 - Planning for DevOps Flashcards
DevOps professionals
Combine people, process and technologies to continuously deliver valuable products and services that meet end user needs and business objectives
Challenges when creating teams
Availability of staff
Disruption of current procedures and processes
How to overcome team challenges
Create team that is:
- Focus on transformation
- Well-respected in subject area
- Internal and external to the business
Give example of clearly-defined set of measurable outcomes
Reduce time spent on bug fix by 60%
Reduce time spent on unplanned work by 70%
Advantage of shorter timelines
Easier to change plans or priorities when necessary
Reduced delay between doing the work and getting feedback
Easier to keep organizational support when positive outcomes are apparent
Waterfall approach
Define, analyze, build and test, and deliver
Hard to accurately define requirements, which can change over time, including during development
Requires change requests and additional cost after delivery
Agile approach
Emphasizes constantly adaptive planning, and early delivery with continual improvement
Development methods are based on releases and iterations
At end of each iteration, should have tested working code
Is focused on shorter-term outcomes
Monolithic
Cake
Microservices
Cupcake
Principles of Agile development
12 principles
Greenfield software protect
Software projects develop in a totally new environment
Brownfield software project
Software projects develop in the immediate presence of existing software applications/systems
System of Record
Emphasize accuracy and security
Provide truth about data elements
Historically evolve slowly and carefully
System of Engagement
More exploratory
Use experimentation to solve new problems
Modified regularly
Prioritize making changes quickly over ensuring that the changes are correct
Different type of staff members
Canaries - voluntarily test bleeding edge features
Early adopters - voluntarily preview releases
Users - consume the products after canaries and early adopters
Ideal target improvements
Used to gain early wins
Small enough to be achievable in a reasonable time-frame
Have benefits that are significant enough to be obvious to the organization
Identify project metrics and KPIs
Faster outcomes
Efficiency
Quality and Security
Culture
Horizontal Teams
Divide teams according to the software architecture
Vertical Teams
Span the architecture and are aligned with product outcomes, and scaling can occur by adding teams
Ideal DevOps team members
Think there is a need to change and have shown an ability to innovate
Well respected and have broad knowledge of organization and how it operates
Ideally, already believe that DevOps practices are what is needed
Cultural changes
fill in
Cross-functional teams
fill in
Collaboration tooling
fill in
Azure DevOps
Azure Boards
Azure Pipelines
Azure Repos
Azure Artifacts
Azure Test Plans
What Can GitHub do
Codespaces
Repos
Actions
Artifacts
Security
Azure DevOps
Work management tool
GitHub
Work management tool
Azure Test Plans
Track sprints and milestones
Apache JMeter
open-source software written in Java and designed to load test functional behavior and measure performance
Pester
Tool to automate testing of PowerShell
