Agile, Scrum and Kanban
With the ordering app, stores don't know exactly what they want until they try it. This is where agile helps: instead of delivering everything after 6 months, you deliver a working version every two weeks and adjust to user feedback. Its best-known framework is Scrum:
| In Scrum | Responsibility | |
|---|---|---|
| Roles | Product Owner | Orders the backlog by value; the customer's voice in the team. |
| Scrum Master | Shields the team, removes blockers and keeps Scrum on track. Not a boss. | |
| Developers | The people who build and test, and decide how to do the work. | |
| Events | Sprint | A fixed cycle (often two weeks) ending in a working increment. |
| Sprint Planning · Daily Scrum | Planning at the start, and a 15-minute daily sync. | |
| Review · Retrospective | Show the increment to stakeholders, then the team reviews how it works. | |
| Artifacts | Product Backlog · Sprint Backlog · Increment | All requirements in order, the sprint's selection, and the working increment. |
Requirements are written as user stories (from the systems analysis track), and the team sizes each in story points rather than days. After a few sprints you know the team's velocity: points finished per sprint. From that you forecast when the rest will be done.
Kanban is simpler: a board with columns (to do → in progress → done) and a cap on items in progress (a WIP limit). The idea: “stop starting, start finishing”. Great for support and maintenance teams.