Combining Kanban and Scrum – lessons from a team of sysadmins Katarzyna Terlecka Agile Conference (AGILE), 2012 Student: 劉家豪 Student ID:102522087.

Slides:



Advertisements
Similar presentations
Iteration Planning.
Advertisements

Tech Next - Scrum Vs Kanban practiced in product development Tech Next, May 7, 2011
The Kanban Game Tsutomu YASUI aka Yattom Agile Developer and Coach
ITEC 370 Lecture 24 Lifecycles. Review Questions? –Grades for Requirements/Design Doc F give prototype demonstration –Testing plan for your software Maintenance.
Scrum. An evolutionary/iterative/incremental/agile software process The main roles in Scrum are: – Scrum team: Team of software developers – Scrum master.
Project Management with TFS 1. What TFS offers for Project Management? Work Item tracking 2 Portfolio backlog Backlog Issue tracking Feature Product Backlog.
Scrum introduction XP Days Agenda Introduction The Scrum process – roles, ceremonies and artifacts Backlog management Conclusions and questions.
Morning – 9am Getting Started Agile Manifesto Values & Principles Scrum Framework ~~ 10:40 to 11:00 Break ~~ Scrum Roles Backlog Grooming Estimation.
Rules of the Game  Loosely based upon the TV show, “Who wants to be a millionaire.®”  Once the question is read, you will have 30 seconds to discuss.
Delegation Skills.
International Scrum Institute Accredited Scrum Certifications for Agile Software Practitioners.
Agile-SCRUM. Introduction to SCRUM Sanil Xavier What is Scrum?
Kanban in Action City Grid Media Case Study Jason Lenny.
Mobile Apps: Review and Retrospectives Refresher Agile Transformation Team 1.
Kanban “Signboard”.
© 2010 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. Deeper Dive Into: User Stories.
What is Scrum Process? Where is it used? How is it better?
Software Engineering- Scrum 徐 瑋 Alen 林芳瑜 Flora 1.
SWEN 302: AGILE METHODS Roma Klapaukh & Alex Potanin.
SCRUM Not your average bacon and eggs. The Basics Product Backlog Sprint Backlogs Sprints – The Daily Scrum – Burn-down chart Sprint Retrospective.
SCRUM introduction 6 April Scrum Team are known as pigs because they’re committed to delivering Sprint Goal People who are involved but not dedicated.
Release and Iteration Planning September 13, 2008.
How to Run An MARKETING SPRINT. This Guide Covers: Why Agile Marketing? How to Put Agility Into Practice How to Make an Agile Marketing Team Agile Marketing:
Take No Prisoners How a Venture Capital Group Does Scrum Jeff Sutherland, Ph.D., USA Igor Altman, USA Agile /05/191.
Copyright © 2012 by Mark J. Sebern Scrum Overview (from
Computer Science and Software Engineering© 2014 Project Lead The Way, Inc. Software Design Process.
Dr. Nguyen Hai Quan.  Why SCRUM?  What is SCRUM?  Some terms  SCRUM Meetings  Sprint  Estimation  Product backlog  Sprint backlog  Whiteboard.
SCRUM and agile methodologies in Production  What is SCRUM?  “The Agile approach is to iterate on the development of the game and react to the results,
Het einde van het beroep van tester - Wat Agile, DevOps en Scrum betekenen voor het testvak -
Theories of Agile, Fails of Security Daniel Liber CyberArk.
Copyright © by Mark J. Sebern Software Engineering Process I SE 2800.
SCRUM.
Agile Adoption G8way Health Project.
AGILE - IMPLEMENTATION (C) CLARION TECHNOLOGIES. ability to move quickly and easily…. AGILE MEANING (LITERALLY)
Using Scrum to Improve Teamwork, Communication, Quality and Speed
Lecture 5 17/9/15. What is Scrum? Scrum is one of the leading agile software development processes Agile framework for completing complex projects. Originally.
AGILE - IMPLEMENTATION (C) CLARION TECHNOLOGIES. ability to move quickly and easily…. AGILE MEANING (LITERALLY)
Agile Ceremonies. Agile - Ceremonies cer·e·mo·ny serə ˌ mōnē noun 1. a formal religious or public occasion, typically one celebrating a particular event.
Challenges of Kanban – how to make it work? Project manager at Execom Professional Scrum Master Master of Computer Milena Pajic |
 SBOK™ (SCRUM Body of Knowledge)  Student course workbook  Case study booklet  Scrum in a page  Scrum Product Owner Certified physical certificate.
1 Development with Agile methodology Scrum Lifecycle DEVELOPMENT PROCESS IN DROISYS INC.
IT Factor TEAM 84 DANI CASABLANCAS, JOHN CRENSHAW, MICHAEL LEONARD, JOHNNY LU, MINNA PRITCHARD, CHAD TUNNEL
Created By:-
Using Scrum to Improve Teamwork, Communication, Quality and Speed.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Barnes & Noble Alonda Morgan. Agile UX Agile.
Utilize Agile Project Management for GIS Projects Jennifer Prather and Lana Tylka.
Agile Project Management
To Scrum or Kanban: Is that the Question?
Project Management with VSTS
Scrum.
Scrum and TargetProcess
Product Sprint Backlog Backlog Up to 1 Month The Scrum Framework
Not your average bacon and eggs
COMP 135: Human-Computer Interface Design
Chapter 3: The Project Management Process Groups: A Case Study
Decomposition.
Johanna Rothman Agile Team Measurements Chapter 12
Teaching slides Chapter 1.
Summarizing Our Models to Date
Scrum Overview.
SCRUM PROCESS RELEASE SCRUM PROCESS M SCRUM ROLES
Scrum Overview.
Agile practices for documentation teams
Delegation Skills.
Scrum in Action.
Scrum: Daily Stand Up Meeting
Organizing and Accelerating Your Work with Scrum
Sprints.
A quick intro to SCRUM and KANBAN By John Voris.
Presentation transcript:

Combining Kanban and Scrum – lessons from a team of sysadmins Katarzyna Terlecka Agile Conference (AGILE), 2012 Student: 劉家豪 Student ID:

Outline Introduction First Try – Scrum Second Try – Kanban The Scrum and Kanban Hybrid Lessons from the way 2

Outline Introduction First Try – Scrum Second Try – Kanban The Scrum and Kanban Hybrid Lessons from the way 3

Introduction A team of fantastically intelligent system administrators. The team consisted of : Two Windows guys were taking care of one sub-network. Three Linux admins with their own network and source control systems. One group knew nothing about others! They have had responsibilities and access to different parts of the network and those due to security policies could not be shared. 4

Introduction Those five guys had around 1700 users distributed across 3 locations and 1000 square meters of a telecommunications laboratory space to take care of. They were administering close to 100 various servers, spread across 4 server rooms in two locations in the city. Because of that the amount of ad-hoc work they’ve had usually exceeded 50 % of their time. 5

Outline Introduction First Try – Scrum Second Try – Kanban The Scrum and Kanban Hybrid Lessons from the way 6

First Try – Scrum They was asked to introduce Scrum to the team for improving the work management. They struggled for five weekly sprints, but failed miserably at each event. Because of the granularity of tasks and the change, the sprint planning meeting does not make sense at all. 7

Outline Introduction First Try – Scrum Second Try – Kanban The Scrum and Kanban Hybrid Lessons from the way 8

Second Try – Kanban The idea of Kanban, which was use to manage work flow. After five days everything crumbled again. They needed that impaired but still beneficial planning, measurements, the care of the Product Owner, someone to guard the process and take care of them, estimations and progress projections and before all, the feeling and view of progress. 9

Outline Introduction First Try – Scrum Second Try – Kanban The Scrum and Kanban Hybrid Lessons from the way 10

The Scrum and Kanban Hybrid There was a Definition of Done for few types of tasks, that had to be followed. There was a Product Backlog - an ordered list of things to do. Format is up to the Product Owner. There was also a physical Board. Queues Competency groups Done & rejected 11

The Scrum and Kanban Hybrid 12

The Scrum and Kanban Hybrid Quotas - recommended limit of tasks N of m members m + 1 <= N <= 2m + 2 Roles - There was a Product Owner, who was taking care of the Product Backlog, and producing tasks for the board. Event – Grooming Session (weekly), Retrospective (2 weeks), Review (max 2 weeks), Daily planning (0.5hr) 13

Outline Introduction First Try – Scrum Second Try – Kanban The Scrum and Kanban Hybrid Lessons from the way 14

Lessons from the way Product Owner - the team decided to direct all requests to him, so that they can work undisturbed. Planning – everyday planning like a sprint. Firefighting - they decided to set up a firefighter, who will take care of a designated mailbox with all of the tiny requests. If there was a bigger thing, the firefighter forwarded the message to the PO. 15

Lessons from the way Continuous Improvement - all improvements were stored at the bottom of the Product Backlog, and once in a while they were reviewed and pulled up. The feeling of progress – One of the biggest problems in Kanban was that the team did not feel the progress. In the hybrid, from time to time we assembled to review finished elements on the board. 16

Q & AQ & A 17