4. Agile vs. DevOps
4.1. Agile, Scrum, Lean, XP...

Figure 4.1. Agility is achieved only by combining Business Practices and Technical Craftsmanship. Agile is not only about Scrum.

Figure 4.2. Agility is achieved only by combining Business Practices and Technical Craftsmanship. Agile is not only about Scrum.
Agile można rozumieć jako sześć spójnych i łączących się dyscyplin:
miękkie:
zarządzanie projektami,
biznes i produkty,
komunikacja i organizacja,
techniczne:
devops,
architektura IT,
jakość i praktyki.
4.2. Spotify Engineering Culture @youtube.com

Figure 4.3. Spotify Engineering Culture @youtube.com
4.3. Agile
[]
What is Agile?
History
Agile Manifesto
Be Agile
That’s so wrong on so many levels
4.4. Lean Startup
Build
Measure
Learn
4.5. Scrum
[]
What is Scrum?
History
Introduction:
Iterative approach
What’s sprint?
Short sprints
Roles:
Scrum Master
Product Owner
Developer
Managers?
Flat structure?
Bubble organization chart
Heroes
Cross-functional team
Issues:
User Stories
Epics
Technical Tasks
Artifacts:
Backlog
Sprintlog
Task board
Units
Story Points
Business Value
Metrics:
Velocity
Capacity
Maturity
Meetings:
Daily Meeting
Planning
Retrospective
Refinement
Review
Planning and Refinement:
Estimation
How big your tasks should be?
Estimation support systems
Sprint goal
Acceptance Criteria
Definition of Done
Sprint Review:
Product Owners role
Stakeholders
Releasable functionality
Sprint Impediments
Charts:
Burn-down Chart
Burn-up Chart
Control Chart
Cumulative Flow Diagram
Epic Report
Sprint Report
Velocity Chart
Version Report
Team Interaction:
Transparency
Retrospective
Management role and team
Scrum, but...
Scrum, and...
Most common mistakes while Scrum implementation
4.5.1. Refinement Simulation
Backlog decomposition
Iterating decomposition
Small, Medium, Large
Must, Should, Could
Sprint
- Introduction to sticky cards backlog note format
header: Priority, Sprint, Estimate, Epic
capital, technical letters
acceptance criteria
Solving disagreement on issue estimation
three columns estimation (Small, Medium, Large)
ballancing sprint capacity
managing hard dependencies (issue is blocked by)
managing soft dependencies (issue relates to other - logically should be done before, but it is not necessary)
4.6. Kanban
What’s Kanban?
History
Introduction:
Pull system
JIT
Context switching
Kanban Board
Improvement:
Muda
Jidoka
Kaizen
Bottlenecks
Metrics
Lean
Workflow:
Columns
Swimlanes
Expedite
Priority
SLA
4.7. Extreme Programming
What is Extreme Programming?
History
Practices:
Test Driven Development (TDD)
Behavior Driven Development (BDD)
Pair Programming
Quality:
Best Practices
Coding Standards
Clean Code
Code Review
Pull Requests