Agile using Scrum Framework

Agile values prioritize individuals and interactions over processes and tools, working software over documentation, customer collaboration over contract negotiation, and responding to change over following a plan.

Explore agile principles that deliver valuable software continuously, welcome change, and promote frequent working software through daily collaboration. Embrace sustainable development, technical excellence, simplicity, and self-organized teams.

Trace the agile and scrum history from the 1995 paper by Jeff and Conjoint to the 2001 manifesto and the formation of the Scrum Alliance and the Scrum Guide.

Learn how the scrum pillars of transparency, inspection, and adaptation drive continuous improvement, and explore the five values: commitment, focus, openness, respect, and courage for effective delivery.

Explore the Scrum framework, including product backlog, sprint backlog, and daily scrums, and learn how a two to four week sprint yields an incremental, deliverable product.

Two to four week sprints, sometimes up to a month, cover design, coding, and testing; keep changes out of the sprint to minimize distractions, placing them in a later sprint.

Explore the scrum framework by examining the product owner, scrum, and development team roles. Learn the ceremonies—sprint planning, daily scrum, sprint review, and sprint retrospective—and the product and sprint backlogs.

The product owner defines the product's future, sets release dates and sprint content, serves as the voice of the client with stakeholders, iterates on value, and approves or rejects work.

The scrum master serves as a servant leader, shields the team from distractions, removes impediments, and trains the organization on scrum values to ensure smooth delivery of the product.

The development team consists of five to nine cross-functional, full-time members, including programmers, user experience designers, and database administrators. Teams are self-organized with no titles and shared responsibility.

Explore sprint planning as the first scrum ceremony, using capacity and the product backlog to define the sprint goal and sprint backlog through collaborative estimates by the team.

Hold a daily 15-minute scrum in the same place and time to discuss yesterday, today, and blockers; only the team attends, product owner may speak, not for problem solving.

The sprint review ceremony presents what the team accomplished in the sprint through a live demo, inviting stakeholders and clients to validate the product and capture feedback for future work.

Conduct a sprint retrospective with the scrum master, product owner, and team to identify what works and what to start or stop. Implement chosen actions in the next sprint.

Define the product backlog as the list of work that adds value. Prioritize top-value items with the product owner and backlog grooming to prepare them for the sprint backlog.

The sprint backlog lists sprint items from product backlog for the sprint, chosen by a self-organized team who sign up for work and update it daily as tasks are clarified.

Define the increment as the sprint output plus the previous sprint increment, serving as a concrete steppingstone toward the product goal, verified in the sprint review by the client.

Review scrum history, the scrum framework, ceremonies and artifacts, and references to the Najin manifesto and the Scrum Guide in this wrap-up of agile using scrum.