Professional Documents
Culture Documents
Scrum
Scrum
It is often used in
software development but can be applied to various fields where complex projects need to be
managed. Scrum provides a structured yet flexible approach to deliver high-value products
iteratively.
1. **Roles:**
- **Product Owner:** Represents the stakeholders and is responsible for defining and prioritizing
the product backlog.
- **Scrum Master:** Facilitates the Scrum process, removes impediments, and ensures that the
team adheres to Scrum practices.
2. **Artifacts:**
- **Product Backlog:** A prioritized list of features, enhancements, and bug fixes that need to be
addressed in the product.
- **Sprint Backlog:** A subset of the product backlog items selected for a specific sprint, along
with a plan for delivering the product increment.
- **Increment:** The sum of all the product backlog items completed during a sprint, representing
a potentially shippable product.
3. **Events:**
- **Sprint:** A time-boxed period (usually 2-4 weeks) during which a potentially releasable product
increment is created.
- **Sprint Planning:** A meeting at the beginning of each sprint where the team plans the work to
be done.
- **Daily Scrum:** A daily stand-up meeting where team members share progress, discuss
challenges, and plan the day's work.
- **Sprint Review:** A meeting at the end of each sprint where the team demonstrates the
product increment and receives feedback.
- **Sprint Retrospective:** A meeting at the end of each sprint where the team reflects on their
performance and identifies areas for improvement.
Scrum emphasizes collaboration, adaptability, and continuous improvement. It aims to deliver a
valuable product increment at the end of each sprint, allowing for frequent feedback and
adjustments. The framework is designed to be lightweight and easy to understand, promoting a
more responsive and customer-centric approach to project management.