SCRUM
Scrum is by far the most popular Agile methodology. Developed in the early 1990s by Ken Schwaber and Jeff Sutherland, Scrum emphasizes time-boxed iterations called “sprints,” typically lasting 1–4 weeks, during which teams deliver potentially shippable product increments.
Key Components of Scrum:
Roles: Scrum defines three core roles—Product Owner (defines requirements), Scrum Master (facilitates the process), and Development Team (executes the work).
Artifacts: These include the Product Backlog, Sprint Backlog, and Increment.
Ceremonies: Sprint Planning, Daily Standup, Sprint Review, and Sprint Retrospective are central to Scrum’s rhythm.
Why Scrum Works:
1. Encourages regular stakeholder feedback. 2. Promotes accountability and transparency. 3. Fosters team empowerment and continuous improvement
Use Cases: Scrum is ideal for complex software projects, startups, and teams needing structured, iterative development with regular check-ins.
Challenges:
-Requires commitment to regular meetings and processes
-Not suitable for projects without clear deliverables
-Can become rigid if misapplied