Scrum Round Table - Effective Agile Retrospectives

•

3 gostaram•4,371 visualizações

Scrum Round Table met als thema ‘Effective Retrospectives'. Onder leiding van twee senior ALM Consultants van Delta-N is er gediscussieerd over de uitdagingen die je in de praktijk tegen komt tijdens een retrospective. Voor deze Round Table was met Ben Linders een specialist op het gebied van Retrospectives uitgenodigd. Tijdens het eerste deel van het programma is Retrospective oefening Car Brand gedaan. Vervolgens is er uitgebreid gediscusseerd over situaties uit de praktijk en is afgesloten met een retrospective.

Negócios

Scrum Round Table
Effective Retrospectives

5 slagvaardige units
SharePoint Development Dynamics IT Pro
- CRM
- CRM Online
- Nav
- Integratie
- Mobile CRM
- Office 365
- IT Infra
- Cloud
- Windows
- Windows Intune
- Beheer & support
- Scrum & agile
- Visual Studio
- TFS migratie
- TFS Support
- Workshops
- Scrum training
- Projecten
- Detachering
- Maatwerk
- Mobile
- Apps
- Windows Azure
- Beheer
- Ontwikkeling
- Infrastructuur
- Consultancy
- Vormgeving
- Enterprise Social
- Applicaties
-
ALM

About us
René van Osnabrugge & Jasper Gilhuis
www.roadtoalm.com
@renevo
renevo@delta-n.nl
www.jaspergilhuis.nl
@jaspergilhuis
jasperg@delta-n.nl

About
Ben Linders
www.benlinders.com
@benlinders

Who are you?
Please introduce yourself
Organization
Role
Involvement with Scrum
6

Agenda
Welcome 14:45 – 15:00
Exercise with Ben Linders 15:00 – 16:00
Discussion 16:00 – 16:45
Retrospective 16:45 – 17:00
Closure 17:00 – 17:30

Exercise by Ben Linders
Effective Retrospective

Retrospective Alternatives
- Star Fish
- Sailboat
- Constellation
- Strength Based
- Timeline
- Emotional Seismograph

Questions
What kind of retrospectives do you use?
…
…
…

Retrospective
What worked well?
What could we have done better?
Topics for the next Scrum Round Table?

Thank you!
See you next time!
Thursday October, 9th: Backlog refinement: The Perfect User Story
More information: www.delta-n.nl/scrum-round-tables

About Delta-N
Microsoft Partner
Delta-N BV Volg ons:
Laan van Waalhaven 450 Twitter: https://twitter.com/DeltaNBV
2497 GR Den Haag Facebook: www.facebook.com/pages/Delta-N-BV
085 – 487 52 00 Blogs: www.delta-n.nl/blogs-medewerkers
info@delta-n.nl Linkedin: www.linkedin.com/company/delta-n
www.delta-n.nl Slideshare: www.slideshare.net/deltanbv

Mais conteúdo relacionado

Mais procurados

Gavin Coughlan (Boost)

AgileNZ Conference

Many of us will chose to implement Agile, yet only a small minority of companies will realize its true benefits. We risk our reputations, our company resources, and sometimes even our careers to make the switch. Despite the risks involved, the potential rewards of; predictable release cycles, higher quality solutions, and re-energized teams are still worth it. In this executive briefing we will review case studies of Agile transformations and learn what can be done to ensure our success.

WHY MOST AGILE TRANSFORMATIONS FAIL; What every executive wished they knew be...

The Braintrust Consulting Group

Release wednesdays and the agile release train upload

Chris Smith

Incorporating Scrum in a Traditional PM Environment - PMI Nashville PDD May 2015

kmegaw

The presentation will show how Root Cause Analysis (RCA) can be applied in way that it supports reaching the business goals of an organisation. It is based on collected data of RCA sessions (done for several years) and the impact on business results, and analysing this data together with non-quantitative information. This has lead to effective RCA methods, applied at specific points in the processes, with significant business results. Also the role of RCA in Total Quality Management and Statistical Process Control is explained, including how RCA used results from Orthogonal Defect Classification for maximum result. Finally, RCA as a pragmatic implementation of the CMMI Causal Analysis & Resolution process area, is elaborated.

The Business Benefit of Root Cause Analysis, Ben Linders, SM/ASM Conference 2003

Ben Linders

Exec Overview to Agile-Scrum

LeanAgileTraining

