Common Scrum Terminologies Every Beginner Must Know
Common Scrum Terminologies Every Beginner Must Know
1. Scrum
A lightweight Agile framework used for developing, delivering, and sustaining complex products. It emphasizes collaboration, iterative progress, and continuous improvement.
2. Scrum Team
A small, cross-functional team consisting of:
Product Owner
Scrum Master
Developers
3. Product Owner (PO)
The person responsible for maximizing the value of the product and managing the Product Backlog. They represent the voice of the customer.
4. Scrum Master
The facilitator of the team who ensures Scrum is understood and followed. They help remove obstacles and support the team’s effectiveness.
5. Developers
Team members who do the work of delivering a potentially releasable Increment of product at the end of each Sprint. They are self-organizing and cross-functional.
6. Sprint
A time-boxed iteration (usually 1–4 weeks) during which a usable product increment is created. All work in Scrum happens within sprints.
7. Sprint Planning
A meeting held at the beginning of each Sprint where the team decides:
What can be delivered (Sprint Goal)
How the work will be accomplished
8. Sprint Goal
A single objective for the Sprint. It gives the team focus and purpose throughout the iteration.
9. Daily Scrum (Stand-up)
A 15-minute daily meeting for the developers to inspect progress and adapt their plan for the next 24 hours.
10. Sprint Review
A meeting held at the end of the Sprint to demonstrate the product increment to stakeholders and collect feedback.
11. Sprint Retrospective
A team reflection meeting held after the Sprint Review to discuss:
What went well
What didn’t go well
How to improve in the next Sprint
12. Product Backlog
An ordered list of everything that is known to be needed in the product. Managed by the Product Owner.
13. Sprint Backlog
The set of Product Backlog items selected for the Sprint, plus a plan for delivering them.
14. Increment
The sum of all Product Backlog items completed during a Sprint and the value of the increments from all previous Sprints. It must be in a usable condition.
15. Definition of Done (DoD)
A shared understanding of what it means for work to be complete. Ensures transparency and consistency.
16. User Story
A simple way to describe a feature from an end-user perspective. Often follows this format:
As a [user], I want [feature] so that [benefit].
17. Velocity
The amount of work a team can complete in a Sprint, often measured in story points or completed backlog items.
18. Burndown Chart
A visual representation of remaining work vs. time in a Sprint. Helps track progress.
19. Impediment
Any obstacle that slows down or blocks the team’s progress. The Scrum Master is responsible for helping remove these.
20. Time-box
A fixed duration for an activity. Scrum uses time-boxing for all events (e.g., Sprints, daily stand-ups, planning).
Learn Scrum Master Training in Hyderabad
Read More
Roles in Scrum: Scrum Master, Product Owner, Developers
Introduction to Scrum Ceremonies
How to Create an Effective Product Backlog
Visit Our Quality Thought Training in Hyderabad
Comments
Post a Comment