Agile Transformation in IT-organizations - Алиса Олеговна Бобовникова

Скачать книгу

helping to find techniques for effective Product Goal detection and Product Backlog management;

      • helping the Scrum Team realize the need for clear and concise Product Backlog elements;

      • helping to apply empirical product planning in a complex environment;

      • facilitating interaction with stakeholders upon request or if necessary.

      A Scrum Master serves the organization in several ways, including:

      • directing, training and advising the organization in Scrum application;

      • planning the transition to Scrum and advising on Scrum application within the organization;

      • helping employees and stakeholders understand and apply an empirical approach to complex work;

      • removing barriers between stakeholders and Scrum Teams.

      SCRUM EVENTS

      Sprint is a container for all other events. Every event in Scrum is a formal opportunity for inspection and adaptation of Scrum artifacts. These events are specially designed to provide the necessary transparency. Failure to conduct any of the Scrum events in accordance with the description leads to a loss of opportunities for inspection and adaptation. Events are used in Scrum to create regularity and minimize the need for meetings not defined in Scrum. A good practice of reducing complexity is to hold all events at the same time, in the same place.

      SPRINT

      Sprints are the pulse of Scrum, where ideas turn into value. This event has a fixed duration of no more than one month to ensure consistency. A new Sprint starts immediately after the completion of the previous one. All the work needed to achieve the Product Goal, including Sprint Planning, Daily Scrum27, Sprint Review and Sprint Retrospective28 events, is done within Sprints.

      Конец ознакомительного фрагмента.

      Текст предоставлен ООО «Литрес».

      Прочитайте эту книгу целиком, купив полную легальную версию на Литрес.

      Безопасно оплатить книгу можно банковской картой Visa, MasterCard, Maestro, со счета мобильного телефона, с платежного терминала, в салоне МТС или Связной, через PayPal, WebMoney, Яндекс.Деньги, QIWI Кошелек, бонусными картами или другим удобным Вам способом.

      Примечания

      1

      Waterfall methodology, also called cascade or waterfall, is a classic model of the software development lifecycle.

      2

      Combination of both iterative and incremental software development methods when the development progress is achieved by short time periods (iterations), each of them delivering an increment to the product developmen

Примечания

1

Waterfall methodology, also called cascade or waterfall, is a classic model of the software development lifecycle.

2

Combination of both iterative and incremental software development methods when the development progress is achieved by short time periods (iterations), each of them delivering an increment to the product development process.

3

Approaches to software development based on the cascade model, with clear sequential stages, and comprehensive documentation.

4

Approaches to software development based on the iterative incremental method.

5

The most common and popular Agile framework.

6

A short time period during which a scrum team performs a given amount of work.

7

A short meeting from 5 to 20 minutes a day, at which team members tell share what is happening in their work tasks.

8

The meeting that starts each sprint, and is intended to determine the team's work plan throughout the sprint.

9

This is a software testing method by which individual units of source code are tested to determine whether they are fit for use.

10

This is a product management method in which you develop a strategy for its phased release.

11

The product or service test version with a minimal set of functions (sometimes even one) that delivers value to the end user.

12

A person or an organization that has rights, interests, requirements or interests regarding the system or its properties that meet their needs and expectations.

13

The information systems creating concept, including their planning, development, testing and deployment.

14

This is a model, illustrating the three constraints interdependence: time, money and scale, as well as how changing one factor requires changing others.

15

A ready-made set of tools that helps a developer to quickly create a product: a website, an application, an online store etc.

16

This is the information with which the Scrum team and stakeholders describe in detail the product being developed, as well as the actions to create it and the activities within the project.

17

An Agile cadence is a reliable series of events and activities that occur on a regular, predictable schedule.

18

This is a small group of people, within which there is no hierarchy, mini-teams or leader and all participants work on the same goal.

19

A Scrum team participants’ roles.

20

A Scrum role which does not imply anything other than the correct Scrum process conduction. Thus, the Scrum master is the server-leader of the team.

A Scrum role, a person responsible for the product creation and

management. (S)he monitors its development process, records the necessary

metrics and is responsible for the result.

21

A Scrum role, a person responsible for the product creation and management. (S)he monitors its development process, records the necessary metrics and is responsible for the result.

22

A team that has all the skills necessary to do the job and is independent on those who are not part of the team. Cross-functional Teams are more flexible, creative and productive than teams where people are specialized in one competence to do their job.

23

An ordered set of elements, a queue of tasks, a list of all the functions that you want to get from the product. This list contains brief descriptions of all the product features desired.

24

A list of specific tasks to implement the product backlog selected elements.

25

This is

Скачать книгу

<p>27</p>

This is a Scrum meeting, one of 5 Scrum events, that lasts no longer than fifteen minutes and is held every working day in the same place at the same time.

<p>28</p>

This is a workshop which is held to discuss how to improve the workflow.