A surprising amount of companies is still using antiquated techniques like resource pools. Not only are they costly, but also hinder productivity and effectiveness. Business people wait for weeks and months to get a 20-minute job done? Not uncommon with resource pools. Feature teams, on the other hand, do have certain characteristics providing the organisation to get things done big time: supported by product owner and team facilitator, self-organised and cross-functional, stable, dedicated, and proactive. This session shows a path from resource pools to feature teams via self-selection of teams, including common fears and doubts during this culture-changing journey.

Resource Pools - How is This Still a Thing? at LAST Conf 2016 in Melbourne, A...

Bernd Schiffer

Strength in Numbers: Improving from the Bottom-Up

KaiNexus

"Essentially, all models are wrong, but some are useful”. This quote captures the fact that, in the complex world of IT, we need the best insights and methods Agile, DevOps and Lean IT offer to drive radical improvement. About Mike Orzen: Mike Orzen has been learning and applying lean and continuous improvement for over 25 years. Considered a pioneer in the field of Lean IT, Mike is co-author of Lean IT: Enabling and Sustaining Your Lean Enterprise which was awarded the Shingo Prize. Last year, he co-authored a second book The Lean IT Field Guide which provides a deployment framework to make Lean IT transformation a reality. An internationally recognised consultant, coach and keynote speaker, Mike is an advisor and instructor with the Lean IT Association, an assessor with The Shingo Institute for Operational Excellence and faculty member of the Lean Enterprise Institute. He also teaches at several universities. A lifelong learner of lean and IT, Mike coaches C-level leaders, managers and transformation coaches in several different industries. As President of Mike Orzen & Associates, he works with organisations to leverage lean thinking while emphasising respectfully engaging people, improving business process capability and leveraging technology to enable a culture of enterprise excellence.

Connecting the Dots: Agile, DevOps, Lean IT - Mike Orzen - AgileNZ 2017

AgileNZ Conference

Scrum Alliance - Certified Agile Leadership - New Certification!!!

The Braintrust Consulting Group

Applying Agile Team Management

Huan Ho

2016 Ohio State COE LSW Presentation

Nikola Cica

Managers and the land of the lost

AgileDenver

Driving Change with Data: Getting Started with Continuous Improvement

LeanKit

How Leaders Can Support Lean Using Leader Standard Work with GoLeanSixSigma.com

GoLeanSixSigma.com

Many Agile practitioners are comfortable working iteratively in small slices once there’s a basic foundation, but struggle with where to start on a new project, product, or other big idea. Participants in this session will learn how to use Richard’s Feature Mining technique to find early slices of any big idea that provide value, learning, and risk-mitigation. Agile For All clients have used this successfully for all kinds of software products, for combined software and hardware systems, and even beyond software in such areas as park construction and office remodeling. In some cases, projects with apparent significant up-front infrastructure requirements were able to ship a valuable slice to customers after just one or two sprints.

Finding the First Slice

AgileDenver

Lessons learned from managing a distributed agile team

AgileDenver

Agile ncr ppt

AgileNCR2016

The Atlassian User Group (AUG) program built a culture of community that includes over 130 groups around the world and continues to grow 60% YoY, thanks to a team of passionate volunteer leaders and members. Building a focused and motivated team across the globe isn't easy, but we'll share the foundation to the user group community's success along with take-aways for attendees looking to build successful teams of their own. In this unique session, we will highlight the Atlassian User Group culture by presenting elements of a real user group event and provide meaningful information for attendees, including the opportunity to sign up and experience the user group team culture themselves.

Atlassian User Group Insights: AUGment your Teams and Culture

Atlassian

Coaches in agile show different stances from coaching, mentoring, and teaching. Webinar Agenda: • Group exercise • What is coaching? • Mentor stance • Coaching stance • Teacher stance ============== Follow us ============== Website: http://xpdays.org Linked In: https://www.linkedin.com/company/xpdays Facebook: https://www.facebook.com/xpdaysorg Twitter: https://twitter.com/xpdaysorg

Coaching stances

XPDays

Mais procurados (20)

Gavin Coughlan (Boost)

WHY MOST AGILE TRANSFORMATIONS FAIL; What every executive wished they knew be...

Release wednesdays and the agile release train upload

Incorporating Scrum in a Traditional PM Environment - PMI Nashville PDD May 2015

The Business Benefit of Root Cause Analysis, Ben Linders, SM/ASM Conference 2003

Exec Overview to Agile-Scrum

Resource Pools - How is This Still a Thing? at LAST Conf 2016 in Melbourne, A...

Strength in Numbers: Improving from the Bottom-Up

