DaKiRy_PMWeekend2016_Валентин Будкін "Мітинги в Scrum - the Good, the Bad and the Ugly"

•

0 likes•160 views

The document discusses various Scrum meetings and provides classifications of "The Good, The Bad, and The Ugly" for each meeting. It summarizes the Daily Standup meeting as having a timebox of 15 minutes where the team updates each other on work, which is good, but can be bad if driven or includes silent members or micromanaging. It also notes implementation talk and using the improvement board as ugly aspects.

Business

Scrum
meetings
The Good, the Bad and the
Ugly

Titles
• Valentyn Budkin
• Scrum facilitator since 2010
• Certified Scrum Product Owner
• val.budkin@gmail.com
Special thanks for Sergio Leone

The Good
• 15 minutes
• Team runs it
• Updating each other
• Timebox
• Chat is OK

The Bad
• Driven
• Asking questions
• Silent
• Managing

The Ugly
• Middle of the day
• Implementation
talk
• Improvement Board

The Good
• 4 hours
• Freezing changes
• Developer create
tasks
• Definition of Done

The Bad
• Non completed backlog
• No ROVe
• Micromanaging tasks

The Ugly
• Detailed backlog
• Scope with date and
budget
• Trading on scope
• Courage

The Good
• 2 hours
• Product owners job
• Tour on working delivery
• Receive feedback
• Put feedback on a board

The Bad
• Show screenshots
• Blaming each other
• Schedule it on Friday

The Ugly
• Devlopers on the stage
• Blaming Product Owner
• Boss sets timing

The document discusses scrum meetings including daily standups, planning meetings, sprint reviews, and retrospectives. It identifies things that can go well ("the good"), problems ("the bad"), and worse issues ("the ugly") with how these meetings are conducted. Key recommendations include keeping meetings short and focused, having the team lead discussions, providing feedback to improve but not blame, and maintaining a safe environment for open discussion.

Scrum meetings

Juan Banda

Scrum meetings include estimation meetings, sprint planning meetings, daily scrum meetings, sprint reviews, and sprint retrospectives. Estimation meetings are held to formally estimate work in preparation for sprint planning. Sprint planning meetings are held in two parts - first to review and analyze the product backlog and team capabilities, and second to analyze and design the sprint goal and selected product backlog items. Daily scrum meetings are 15-minute stand-up meetings held daily to discuss work achieved, work planned for the next day, and any impediments. Sprint reviews are held with stakeholders to review functionality completed during the sprint and groom the product backlog. Sprint retrospectives are held for the team to inspect and adapt their process and

Flexible Meetings

Kirill Romanov

The document outlines different types of meetings that can be part of an agile Scrum process, including daily stand-up meetings, daily team lead calls, weekly grooming meetings, weekly technical review meetings, bi-weekly sprint planning meetings, bi-weekly architecture committee meetings, demonstrations after each sprint, weekly retrospectives, monthly global reviews, and occasional "come into my world" meetings. It provides brief descriptions of the goals and participants for each type of meeting.

Agile SCRUM presentation HJT_Final

Haresh Thevathasan, PMP®, ITIL®, CSM

The document discusses the Scrum framework, an agile methodology for project management. It describes Scrum practices like sprint planning meetings, daily stand-ups, sprint reviews and retrospectives. The Scrum framework uses product backlogs, sprint backlogs and increments to organize work into short cycles. Key Scrum roles include the Product Owner, Scrum Master and development team. The goals of Scrum are to deliver working software frequently through self-organizing teams, transparency and inspection/adaptation of the process.

Scrum methodology

sgibby238

Scrum methodology

Bunlong Van

Scrum is a framework for managing projects that uses sprints, daily stand-up meetings, and artifacts like a product backlog to facilitate collaboration and ensure work is progressing towards goals. Key roles include the product owner who prioritizes work, the scrum team who does the work, and a scrum master who facilitates the process. Each sprint is time-boxed, usually to two weeks, and results in a potentially shippable product increment that is reviewed at the end of the sprint. Meetings like planning and retrospectives help coordinate work and improve the process. The goals of scrum include accountability, ability to adapt to change, and focus on delivering value.

2013 Enterprise Track, Getting GIS done using the Scrum Methodology Jonathan ...

GIS in the Rockies

We live in a world where limited resources is a constant battle. One of the biggest struggles is how to get work done and make sure that it brings the most value possible to our customer. Managing GIS work through Scrum provides a way to do this. In this presentation, I will explain the concepts around the Agile methodology and how it could be applied not only in the IT world, but to any GIS work that needs to be done.

Scrum basics

casarica

