Agile is a way of working that focuses on taking small steps and making constant improvements. It values flexible planning and teamwork over following a rigid, unchangeable schedule.

Introduction to Agile

Scrum is a popular set of rules used within Agile to help teams organize their daily work. It provides a simple structure of roles, meetings, and lists to keep everyone on track.

The Scrum Framework

A Sprint is a short, fixed period of time, usually two to four weeks, where a team works to finish a specific set of tasks. This helps the team stay focused and deliver small results quickly.

Working in Sprints

This person represents the customer and decides what is most important to build first. They manage the master list of work to ensure the team is always creating the most value.

The Product Owner

Think of this person as a team coach who helps everyone follow the Scrum rules. They don't give orders, but they do help remove any obstacles that slow the team down.

The Scrum Master

This is the group of people who actually create the product, such as designers or builders. They are self-organized, meaning they decide together how to get their assigned work done.

The Development Team

This is a master To-Do list that contains every feature or fix needed for the entire project. The items are ranked so the most important work stays at the very top.

The Product Backlog

This is a smaller list of tasks chosen from the master list to be completed during the current work period. It serves as the team's specific plan for the next few weeks.

The Sprint Backlog

At the start of every work period, the team meets to discuss what they can realistically finish. They pick tasks from the master list and agree on a goal for the upcoming weeks.

Sprint Planning Meeting

This is a quick, 15-minute morning meeting where team members share what they did yesterday and what they plan to do today. It helps everyone see if anyone needs help.

The Daily Stand-up

At the end of a work period, the team shows their finished work to the customer or boss. This is a chance to get feedback and see if the project is moving in the right direction.

The Sprint Review

After the work is shown, the team meets privately to talk about how they worked together. They identify what went well and what they can do better in the next work period.

The Sprint Retrospective

These are simple descriptions of a feature told from the perspective of the person who will use it. They help the team understand exactly what the user needs and why.

Writing User Stories

This is a shared checklist of quality standards that every task must meet before it is considered finished. It ensures that everyone has the same idea of what 'finished' looks like.

Definition of Done

Instead of waiting months to finish the whole project, the team builds and releases small, working pieces regularly. This allows customers to start using part of the product much sooner.

Incremental Progress

Teams often use a board with columns like 'To Do,' 'Doing,' and 'Done' to track their work visually. This makes it easy for anyone to see the project's status at a glance.

Visual Progress Boards

Agile encourages talking directly to teammates and customers rather than relying only on long emails or documents. Simple, face-to-face conversations help prevent misunderstandings.

Clear Communication

In Agile, managers trust the people doing the work to make the best decisions on how to build the product. This empowerment often leads to more creative and faster results.

Trusting the Team

The team regularly stops to inspect their work and the way they are working. By looking at real evidence of what worked, they can adapt and improve their process over time.

What is a Retrospective?