Connecting the Dots: Agile, DevOps, Lean IT - Mike Orzen - AgileNZ 2017

Scrum Alliance - Certified Agile Leadership - New Certification!!!

Applying Agile Team Management

2016 Ohio State COE LSW Presentation

Managers and the land of the lost

Driving Change with Data: Getting Started with Continuous Improvement

How Leaders Can Support Lean Using Leader Standard Work with GoLeanSixSigma.com

Finding the First Slice

Lessons learned from managing a distributed agile team

Agile ncr ppt

Atlassian User Group Insights: AUGment your Teams and Culture

Coaching stances

Destaque

Buy-in from professionals is crucial to make changes succeed in organizations. Many improvement programs fail when professionals are insufficiently involved during the changes. Agile retrospectives can be used to do continuous and lasting improvements in organizations. They are owned and done by the teams, who decide when, where, and how they will change their way of working. This is why agile retrospectives are a sustainable approach for improvement. We need to uncover better ways to do improvements in organizations. Use an iterative approach for change with short-cycled improvements and frequent feedback to learn how to improve and get better in doing it. Agile retrospectives are a better way to do continuous improvement. Teams decide when, where, and how they will change their way of working, in stead of having the changes dictated by managers or quality/process people. Retrospectives give power to the teams and help them to become self-organized. My first book Getting Value out of Agile Retrospectives – A Toolbox of Retrospective Exercises contains many exercises that you can use to do retrospectives, supported with the “what” and “why” of retrospectives, the business value and benefits that they can bring you, and advice for introducing and improving retrospectives.

Sustainable Improvement through Agile Retrospectives - AgileEE 2015 - Ben Li...

Ben Linders

http://www.benlinders.com The presentation will show how Root Cause Analysis (RCA) can be applied in way that it supports reaching the business goals of an organisation. It is based on the results of an investigation done after applying RCA for several years. This has lead to effective RCA methods, applied at specific points in the processes, with significant results. Also the role of RCA in Total Quality Management and Statistical Process Control is explained, and RCA as a pragmatic implementation of the CMMI Causal Analysis & Resolution process area is elaborated.

Experiences using Root Cause Analysis for Improvement, Ben Linders, European ...

Ben Linders

The agile manifesto proposes that a “team reflects on how to become more effective”. Agile retrospectives can be used to inspect and adapt the way of working. They help teams to become agile by deploying agile practices in an effective way and continuously learning and improve themselves. This talk explains the “what” and “why” of retrospectives and the business value and benefits that they can bring. Examples will be given of exercises that you can use to facilitate retrospectives, supported with advice for introducing and improving retrospectives. It is based on the successful book Getting Value out of Agile Retrospectives which is published on InfoQ, Amazon, Leanpub. Retrospectives are a great way for teams to improve their way of working, to become more agile and lean. Getting actions out of a retrospective that are doable, and getting them done helps teams to improve continuously and deliver more value to their customers.

Learning to Become Agile, with Retrospectives - QCon London 2015 - Ben Linders

Ben Linders

Why, what, an How of Agile Retrospectives - Lean Kanban Benelux 2015 - Ben Li...

Ben Linders

Writing a book by two people who never met each other face 2 face when they wrote, published and promoted the book is an amazing experience! Having it translated by self organized agile teams all around the world makes it awesome!!! Come and hear how we did this and what made it work, and learn how you can effectively work with people all around the world. In 2013 Luis Gonçalves and I wrote the book Getting Value out of Agile Retrospectives. We did this by working together fully remote. We self-published it in December 2013 and gained many readers worldwide. We never met each other in person until April 2014, and are still collaborating to promote the book and helping teams worldwide to get more value out of doing agile retrospectives. In 2014 we started with teams of volunteers all around the world to translate our book. Working remotely with people that you don't know, from different cultures, with their own ways of working, and on different continents is certainly challenging, but it turned out to be an effective and fun way to do it! Join this session to learn: - how you can get to know people and work together remote, i.e. without meeting face 2 face; - which tools you can use to collaborate and communicate when working remote together; - how you can translate a book with self organized distributed agile teams of volunteers; - and how value, trust and respect can make it all possible.

Valuable Agile Retrospectives: The Making of - XP Days 2014 - Ben Linders

Ben Linders

Need for Continuous Improvement in Agile - 1stconf Melbourne 2016 - Ben Linders

Ben Linders

Becoming Agile and Lean in Process Improvement - UNICOM - Ben Linders

Ben Linders

