History: Business requirements change quickly while the technology is still under development. (Compared to the Waterfall software development model). Agile Manifesto (with 12 principles) in 2001.
Definition: move quickly and easily, think and understand quickly.
For user requirements and team progress for the sprint
Kanban board cards on differenct columns, e.g., Backlog, In Progress, Peer Review, In Test, Done, Blocked
3. Agile Backlog Refinement
Backlog Refinement (preparing for Sprint Planning): is a recurring event for agile teams. The process ensure that the next few sprints worth of user stories in the product backlog are prepared for sprint planning
The Product Backlog
Epic: Epics (both business and enabler) are the primary economic drivers for the program portfolio. Progress is measured as outcomes against the benefit hypothesis. Takes 9-12 months.
Feature: A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria. Takes less than 12 weeks.
Small functionality. Takes ~2 weeks. Breaks it down into tasks; a task should be completed by one person.
Ex: A a Marketing Lead (who), I want to hava a content management system (what) so that I can manage and provide quality content and experiences to my readers (why).
The Three C's: Card (who, what, why), Conversion, Confirmation.
Create alignment with Program Increment (PI) planning: SAFs uses "Cadence" and "Synchronization" to assist in combining the work of multiple teams into one.
1. What is Agile?
2. How does Agile Work? (Scrum/Kanban)
3. Agile Backlog Refinement
4. Scaling Agile