Values, Sprints & Scrum Ceremonies

Agile Is a Philosophy, Not a Framework

The Agile Manifesto states preferences (X over Y, not X-only): individuals and interactions over processes and tools; working software over comprehensive documentation; customer collaboration over contract negotiation; responding to change over following a plan. Scrum and Kanban are specific frameworks implementing these values — Agile itself prescribes no fixed process.

Sprints & Why Iterate

A fixed, time-boxed period (often 1-4 weeks) delivering a working increment by its end. Smaller, frequent increments surface misunderstandings while the cost of correcting them is still low — a large, single, all-at-once effort risks discovering a fundamental misdirection only after most work is already done.

Scrum Ceremonies

Daily standup — brief, ~15min sync (what I did, what's next, blockers), not deep problem-solving. Sprint review — demo working software to stakeholders, gather PRODUCT feedback. Retrospective — reflect on the team's own PROCESS, what to improve next sprint. Review and retro are distinct: one looks outward at the product, the other looks inward at how the team worked.

Roles: Product Owner vs. Scrum Master

Product Owner: owns WHAT to build — prioritizes the backlog based on business value. Scrum Master: facilitates the process — removes impediments, coaches Scrum practices — not a command-and-control project manager assigning individual tasks.