Methodologies - SCRUM - CCEA - SSD

What is SCRUM?

The SCRUM methodology is a way of managing projects that helps teams to work together.

How does SCRUM manage projects?

It involves taking a large project and breaking it into small, manageable parts which are allocated to appropriate members of the team.

How is progress tracked in SCRUM?

The progress is checked regularly.

What are the main roles in SCRUM?

Product Owner, Scrum Master, and Development Team.

What does the Product Owner do?

-Decides what the project is/what needs built.
-They prioritise work and define user requirements
-represent the stakeholders in the design of the system.

What does the Scrum Master do?

-Helps the team follow the process and removes obstacles.
-They ensure that the team follows the SCRUM process
-facilitate teamwork.

What does the Development Team do?

Builds the solution.

What is a Sprint?

A work cycle in which a small part of the project is completed.

How long is a typical Sprint?

Generally 1-4 weeks long.

What happens at the end of a Sprint?

The team reviews work to date and plans the next steps.

Why are Sprints useful?

They allow for continuous improvements, adaptability, and keep the team focused.

What are the key meetings in SCRUM?

Daily Stand-ups, Sprint Review, and Sprint Retrospective.

What happens in Daily Stand-ups?

Quick meeting to discuss progress and problems.

What happens in a Sprint Review?

Demonstrating what has been done at the end of each sprint.

What happens in a Sprint Retrospective?

Discussion on what has gone well and what needs improvement.

What are the 4 advantages of SCRUM?

-Faster progress and continuous feedback.
-Teams can quickly adapt to changes.
-Encourages teamwork and communication.
-Problems can be solved early.

What are the 4 disadvantages of SCRUM?

-Requires experience to be well implemented.
-Can be chaotic if not properly managed by the Scrum Master.
-Works best with small, dedicated teams.
-Too many meetings can slow progress.

When to use SCRUM?

-When working on a complex problem with changing requirements.
-When collaboration and updates are required.
-When the project requires continuous improvements or adaptations.

When NOT to use SCRUM?

-When a project has fixed requirements.
-When the team is inexperienced with SCRUM.
-When strict deadlines must be met with no flexibility.