Summary -

In this topic, we described about the Scrum Terminologies in detail.

The most popular scrum terminologies in Agile methodology are specified below -

Scrum Terminologies
  1. Burn down chart - Burn down chart is the chart which would project the amount of work which would be remaining in the product backlog. Time would be represented on the horizontal axis and remaining work on the vertical axis. Work that is remaining would be communicated by using a burn down chart.
  2. Burn up chart - Burn up chart is the chart which would represent the amount of work completed on the vertical axis. Time would be represented on the horizontal axis and work completed on the vertical axis. The amount of work which would be in scope would be plotted as a line. The burn up would be expected to approach this line as the work is completed.
  3. Daily Scrum - Scrum is an event which is a 15-minute time-boxed even that is held each day for the development team. Daily Scrum would be conducted at the same time and same place each day to reduce complexity.
  4. Definition of Done - Definition of Done is the way the quality of work is derived and is used to assess when a user story is completed.
  5. Development Team - It is the role within the scrum team who is accountable for Organizing, managing, and doing all development work that is needed to create a releasable product increment.
  6. Emergence - It is the process of coming into existence of new facts or new knowledge fact which is becoming visible unexpectedly.
  7. Empiricism - It is a process control type in which only the past would be considered and accepted as certain, decisions would be based on Experience, Experimentation and Observation. It has three pillars: Inspection, adaptation, and transparency.
  8. Increment - Scrum Artifact that would define a valuable and complete work that is produced by the Development team during a sprint. Sum of all the increments would produce a product.
  9. Product Backlog - It is a Scrum Artifact that would consist of list of work that would be done to create, maintain and sustain a product. Product Backlog would be maintained by the Product Owner.
  10. Product Owner - Product Owner would be responsible to increase the product value by incrementally managing and expressing functional and expressing business for a product to development teams.
  11. Ready - An understanding between the Development team and Product Owner about the preferred level of description of the product backlog items that are introduced at the sprint planning.
  12. Scrum - Scrum is a lightweight framework that is easily understandable and difficult to master. This framework would support the teams in complex product developments. Scrum would consist of Scrum Teams and their associated roles, artifacts, rules, and events.
  13. Scrum Board - It is a physical board that is used to visualize the information for and by the Scrum team. It is often used to manage sprint backlog.
  14. Scrum Master - Role within a scrum team who is accountable for coaching, guiding, teaching, and assisting a scrum team.
  15. Scrum Team - Scrum Team is a self-Organizing team which consists of a Product Owner, Scrum Master and Development team.
  16. Self-Organization in Scrum - Self Organized scrum Teams are self-sufficient and self-reliant in accomplishing their work without the need of any guidance. Teams are so proficient enough to adopt the best practices to achieve their sprint goals.
  17. Sprint - Scrum is a time-boxed event which would consume one month or less time period and which would serve as a container for other scrum activities and events. Sprints would continue one after the other without any gaps.
  18. Sprint Backlog - Once the sprint planning is done, the team would work only on a chosen set of items in the next sprint. Those items will then be removed from the product backlog and moved into the sprint backlog. The sprint backlog would be guided by a sprint goal. Sprint backlog is the actual work which the team currently plans to complete during the sprint.
  19. Sprint Planning - Scrum Planning is a time boxed event to 8 hours or less to start a sprint. It would serve the scrum team to inspect the work from product backlog which is most important to be accomplished next and design that work into sprint backlog.
  20. Sprint Retrospective - This would be the Final meeting in the Sprint.The Scrum team would review what could be improved for future sprints and how they should be done.
  21. Sprint Review - Scrum Event is set to a time boxed event of 4 hours or less in order to conclude the development work of a sprint.
  22. Stakeholder - A person who is external to the scrum team with a particular interest in and the knowledge of a product that is needed for an incremental discovery represented by the product owner .He would be and would be engaged actively with scrum team at sprint review.
  23. Values - When the values of commitment, focus, openness, courage and respect are incorporated, the 'scrum pillars' of transparency, adaption and inspection would create trust to everyone.
  24. Velocity - Velocity is a measure of the amount of work a team would handle during a single sprint and is an important metric in Scrum.Velocity would be calculated at the end of the sprint by summing up all the points for all user stories that are completed totally.