Photo by Syd Wachs (Syd Wachs) on Unsplash
You will need it to understand the Scrum Guide.
The common name for the Product Backlog, Sprint Backlog and Product Increment.
A list of future changes in the Product. Product backlog is created and edited by the Product Owner only.
A list of tasks for the current cycle. The Sprint backlog is made by the Development Team.
Responsible for the Product, has a vision of what kind of Product customers will prefer and appropriately will make a profit. Only the Product Owner can create and edit Product Backlog.
Daily the Development Team meeting, where it analyses what was done for the last day and expects the remaining work for today. The daily Scrum helps the Team to follow a gradual approximation to the Sprint Goal.
All new features, created during current and previous cycles. For example, if a bakery bakes pies, the Increment will be a new filling or an improved dough recipe.
Consistent and gradual improvement of the Product every next Sprint.
Work in small steps. With this approach, it is impossible to make a perfect Product with all desirable functions instantly. So first, Product with minimum of options is created and then the Team step by step adds new features or remove some old ones. It is important that at the end of each stage (iteration) there is the Product that works and it is available for customers.
The Product quality standards. Needed to exclude the hack work. If some features, done during the Sprint, do not meet all the Criteria, it means the Product is not ready yet.
The Development Team
A team that produce a Product. The optimal size is 3–9 people.
Photo by Tim Gouw(Tim Gouw) on Unsplash
Way of learning when the teacher (coach) does not give ready answers but helps the client to find them by his own.
The client: My business does not make a profit. What should I do?
Expert: You have problems here and here. Fix them and everything will be OK.
Coach: Let’s see. Why is your business not profitable?
The Sprint Overview
Presentation of updated Product to stakeholders, customers and the Product Owner. The Sprint Overview is needed to obtain feedback on the updated Product and adjust its further development. One of the five main Scrum events.
Meeting of the Product Owner and Development Team, where they decide what will be done in this Sprint. One of the five main Scrum events.
The Sprint Retrospective
Meeting of the scrum-master and the Development Team, where they discuss the work of the Team. What problems in relationships, tools and processes the Team faced and how they can be fixed. One of the five main Scrum events.
A way to organize the work in the spirit of Agile. Scrum is a framework, but not a methodology.
The Product Owner + The Development Team + Scrum-master.
Responsible for the promotion and support of Scrum in the company. Helps everyone to understand the theory, practices, rules and values of Scrum.
The Scrum Board
A tool that helps to visualize the Product workflow process during the Sprint. Can be a real Board with leaflets or notes or online Board in the program. The main thing is, it should be convenient to use by the Team. An optional artifact.
A period during which the Scrum Team creates or improves some of the Product options preferred by the customer.
A person interested in the Product success. A stakeholder can be an investor, a regular customer or any person whose opinion is important.
Product Backlog Refinement (PBR)
In this process the Development Team and the Product Owner take part only. Together, they divide tasks into pieces that can be done during one Sprint. One of the five main Scrum events.
A set of rules that helps to organize the workflow according to the principles of Agile.
An essential skill for a scrum master. Organizing of effective discussion of working moments. For example, the Team gathered on the Sprint Retrospective.
Scrum master invites the Team to discuss the last Sprint and keep silent till the end of Retro. The team begins the discussion, but are constantly distracted by secondary topics. As a result, nothing was decided for the allotted time.
The scrum master asks guiding questions, organizes the discussion in pairs, and then collects the results into one big poster. The team offers swings and changes in workflow.
Values of Scrum
Loyalty, courage, focus, openness and respect. By following the Scrum values a favorable atmosphere for work is created.
The basic idea of Scrum. Work based on the transparency of all processes, inspection of work and adaptation to changing conditions. For example, air-conditioner regularly measures the temperature in the room (inspection) and, if necessary, switches on cooling mode (adapts). It is important that the temperature sensor works properly and correctly shows the temperature (transparency).
Got an idea or a project? Hire the Agile Software development team. No-Risk
Photo by Antenna(@antenna) on Unsplash