Mai Müür Tallinn 2014.  Retrospective as a part of Scrum  The idea of retrospectives  Rules of the game  Impact to IT team  Strenghts and weaknesses.

Slides:



Advertisements
Similar presentations
Service Redesign in an Equally Well Test site Starting Small Fires –
Advertisements

Sprint Review Results Example Template.
Reflections on ‘Middle’ Management. A Question Who is the most important person, at work, in terms of your future success? Answer at end.
Beyond Retrospectives Linda Rising
Agile Project Management with Scrum
Presentation from: See Also: scrumreferencecard.com/ScrumReferenceCard.pdf.
Scrum CS These slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Introduction to Scrum.
Agile Teaming Concepts for and from the Facebook Generation Neil Rodgers NASA Enterprise Applications Competency Center (NEACC) 1.
A Portrait of Scrum Project Management By Nader Khorrami Rad Project Management Professional (PMP) Certified ScrumMaster (CSM) Professional Scrum Master.
Morning – 9am Getting Started Agile Manifesto Values & Principles Scrum Framework ~~ 10:40 to 11:00 Break ~~ Scrum Roles Backlog Grooming Estimation.
Scrum (software development)
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.
Project Retrospectives Linda Rising
Agile Methodologies for Project Management By – Komal Mehta.
Agile/Scrum Case study Code name: ninja.  2 scrum teams  One product backlog  8 months so far  Long term project  External integrations  R&D and.
An Overview of Agile L e a d i n g C h a n g e T h r o u g h C o l l a b o r a t i o n.
Mobile Apps: Review and Retrospectives Refresher Agile Transformation Team 1.
Sprint – Weekly cadence
18 Weeks Referral To Treatment Waiting Times Standard
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.
Winter Pressures Emergency access Getting it right for patients and staff June 2009.
1 - Agile in a nutshell. 2 - Basic principles ●Relies on an iterative, incremental development mechanism with continuous adaptation to customer requirements.
COLLABORATION MODULE #4 Making Decisions Collaboratively An online module developed by Pivot Learning Partners for the West Contra Costa Unified School.
Process is continuously improving Have Definition of Done (DoD) DoD achievable within each iteration Team respects DoD The bottom line Delivering working,
© 2010 Plexent – All rights reserved. IT SERVICE MANAGEMENT March, 16 th 2010 Dr. Mark O. Kaletka Computing Division Associate Head for Laboratory and.
Thematic inter-disciplinary planning & A Curriculum for Excellence Western Isles February 2007: Workshop session.
Simple solutions - work. What have we done differently? Redesign of early years play in one community Redesign of oral health promotion in two communities.
Take No Prisoners How a Venture Capital Group Does Scrum Jeff Sutherland, Ph.D., USA Igor Altman, USA Agile /05/191.
SIMVaC Project Retrospective Summary (Retrospective held on 16 Sept 2005) Mary Lynn Manns With special thanks to.
OFFICE OF INFORMATION AND TECHNOLOGY Mobile Applications Scrum Framework November 21, :00 am (EST) Seal of the U.S. Department of Veterans Affairs.
Scrum Santhosh Srinivasan. Outline What is Scrum What is Scrum Why Scrum Why Scrum Scrum Practices Scrum Practices Why Scrum works Why Scrum works Pros.
With a hint of HP Quality Center Agile development and functional testing: friend or foe? Tom Vercauteren, June 26th, 2009.
Copyright © by Mark J. Sebern Software Engineering Process I SE Sprint review and retrospective.
Reflecting for Revalidation with the Nursing and Midwifery Council
Presentation title: 32pt Arial Regular, black Recommended maximum length: 1 line Innovation – Making it happen NHS Institute for Innovation and Improvement.
WATERFALL DEVELOPMENT MODEL. Waterfall model is LINEAR development lifecycle. This means each phase must be completed before moving onto the next!!! WHAT.
Presentation from: See Also: scrumreferencecard.com/ScrumReferenceCard.pdf.
Giving order to the chaos of agile Presented by Matt Campo CSC 490 Fall 2015.
Retrospectives - Use to Improve Anything Susan Smith Lean Agile Kansas City 2015.
Change is great- you go first! Tony Martin Practice Business Manager July 2008 Hebden Bridge Group Practice.
Learning to Craft Code is Challenging Every skill we have acquired was trick at first We need to take baby steps We need proper support.
Copyright © 2013 by Mark J. Sebern Sprint Review & Retrospective Two “end of sprint” activities Sprint review Sprint retrospective How do they differ?
Releasing Potential Programme Su Fowler-Johnson, Director Claire Harris, Associate Partner.
What is a Project Retrospective? A retrospective is an opportunity for the participants to learn how to improve. The focus is on learning—not fault-finding.
1 Development with Agile methodology Scrum Lifecycle DEVELOPMENT PROCESS IN DROISYS INC.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Introduction to Software Engineering Muhammad Nasir Agile Software Development(3)
AGILE METHODS Curtis Cook CS 569 Spring 2003.
AGILE SCRUM METHODOLOGY
SCRUM.
Product Sprint Backlog Backlog Up to 1 Month The Scrum Framework
Spring 2013 Advising Starts this week.
Not your average bacon and eggs
COMP 135: Human-Computer Interface Design
The Scrum Approach.
Chapter 3: The Project Management Process Groups: A Case Study
CSCE 741 Software Process Lecture 04 Availability
AGILE METHODOLOGY MANAGE PROJECT USING AGILE SCRUM.
Teaching slides Chapter 1.
SCRUM PROCESS RELEASE SCRUM PROCESS M SCRUM ROLES
CSCE 741 Software Process Lecture 04 Availability
CSCE 741 Software Process Lecture 04 Availability
Scrum Overview.
Part 2 of the Module.
“If it’s a school day, during school hours, one-fifth of the total American population consists of public school students K through 12. One in five Americans.
Agile, Scrum and CMMI Methodologies
Presentation transcript:

