This document discusses different Agile frameworks including Scrum, Kanban, and a hybrid called Scrumban. It provides pros and cons for each approach. Scrum emphasizes control with small tasks and iterations while Kanban focuses on continuous flow without strict iterations. Scrumban combines elements of Scrum and Kanban for flexibility. The document also briefly outlines an onboarding squad process and development workflow.

1. Flavors of Agile
and what I know about them

2. Agile manifesto
Individuals and interactions
over processes and tools
Working software
over comprehensive documentation
Customer collaboration
over contract negotiation
Responding to change
over following a plan
Agilious Gelatus, circa 140 BCE

3. Agile criterias
Agility
Transparency
Done is Done
Iterative improvement

4. SCRUM
Tasks
Emphasises Control
Rigid iterations, assignments
Sync by meetings
Commitment
Roles

6. SCRUM pros
Controlled - tasks are small, short estimates
Predictable - velocity (capacity) is planned
Agile - can change between sprints
Verbose/transparent - commitment means
detailed reports
“Intense” - sprints can become little crunch
modes

7. Kanban
Stories are everything
Emphasises Flow
Design
WIP
Completion
No going back
Sync by Board

9. Kanban pros
Flexible - change priorities at any time
Simple - dirt simple process
Efficient - little overhead
Emergent velocity
Team focus
Multi-Kanban

10. Scrumban (Hybrid)
Emphasises transition
Meetings - events
Stories/Tasks (little kanbans)
Iterations, Commitment
No going back, flow within sprint
Team choice

11. Scrumban - pros
Controlled
Predictable
Transparent
Efficient
Team focus

12. Onboarding Squad process
Development workflow
Separate context workflows
Accumulated deployments
Selective roll-out

13. Bon appetite!