Sprint burndown – Выгорание спринта: a visible chart that indicates on a daily basis the amount of work remaining in the sprint.
Story – История: a backlog item usually using the template form: as a [user] I want [function] so that [business value], cf product backlog item.
Relative estimation – Относительная оценка: sizing backlog items by grouping them into relative size ranges rather than by absolute units (e.g. – hours). See Fibonacci and t-shirt sizes.
Release – Выпуск: the transition of an increment of potentially shippable product from the development team into routine use by customers. Releases typically happen when one or more sprints result in the product having enough value to outweigh the cost of deploying it.
Release burndown chart – Диаграмма выгорания релиза: a visible chart to show progress towards a release.
Roman vote – Римское голосование: see thumb vote.
Done – сделано: also referred to as “done done”, this term is used to describe a product increment that is considered potentially releasable; it means that all design, coding, testing, and documentation have been completed and the increment is fully integrated into the system.
Epic – эпик: a very large user story that is eventually broken down into smaller stories; epics are often used as placeholders for new ideas that have not been thought out fully. There’s nothing wrong with having an epic, as long as it is not a high priority.
Impediment – “проблемы” мешающие гибкой команде: anything that prevents the team from meeting their potential (e.g. chairs are uncomfortable). If organizational, it is the scrum master’s responsibility to eliminate it. If it is internal to the team, then they themselves should do away with it.
Impediment backlog – бэклог “проблем”: a visible or non-visible list of impediments in priority order according to how seriously they are blocking the team from productivity.
Release – выпуск: the transition of an increment of potentially shippable product from the development team into routine use by customers. Releases typically happen when one or more sprints result in the product having enough value to outweigh the cost of deploying it.
Cross-functional team – Кросс-функциональная команда: a team that has all the necessary skills t create the product
Spike – “всплеск”: a short, time-boxed piece of research, usually technical, on a single story that is intended to provide just enough information that the team can estimate the size of the story.
Story point – количество “чего либо”, которое обозначает сложность задачи(таска): a unit of measurement applied to the size of a story, cf. Fibonacci sequence T-shirt sizes, powers of 2, are other ways of assigning story points.
Velocity – насколько быстро команда выполняет работу(обычно в сторипойнтах(смотри выше)): the rate at which a team completes work, usually measured in story points. In scrum, velocity is how much product backlog effort a team can handle in one sprint. This can be estimated by viewing previous sprints, assuming the team composition and sprint duration are kept constant. It can also be established on a sprint-by-sprint basis, using commitment-based planning.
Stakeholder – Акционер: a person external to the Scrum Team with a specific interest in and knowledge of a product that is required for incremental discovery. Represented by the Product Owner and actively engaged with the Scrum Team at Sprint Review.
Timeboxing- таймбокс:is a time management technique where you allocate a fixed time period to a planned activity.
SCRUM
Sprint – Спринт: goal aka sprint theme; the key focus of the work for a single sprint.
Sprint task – Спринт задача: a single small item of work that helps one particular story reach completion.
Sprint backlog – Бэклог спринта: defines the work for a sprint, represented by the set of tasks that must be completed to realise the sprint’s goals, and a selected set of product backlog items.
Scrum master role – Роль скрам-мастера: the scrum master is a facilitator for the team and product owner. Rather than manage the team, the scrum master works to assist both the team and product owner in the following ways
Scrum – cкрим – скурим – скрам: Scrum is a lightweight framework that helps people, teams and organisations generate value through adaptive solutions for complex problems as defined in the Scrum Guide.
Product Owner (PO) – Владелец продукта – the only person responsible for managing the Product Backlog
Product Backlog – список задач: A Scrum Artifact that consists of an ordered list of the work to be done in order to create, maintain and sustain a product. Managed by the Product Owner.
Sprint planning – Планирование спринта: a meeting between the team and the product owner to plan the sprint and arrive at an agreement on the commitment.
Sprint Review – Обзор спринта: a meeting where the team inspects the outcome of the Sprint and determines future adaptations.
Sprint Retrospective – ретроспектива спринта: a meeting with the purpose to plan ways to increase the quality and effectiveness of the next sprint.
Increment – инкремент: the final product of a sprint that represents a prototype of the final product
Daily scrum – Ежедневный скрам: a 15-minute daily team meeting to share progress, report impediments and make commitments. During the daily scrum each team member answers three questions:
- “What have I done since the last scrum meeting? (i.e. yesterday)”
- “What will I do before the next scrum meeting? (i.e. today)”
- “What prevents me from performing my work as efficiently as possible?”
Scrum values:
- Commitment – обязательство
- Courage – смелость
- Focus – фокус
- Openness – открытость
- Respect – уважение
Definition of “Done” – Определение термина “Сделано”: a checklist of items that must be completed to call an item is finished