Mai Müür Tallinn 2014

 Retrospective as a part of Scrum  The idea of retrospectives  Rules of the game  Impact to IT team  Strenghts and weaknesses

Sprint planning meeting Daily scrum 1-2 weeks Sprint review meeting Sprint retrospective 1-3 hours Release Sprint backlog Product backlog Updated product backlog

Here is Edward Bear, coming downstairs now, bump, bump,bump,bump, on the back of his head, behind Christopher Robin. It is, as far as he knows, the only way of coming downstairs, but sometimes he feels that there is another way, if only could stop bumping for a moment and think of it. * * qoutation from Winnie the Pooh by Norm Kerth, (Kerth 2001) Norm Kerth** **Norm Kerth -the founder of the modern-day movement of retrospectives

What went well? Where we failed? What should we improve? What should we stop? What should we start? DEVELOPMENT PROCESS Tehnical event Organizational event Personal event INSPECTADAPT Made by Scrum Team Supported by Scrum Master

Scrum retrospective prework Timebox for meeting 1-3 hours Scrum exercises Decisions for next sprints : What? Who? When? Changes to product backlog

KEEP DOING STOP DOING TRY INSIGHTS PREASSIGNED CATEGORIES SILENT GROUPING SHARED CONTEXT PRIORITIZING INSIGHTS DOT VOTING DETERMINE THE SOLUTION/WHO WILL DO IT/ HOW LONG DOES IT TAKE INSIGHTS BACKLOG. CLOSING. FOLLOW UP

INPUT  Agreed focus  Precollected objective data  Team members with subjective data and spirit  Backlog of insights from previous retrospective  Exercises and materials for visualization OUTPUT  Process improvement actions  Insight backlog  Changes in teamspirit

You might not like Your job, but still enjoy the camaraderie of the people You work with.* * Explanation to the word “c amaraderie” in Vocabulary.com

STRENGHTS  Fixed rules and timetable  Positive mindsetting  Equal possibility for every team member  Simple decision making tools WEAKNESSES  Weak Scrum Master  Inactivity in reflection/participation  Team doesn`t have clear understanding about Scrum process

Take retrospective as a good advantage to look inside the process, before You are totally lost. Thank You!

 Derby E., Larsen D., Agile Retrospectives, The Pragmatic Bookshelf; version: P 6.0 – 2011  Schwaber K., Sutherland J.; The Definitive Guide to Scrum: The Rules of the Game, The Scrum Guide TM, July2013  Rubin, Kenneth S. Essential Scrum: A Practical Guide to the Most Popular Agile Process (Addison-Wesley Signature Series (Cohn)) (Kindle Location 21). Pearson Education. Kindle Edition. (