The Ericsson Operational Development & Quality team has managed to introduce a new Management System with a process baseline, rolled out measurements throughout the organization using a Balanced ScoreCard approach, and kept up a focused continuous improvement program. This presentation shows how (obstacles, KSF, results). At all times, management has made clear that they need control of all aspects of the operation. With a collaborated approach of management and Operational Development (OD), the balanced scorecard was introduced. OD has streamlined target setting, monthly reporting, and quarterly management reviews. The monthly report has been enhanced from a figures only report to full analysis, action definition and forecasting per reported target, involving the line by means of feedback interviews. A Management System was introduced, moulding and optimizing the existing organisation structure, authorities, and policies. With this management system, the set of processes was reduced, and process support was re-enforced. A continuous improvement program was continued, with more focus on organizational targets. Existing tools like audits, root cause analysis, and improvement sessions were used to extract vital few actions together with line and project management; the resulting actions were tracked to completing by the OD team. Key success factors have been the management commitment & active support, the drive of the OD & Quality team, and the build up of skills and knowledge that was needed to implement the changes. Cross-organizational co-operation was stimulated, and management was involved through the monthly reporting & feedback cycle. This presentation will give examples of this, and hints & tips on how to exploit these key success factors in your own organization. The result is an efficient organization, capable of running projects and supporting activities in a largely quantitative managed way, meeting the required business results.

Agile Quality: maximize results with a small quality team, Ben Linders, Europ...

Ben Linders

The agile manifesto proposes that a “team reflects on how to become more effective”. Agile retrospectives can be used to inspect and adapt the way of working. They help teams to deploy agile practices in an effective way and to continuously learn and improve themselves.But sometimes teams struggle to figure out what an agile retrospective is? And they wonder how they should do them? This presentation explains the “what” and “why” of retrospectives and the business value and benefits that they can bring. It shows several exercises from the book "Getting Value out of Agile Retrospectives" to help you to facilitate retrospectives, supported with advice for introducing and improving retrospectives. Retrospectives are a great way for teams to improve their way of working, to become more agile and lean. Getting actions out of a retrospective that are doable, and getting them done helps teams to learn and improve continuously.

Doing Valuable Agile Retrospectives -ATBru 2014 - Ben Linders

Ben Linders

Adopting agile often doesn’t go as smoothly as expected in an organization. The road to agility can be hard to travel: You can’t plan your journey up front and there will be surprises along the way. Becoming agile is a learning process which requires that you reflect regularly and adopt your way of working, finding better ways to travel. Ben Linders will explore what teams, agile coaches, Scrum masters, and managers can do to be prepared for a journey to agility, what to pack and how to decide which road to follow along the way. This talk will help you to successfully deploy ideas and practices that you’ve learned at the conference.

The road to agility - AgileEE conference 2016 - Ben Linders

Ben Linders

Change Using your Strengths: That's a change!

Ben Linders

Wouldn’t it be nice if you had more insight in product quality, during development? To estimate defects inserted in the product, and check how effective test is in capturing defects? We developed a model to measure defects from requirements to customer feedback after release. It is used to control projects (putting quality next to planning/budget), evaluate risks, and decide on release and support. Baseline data is used to measure and improve process performance.

Controlling Project Performance by Using a Defect Model - SEPG NA 2008 - Ben ...

Ben Linders

Becoming agile is a journey, which can be difficult to travel. Assuming that you know why you want to become agile (a first but crucial step) you start looking for ways how to get there. Questions like "what do you want to keep from your current way of working" and "what would you like to change" will come up. Then the next question is "what are ways to do this". There isn't a silver bullet or standard route to become agile, you have to find your own way. A fixed route description won't help you. You need an "agile map" that inspires you with ideas and suggestions on where to go on your journey. The Agile Self-Assessment game is here for you to travel your agile journey. Come play the Agile Self-Assessment game in teams to discover how agile you are and what you can do to increase your agility. Players will receive a link to download the card game so that they can play it in their own organization (CC BY-NC-ND 3.0 License).

Agile Self-assessment Game - XP Days Benelux 2016 - Ben Linders

Ben Linders

The agile manifesto proposes that a “team reflects on how to become more effective”. Agile retrospectives can be used to inspect and adapt the way of working. But sometimes teams struggle to figure out what an agile retrospective is? And they wonder how they should do them? Retrospectives help teams to deploy agile practices in an effective way and to continuously learn and improve themselves. The retrospective facilitator (often the scrum master) should have a toolbox of retrospective exercises, and be able to pick the most effective one. This presentation explains the “what” and “why” of retrospectives and the business value and benefits that they can bring. You will experience several exercises that you can use to facilitate retrospectives, supported with advice for introducing and improving retrospectives. Retrospectives are a great way for teams to improve their way of working, to become more agile and lean. Getting actions out of a retrospective that are doable, and getting them done helps teams to learn and improve continuously.

