Do (Work each Day within iteration)
Vocabulary 1.1
| English | Translate in the context |
| Scope Matters | вопросы содержания |
| Project Charter | Устав проекта |
| justification | обоснование |
| assumptions | допущения |
| milestone | веха |
| approval | одобрение, утверждение |
| template | образец |
| baseline | основа, база, базисный |
| consequences | последствия |
| predetermined | предопределенный |
| to gather up | собрать |
| implementation | внедрение |
| output | Здесь: проектный результат |
| outcome | Здесь: продуктовый результат |
| Work Breakdown Structure | структурная декомпозиция работ, иерархическая структура проектных работ |
| encompass | охватывать |
| Work Packages | пакеты работ, самая мелкая единица в структурной декомпозиции работ по проекту, более неделимая |
| tangible | вещественный, ощутимый, зримый |
| gui | графический интерфейс пользователя |
| backend | базовая программа |
| User’s stories | пользовательские истории (элемент бэклога, обычно представляющий собой описание части общего результата в виде законченной с точки зрения конечного пользователя характеристики, свойства, кусочка продукта) |
EXERCISE 3
SCRUM CARD GAME
The purpose: to learn the SCRUM framework in operation processes
The volume: 3 academic hours, in accordance with learning plan.
About the Game
SCRUM CARD GAME[1]. The goal of the second part of the game is to learn the SCRUM framework in operation processes. It is a simple game, which lets players experience work in Scrum sprints and brings to discussion many questions and topics that happen in real life while working in a Scrum team. This experience facilitates learning and makes participants prepared to the real use of Scrum.
|
|
|
It is necessary to divide the student group into teams of 4-5-6 students, equally if possible. No more than six players per team.
There are some roles in each subgroup: Product Owner, Scrum Master and Scrum Team (picture 5).
Picture 5. SCRUM framework
Set the Goal: You are competitive development centers aimed to deliver a new application to the market. The most productive team wins.
Game Set
- Set of cards: Stories, Events, Problems, and Solutions (see printable version below)
- Two six-sided dices (per each team)
- Flipchart
- Markers
Preparation
● Provide each team with a set of Story cards
○ Cards with stories forming the “Backlog” deck
○ Backlog is prioritized (sequence number in top corner) and estimated (hours in bottom corner) by the Product Owner in the beginning of the Game
○ 3 days per iteration (there will be maximum 3 iterations)
○ every iteration consists of:
■ Planning and commitment
■ Work within iteration
■ Sprint Review + Retrospective
● Make the group arrange a simple Task Board by marking TO DO, DOING, DONE columns with simple sticky notes to visualize their state.
● Prepare a flipchart list with visualization of PLAN and ACTUAL columns for each team in play.
The Product Owner prioritizes the Backlog (Story cards): writes sequence number in top corner for each Story card and estimates them – writes the number of hours in bottom corner of the Story Cards. The Product Owner may (has to) change these number during the game (but not during the Sprint). This role should not be combined with that of the Scrum Master. The product owner should not dictate how the team fulfills the task.
The Scrum Master is accountable for removing impediments to the ability of the Team to deliver the product goals and deliverables. The Scrum Master acts as a buffer between the team and any distracting influences. The Scrum Master ensures that the scrum framework is followed.
|
|
|
The core responsibilities of a scrum master include:
· Helping the Product Owner.
· Helping the team to determine the definition of done for the product
· Coaching the team, within the Scrum principles
· Promoting self-organization within the Team
The team experience three Scrum Sprints with a normal cycle: Plan, Do, Act, Check (pic. 6).
Picture 6. PDCA Cycle
Planning
● Scrum Master asks his team “how many features do you believe you can deliver in the next iteration?”
○ In the first round every team may calculate their number of man-hours per iteration as they would like to do. It is allowed them to make even optimistic commitment.
○ To perform 2nd and 3rd planning Scrum Master asks his team to use historical data.
● Scrum Master puts selected cards from “Backlog” into TO DO column.
● Scrum Master writes down commitment as the total number of estimates and numbers of Stories of every team on a flip chart into “Plan” column.
Do (Work each Day within iteration)
Each iteration consists of three days. Each day consists of every team-member working on the sprint.
It starts with player 1 “working” on the sprint. If the last member of the team “worked” the first day has ended. Now the same for day two and three starts. “Working” in the sprint is described below:
Every team member in their turn should:
● Select a Story to work on (it should appear in “IN PROGRESS”) and make this choice visible by pointing on the card with the finger.
● Roll two dices to determine the number of productive hours of this team-member on this day
● Deduct number on the dice from remaining hours on the card (s)he “works on”
● Pull the card from the “Chance” deck
● Do whatever the card says. There are three possible types of cards:
○ Event - a one-time action, that affects immediately and discarded after the play
○ Problem - these sticky issues are blocking the Story that the player was “working on”. Each problem is a case taken from the real life, a team could bring examples or details into each Problem from their experience.
|
|
|
■ Blocking means the team can’t move the story into DONE state, they have to find a Solution for the kind of problems stated on a card.
■ Blocking doesn’t prevent from continue work on a Story (deducting hours until zero).
■ Sometimes, positive Events could also help with Problems
○ Solutions - A solution is a team’s asset or action which can be applied at any time to solve a problem and unblock a Story. Once Solution applied the Problem and Solution cards are discarded.
■ Solutions could be collected by the team if there are no appropriate Problems - they are collected from iteration to iteration and belong to the whole team.
● If User Story is done (0 hours remaining and no blockers) - move it to DONE column.
● DONE criteria for a Story:
○ Team members delivered the number of hours equal or greater than estimate for a Story
○ A Story is not blocked with a Problem.
Once again, at every “day” each player does follow:
● Choose a card to “work on”
● Throw two dices
● Pick a Chance card
Check (Sprint Review + Retrospective)
● After each player has passed 3 turns - the Sprint is over.
● Each team should present Stories accomplished (i.e. only stories in DONE column) and calculate the actual result as the total of DONE Stories.
● Compare Actual result with initial Plan.
● Review undone work and discuss the reason, also discuss how to account these un-done Stories in next Sprint to make sure we maintain the total number from the original estimations.
● Retrospect on how to perform in next Sprint to achieve more
Act (Debriefing)
To start debriefing you should bring in front of the audience the flipchart(s) with visualizing all Planned and Actual data for each of three sprints.
Here are some topics to
● Planned vs Actual
● Velocity variations
● Hours Estimate vs Size (Original Estimate)
● Major risks happened (Technical, People, Unplanned Events)
|
|
|
● What are the hardest types of risks to take?
● Could we forecast bad events?
● and etc…
INDEPENDENT WORK
You should read the article “The Scream Guide”[2] (Scream is the humoristic imitation of Scrum) and answer the question:
What are the main features that Scrum
is imitated in a company, but is not real?
[1] SCRUM CARD GAME by Timofey (Tim) Yevgrashyn is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License (See http://scrumcardgame.com). To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/4.0/ The roles of Product Owner, Scrum Master were added in the original version.
[2] Michael Küsters. The Scream Guide [Electronic Resource]. – Reading regime:https://docs.google.com/document/d/1-2aZP3BlctQrWP8bNpSxkVBKphypALPINUGGTn26els/mobilebasic#heading=h.wu9pn3pyzdq2
Дата добавления: 2019-11-16; просмотров: 58; Мы поможем в написании вашей работы! |
Мы поможем в написании ваших работ!