Scrum is an agile framework for managing product development that involves short development iterations called sprints. The key roles in scrum include the product owner, scrum master, and development team. Scrum utilizes ceremonies such as sprint planning, daily stand-ups, sprint reviews, and retrospectives. It focuses on transparency, inspection, and adaptation through artifacts like the product backlog and sprint backlog. The goal of scrum is to deliver working software frequently and gather feedback to make continuous improvements.

This document provides an overview and agenda for a training on Scrum basics. It begins with an introduction section and then covers the fundamentals of Scrum over multiple sections. It includes details on roles like Product Owner and Scrum Master. There is a section on the Scrum process that outlines the sprint planning, daily standup, demo, and retrospective meetings. Other areas covered include prioritizing the product backlog, velocity, estimation techniques, and tips for running an effective retrospective. The training will conclude with a question and answer session.

Can GIS be Agile?

Tim Nolan

This document discusses how geographic information systems (GIS) projects can adopt agile methodologies. It provides an overview of agile concepts like iterative development, self-organizing teams, and delivering working software frequently. The document explains how GIS projects involve similar elements to software projects like requirements, design, implementation, and maintenance. It then offers practical advice for implementing agile practices in a GIS context, such as defining user stories, estimating efforts, and tracking progress through burn down charts and velocity metrics. The goal is to help GIS teams work in a more iterative and collaborative way to continuously improve.

Scrum Methodology

Nader Abdallah

This document provides an overview of Scrum, an agile project management framework. It defines Scrum, describes its core components including roles like Product Owner and Scrum Master, and the sprint-based process. Key aspects covered are the product and sprint backlogs, daily scrums, sprint planning and reviews. Benefits of Scrum like improved productivity, communication and handling changing priorities are highlighted. The document also briefly discusses scaling Scrum to larger projects and teams.

Scrum Methodology

University of Haripur

The document discusses the Scrum methodology. It describes the key concepts of Scrum including product backlogs, which are collections of user stories that describe features from the user's perspective. It outlines the main roles in Scrum including the product owner, Scrum master, developers, and testers. It also describes the planning process, sprints which are short work cycles, burndown charts to track progress, and sprint retrospectives to improve.

ScrumInTenSlides

Learning Tree International

The document summarizes key aspects of Scrum in 10 slides. It outlines the 5 Scrum values of commitment, focus, openness, respect and courage. It then describes the roles of the Product Owner who manages the product backlog and maximizes ROI, the Scrum Master who facilitates Scrum events and removes impediments, and the self-organizing Scrum Team. It also summarizes the product backlog, sprint goal, daily scrum meeting, sprint review, sprint retrospective and the process of continuous improvement in Scrum.

What is scrum

Aaron Corcoran

This document provides an overview of Agile and Scrum concepts and processes. It describes the purpose of Scrum as delivering value through incremental releases. The key roles of Product Owner, Scrum Master, and Team are outlined. Scrum artifacts like the Product and Sprint Backlogs and their purposes are defined. Meeting ceremonies like Sprint Planning, Daily Scrum, Review and Retrospective are summarized along with their goals and timing. The document emphasizes continuous inspection and adaptation through its cadenced processes.

General Scrum Guidelines - Everyday Activities

Miro Jeliaskoff

Learn scrum in half an hour

Abhay Kumar

The document provides an overview of Agile Scrum methodology. It describes the key roles of Product Owner, Scrum Master, and Team. It explains the main Scrum processes of Release Planning, Sprint Planning, Daily Scrum, Sprint, Sprint Review, and Sprint Retrospective. It outlines the activities involved in each process and how they contribute to delivering working software in an iterative manner through inspection and adaptation.

Agile Methodology

AnveshPatel7

The document discusses Agile methodology and Scrum framework. It describes Scrum as an Agile process that focuses on delivering high business value in short iterations through inspection of working software. Scrum uses roles like Product Owner and Scrum Master, ceremonies like Sprint Planning and Daily Scrums, and artifacts like user stories, product backlog and burn down charts. The document outlines the advantages of Agile as rapid delivery, interaction emphasis, and adaptation to change, as well as potential disadvantages like difficulty assessing effort upfront and lack of documentation emphasis.

Scrum, A Brief Introduction

Muhammad Waqas Akram

Занічковська Олена і Крамаренко Михайло ГРА "Виграй у тендері!"

DaKiRy_PMWeekend2016_Валентин Будкін "Мітинги в Scrum - the Good, the Bad and the Ugly"

Recommended

Recommended

More Related Content

What's hot

What's hot (10)

Viewers also liked

Viewers also liked (20)

More from Dakiry

More from Dakiry (20)

Recently uploaded

Recently uploaded (20)

DaKiRy_PMWeekend2016_Валентин Будкін "Мітинги в Scrum - the Good, the Bad and the Ugly"