1. automate & integrate the processes
1.1. software development
1.2. IT teams
2. Agile
2.1. Kanban Method
2.1.1. Reports
2.1.1.1. control charts
2.1.1.1.1. shows the cycle time for each issue as well as a rolling average for the team
2.1.1.2. cumulative flow diagram
2.1.1.2.1. spot blockages
2.1.2. Benefits
2.1.2.1. Planning flexibility
2.1.2.1.1. only focused on the work that's actively in progress
2.1.2.1.2. The product owner is free to reprioritize work in the backlo
2.1.2.2. Shortened time cycles
2.1.2.2.1. Overlapping skill sets
2.1.2.3. Fewer bottlenecks
2.1.2.3.1. limit the amount of work in progress (WIP)
2.1.2.4. Visual metrics
2.1.2.4.1. reports
2.1.3. Process
2.1.3.1. Key metrics
2.1.3.1.1. Cycle time
2.1.4. Jira
2.1.5. Board
2.1.5.1. Visual signals
2.1.5.1.1. Kanban cards
2.1.5.2. columns
2.1.5.2.1. workflow
2.1.5.3. work-in-progress limits (WIP limits)
2.1.5.3.1. critical for exposing bottlenecks in the workflow
2.1.5.3.2. maximizing flow
2.1.5.4. a commitment point
2.1.5.4.1. backlog
2.1.5.5. a delivery point
2.1.5.5.1. he end of a kanban team’s workflow
2.1.5.5.2. team’s goal is to take cards from the commitment point to the delivery point as fast as possible
2.2. Scrum Method
2.2.1. relative
2.2.1.1. original scrum (compexoty of the tasks)
2.2.1.2. the least complexity: 1 stpry point, max 8 points
2.2.2. merge (story point-4 hrs)
2.2.2.1. 1 sprint: 20 points
2.2.2.2. if they are in the same estimate: true estimate, if not there is different in fali estimate
2.2.3. definition
2.2.3.1. empiricism
2.2.3.1.1. knowledge comes from experience
2.2.3.1.2. decisions are made based on what is observed
2.2.3.2. lean thinking
2.2.3.2.1. reduces waste
2.2.3.2.2. focuses on essentials
2.2.4. framework
2.2.4.1. characteristic
2.2.4.1.1. heuristic
2.2.4.2. definition
2.2.4.2.1. a set of values, principles, and practices
2.2.5. scrum team
2.2.5.1. product owner
2.2.5.1.1. definition
2.2.5.1.2. roles
2.2.5.2. scrum master
2.2.5.2.1. definition
2.2.5.2.2. roles
2.2.5.3. development team
2.2.5.3.1. testers
2.2.5.3.2. designers
2.2.5.3.3. UX specialists
2.2.5.3.4. ops engineers
2.2.6. Scrum artifacts
2.2.6.1. Product Backlog
2.2.6.1.1. the primary list of work that needs to get done
2.2.6.1.2. constantly revisited, re-prioritized
2.2.6.2. Sprint Backlog
2.2.6.2.1. implementation in the current sprint cycle
2.2.6.3. Increment (or Sprint Goal)
2.2.6.3.1. the usable end-product from a sprint
2.2.6.3.2. definition of “Done”
2.2.7. Scrum ceremonies or events
2.2.7.1. Organize the backlog
2.2.7.2. Sprint planning
2.2.7.2.1. an event in scrum that kicks off the sprint
2.2.7.2.2. process
2.2.7.3. Sprint
2.2.7.3.1. a short, time-boxed period when a scrum team works to complete a set amount of work
2.2.7.4. Daily scrum or stand up
2.2.7.5. Sprint review
2.2.7.6. Sprint retrospective
2.2.8. Values
2.2.8.1. Commitment
2.2.8.2. Courage
2.2.8.3. Focus
2.2.8.4. Openness
2.2.8.5. Respect
3. Continuous Delivery
4. Microservices
5. Infinity Loop (Constant Collaboration & Iterative Improv.)
6. DevOps
6.1. Overview
6.1.1. Definition
6.1.1.1. a set of
6.1.1.1.1. Practice
6.1.1.1.2. Tools
6.1.1.1.3. Culture philosophy
6.1.2. How does it work
6.1.2.1. DevOps team
6.1.2.1.1. developers
6.1.2.1.2. IT operations
6.1.2.2. DevOps Model
6.1.2.2.1. Collaboration
6.1.2.2.2. Speed & Quality
6.1.2.2.3. Cultural Shift
6.1.2.2.4. Collaboration
6.1.2.3. DevOps Toolchain
6.1.2.3.1. Automation
6.1.2.3.2. Continuous Integration
6.1.2.3.3. Continuous Delivery
6.1.2.3.4. Collaboration
6.1.3. The DevOps lifecycle
6.1.3.1. Development
6.1.3.1.1. Discover
6.1.3.1.2. Plan
6.1.3.1.3. Build
6.1.3.1.4. Test
6.1.3.2. Operations
6.1.3.2.1. Deploy
6.1.3.2.2. Operate
6.1.3.2.3. Observe
6.1.3.2.4. Continuous feedback
6.1.4. Benefits
6.1.4.1. Speed
6.1.4.2. Improved collaboration
6.1.4.3. Rapid deployment
6.1.4.4. Quality and reliability
6.1.4.5. Security
6.1.5. DevOps practices
6.1.5.1. Continuous integration
6.1.5.2. Continuous delivery
6.1.5.3. Situational awareness
6.1.5.4. Automation
6.1.5.5. Infrastructure as Code
6.1.5.6. Microservices
6.1.5.7. Monitoring
7. working collaboratively throughout the product lifecycle
7.1. increase the speed and quality of software deployment
8. Goals
8.1. increase value to customers
8.2. improve their processes
9. CI/CD pipeline
10. Overview
10.1. software development lifecycle
10.1.1. Discover
10.1.1.1. Projects are envisioned, designed, and prioritized
10.1.1.1.1. Agile Method
10.1.2. Plan
10.1.2.1. Stakeholders are identified
10.1.2.2. budgets set
10.1.2.3. infrastructure requisitioned
10.1.3. Build and Test
10.1.3.1. build production-ready software
10.1.3.1.1. meets requirements and feedback
10.1.4. Deploy
10.1.5. Operate
10.1.5.1. Support
10.1.5.2. Maintenance
10.1.6. Observe
10.2. Practice throughout lifecircle
10.2.1. Continuous feedback
10.2.1.1. evaluate each release and generate reports to improve future releases
10.2.1.2. ask for customers to give input about the value and impact of product feature
10.2.1.3. share business-related outcomes with stakeholders
10.2.2. Security
10.2.2.1. testing should be included throughout the software development lifecycle
10.2.2.1.1. minimize bugs in software code
10.3. Key features
10.3.1. Agile
10.3.2. DevOps
10.3.3. Continuous integration and delivery (CI/CD)
10.3.4. Microservices