Spice up your agile retrospectives - LKFR14 - Ben Linders

Ben Linders

The agile manifesto proposes that a “team reflects on how to become more effective”. Agile retrospectives can be used to inspect and adapt the way of working. Retrospectives help teams to deploy agile practices in an effective way and to continuously learn and improve themselves. Ben Linders, co-author of Getting Value out of Agile Retrospectives, will talk about the why and how of agile retrospectives, with much practical tips, stories, and examples. Ben will also give a workshop on Valuable Agile Retrospectives on October 22.

Spicing up Agile Retrospectives - Agile Tour London 2015 - Ben Linders

Ben Linders

Keynote Need for Continuous Improvement - Agile Tour Kaunas 2016 - Ben Linders

Ben Linders

Wouldn’t it be nice if you could have more insight into the quality of a product, while it is developed, and not afterwards? Would you like to be able to estimate how many defects are inserted in the product in a certain phase, and how effective a (test) phase is in capturing these defects? To optimize your test phases regarding focus and effort in relation to how many defects they will find? This presentation will show a simple but very effective model that makes it possible: The Project Defect Model. The aim of the Project Defect Model is to track product quality, take corrective actions and reduce quality risks. To get more insight into the quality of the product during development, it is needed to measure the software development processes with two views: Introduction and detection of defects. Introduction is done during the specification, design and coding phases; defects are either introduced into documents or into the actual product. Detection of defects is done via inspections and test during all the phases of the project. A tool was developed using a spreadsheet. The purpose of the tool was to estimate the number of defects per phase, and to track all defects discovered in inspections and tests against these estimates. The tool supported analysis of the data with both calculated values and graphs comparing actuals to estimates in terms of current status and trends over time. The Project Defect Model has been beneficial to projects. It has helped estimating, planning, and tracking quality during the project, including an estimate of the the number of defects left in the released product. The quality data has been used in the project together with time and cost data, to take better decisions on test, review and inspections, and design. Also it has identified quality risks at an early stage, helping the project take corrective actions and decisions on product release and maintenance capacity planning. Finally the model provided insight into the effectiveness of the verification activities, supporting effective process improvement. Paper: The presentation is on a defect planning/tracking tool and approach. Focus will be upon: • Goals: What was the purpose of the model, why developed, what did we want to reach? • How: Show the definition of the model and its implementation and application. • Tools: The tool that was developed to implement the model, how it works, strengths. • Results: How did the model and tool help the project? Did it live up to its purpose? • Success factors: What were key issues that we have dealt successfully with? • Future: How is this model used in future projects, what could further increase its benefits?

Controlling Project during Development with a Defect Model, Ben Linders, ICST...

Ben Linders

This presentation will show how to apply the CMMI in a business focussed way, by doing frequent assessments. Goals are input to the planning of assessments, a matrix is used to assure both organisation and process area coverage, and the results of assessments integrate smoothly within operational targets of existing groups within the organisation. Practical tools support the frequent assessments, and experience with the CMMI is used to optimize the assessment and improvement cycle, resulting in continuously improving the performance of the organisation towards its goals.

Reaching Business Goals with Value Adding CMMI Assessments, Ben Linders, Euro...

Ben Linders

How could you maintain quality and organizational efficiency, when the quality staff is reduced? What can you do to optimize improvement effort, and contribute to organizational results? How do you keep up morale in difficult times? This presentation will show a continuous process of keeping focus, involving people from line and projects, collaboration, and communication. The approach was driven by strong needs from management, and implemented based on values and key success factors of the company. The results are better control, increased performance, and meeting organizational targets.

Agile quality: Maximize results with a small quality team - PSQT 2005 - Ben L...

Ben Linders

The agile manifesto proposes that a “team reflects on how to become more effective”. Agile retrospectives can be used to inspect and adapt the way of working. Retrospectives help teams to deploy agile practices in an effective way and to continuously learn and improve themselves. Ben Linders, co-author of Getting Value out of Agile Retrospectives, will talk about the why and how of agile retrospectives, with much practical tips, stories, and examples. Ben also gives full-day workshops on Valuable Agile Retrospectives.

Spicing up Agile Retrospectives - Agile Practitioners 2016 - Ben Linders

Ben Linders

Destaque (20)