Common Scrum Terminologies Every Beginner Must Know
π Basic Scrum Terminologies
1. Scrum
A lightweight Agile framework used to manage and develop complex products, typically in software development.
2. Agile
A project management philosophy that values flexibility, customer collaboration, and iterative progress.
π₯ Scrum Roles
3. Product Owner
Responsible for defining the product vision, managing the Product Backlog, and ensuring the team delivers value to the customer.
4. Scrum Master
Acts as a facilitator who helps the team follow Scrum principles, removes blockers, and improves team dynamics.
5. Development Team
A cross-functional group of professionals (developers, testers, designers, etc.) who build the product.
π Scrum Events (Ceremonies)
6. Sprint
A time-boxed iteration (usually 1–4 weeks) during which a usable product increment is developed.
7. Sprint Planning
A meeting at the start of each sprint where the team plans the work to be done.
8. Daily Scrum (Stand-up)
A 15-minute daily meeting for the team to sync up on progress and highlight any blockers.
9. Sprint Review
A meeting held at the end of the sprint to demonstrate what was built and gather feedback.
10. Sprint Retrospective
A meeting to reflect on the sprint and discuss improvements for the next one.
π Scrum Artifacts
11. Product Backlog
A prioritized list of all the work that needs to be done for the product. Managed by the Product Owner.
12. Sprint Backlog
A list of tasks and user stories selected from the Product Backlog for the current sprint.
13. Increment
The working product that results from a sprint. It must be potentially shippable.
π§© Other Useful Terms
14. User Story
A simple description of a product feature from the end-user’s perspective. Example: "As a user, I want to reset my password so that I can recover my account."
15. Definition of Done (DoD)
A clear checklist of what needs to be completed for a backlog item to be considered "done."
16. Burndown Chart
A graph that shows remaining work over time in a sprint, helping track progress.
17. Velocity
The amount of work a team completes during a sprint, used to predict future performance.
18. Epic
A large user story that can be broken down into smaller stories.
19. Impediment
Anything that blocks team progress. Scrum Masters are responsible for removing these.
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 IHUB Talent Training in Hyderabad
Comments
Post a Comment