Retrospective Antipatterns Aino Corry @apaipi Putting speakers on - - PowerPoint PPT Presentation

▶
retrospective antipatterns
SMART_READER_LITE
LIVE PREVIEW

Retrospective Antipatterns Aino Corry @apaipi Putting speakers on - - PowerPoint PPT Presentation

Apr 08, 2024 303 likes •758 views

Retrospective Antipatterns Aino Corry @apaipi Putting speakers on stage Messing with the heads of students Making developers communicate Goals with this talk Better retrospectives Awareness of anti-patterns A surprise Retrospective

slide-1
SLIDE 1

Retrospective Antipatterns

Aino Corry

@apaipi Putting speakers on stage Messing with the heads of students Making developers communicate

slide-2
SLIDE 2

Goals with this talk

Better retrospectives

Awareness of anti-patterns

A surprise …

slide-3
SLIDE 3

Retrospective Antipatterns

Prime Directive Ignorance The Wheel of Fortune Death by Postponement Let's get it over with! In the Soup DIY Retrospectives (and 2 extra patterns)

slide-4
SLIDE 4

Anti-patterns


  • it seemed like a good solution at the time…

Problem

You need to figure out where to place the functionality of the class

Forces

You are using OO. You are experienced in imperative or functional programming

Anti-pattern solution

You place all your methods in your favorite class – the heart of the architecture.

Consequences

Your class will become extremely big It will be difficult to understand and maintain the software

slide-5
SLIDE 5

The Blob

Refactored solution

Refactor the class by merging the methods into other classes.

Strategies

High cohesion – low coupling Now known as micro services

Benefits and drawbacks

You will have a smaller class Refactoring takes time up front, but saves time later.

slide-6
SLIDE 6

Titanic A/S – reliable navigation software

Peter Nicky Jim Susan Robert Sarah

Scrum Master

slide-7
SLIDE 7

Sarah facilitates her first retrospective 


  • Week 2

Regardless of what we discover, we must understand and truly believe that everyone did the best job he or she could, given what was known at the time, his or her skills and abilities, the resources available, and the situation at hand.

Norm Kerth

slide-8
SLIDE 8

Regardless of what we discover, we must understand and truly believe that everyone did the best job he or she could, given what was known at the time, his or her skills and abilities, the resources available, and the situation at hand.

Prime Directive Ignorance

Norm Kerth

~ Developer ~ Norm

slide-9
SLIDE 9

Prime Directive Ignorance

Problem:

It feels awkward to follow the directive

Antipattern solution:

Just forget it

Consequences:

People bring all their assumptions and negative expectations to the retrospective.

Anecdotal evidence:

People do not really listen. People are afraid to go to retrospectives

Refactored Solution:

Bring the directive to each retrospective in some way

slide-10
SLIDE 10

Regardless of what we discover, we must understand and truly believe that everyone did the best job he or she could, given what was known at the time, his or her skills and abilities, the resources available, and the situation at hand.

Prime Directive

Norm Kerth

slide-11
SLIDE 11

Week 4


The next retrospective

slide-12
SLIDE 12

The Wheel of Fortune


  • symptoms and problems
slide-13
SLIDE 13

The Wheel of Fortune

Problem: We are all busy and retrospectives takes time from coding Antipattern solution: Just skip a step or two in the retrospective and get on with it Consequences: The problems that you find and suggest solutions for are only the symptoms of the real problems. Refactored Solution: Use the phase: generate insight to find the cause

  • f the problems
slide-14
SLIDE 14

The wheel of Fortune


Stages and activities

Set the Stage – getting ready Closing the retrospective –summary Decide what to do - the future Generate insights - now Gather Data – the past

slide-15
SLIDE 15

Robert Sarah

slide-16
SLIDE 16

Jim says to Robert:

How many times, have you thought: 'Boy, I sure wish there was an easier way to pick up women, like published API with code samples?' What would you say if such documentation was not only available, but succinctly put into 22 design patterns and given formal descriptions just like the ones in your GoF book?

slide-17
SLIDE 17

Decorated Visitor Honeypot

Problem You want to connect to and create conversational state with

women, but you want them to do all the work

Forces

There are women in your realm Women notice their surroundings more than men Women are skilled at obtaining excuses to start seemingly innocent conversations with men, they are interested in

Solution

Establish an appealing environment and indirectly initiate

connections initiated by others

slide-18
SLIDE 18

Decorated Visitor Honeypot

Strategies

Expose your interests (or wanted interests) The kitten/puppy angle Decorate yourself Chocolate, chocolate, chocolate

Benefits and drawbacks

Women walking by will do the work for you It can be costly You may oversell yourself…

Related Patterns

Unexpected Resource God

slide-19
SLIDE 19

The Design Pattern Book

slide-20
SLIDE 20

Week 4 – 6


Death by Postponement

slide-21
SLIDE 21

Death by Postponement

Problem: You notice a problem Antipattern solution: You wait until the retrospective to raise it Consequences: The solution is delayed, too many problems at the retrospective, not enough time to explore what is not known Refactored Solution: Raise the problem, when it occurs. Use the retrospective time to explore

slide-22
SLIDE 22

Death by Postponement


  • real time Time-Line
slide-23
SLIDE 23

Week 6 – 8

"Time for coding is more important…" "We do not get anything out of them…" "They always blame me for…" "We can do it in half the time…"

slide-24
SLIDE 24

Let's get it over with

slide-25
SLIDE 25

Let's get it over with

Problem: Time for coding is more important Antipattern solution: Retrospectives vanish Consequences: The time is saved, but more time is wasted on doing the wrong things or people leaving Refactored Solution: Restart them; get new activities, an external facilitator, follow up on actions, get management backup by pointing out painpoints

slide-26
SLIDE 26

Let's get it over with


  • ask questions
slide-27
SLIDE 27

But how is Robert doing..?

slide-28
SLIDE 28

Surprise Statefulness

Problem

You want to convince the target female that you are a package

  • f extremely desirable resources

Forces

Women view men as somewhat self-centered Women assign significant value to a man who takes the trouble to make her private data persistent

Solution

Use optimistic persistence to implement explicit storage and retrieval of her private attributes

slide-29
SLIDE 29

Surprise Statefulness

Strategies

Standard text retrieval strategy Object instantiation strategy

Benefits and drawbacks

Considerable investment up front Dirty read Corresponding high return

Related Patterns

Interested Listener - listen

slide-30
SLIDE 30

Week 8 – 10

"We always discuss the testing framework…" "The boss will never allow it…" "Why can the retrospectives not help us…" "We never get anything changed…"

slide-31
SLIDE 31

In the soup

slide-32
SLIDE 32

In the soup

Problem: "We want to work on the big problems" Antipattern solution: The actions need management approval/action Consequences: If management has different priorities, nothing happens. Retrospectives degenerate into complaint sessions, and waste of time. Refactored Solution: Stay out of the soup or come up with a least one action that the team can do something about

slide-33
SLIDE 33

Influence

In the soup


  • change, adapt, accept

Do "The Soup"

The communication with testers is bad Change the location of the company Code review all major changes

slide-34
SLIDE 34

Influence

In the soup


  • change, adapt, accept

Do "The Soup"

The communication with testers is bad Change the location of the company Come up with reasons for a local hub Code review all major changes Move closer to the testers

slide-35
SLIDE 35

Week 10 – 12

"They are a waste of time…" "The retrospectives are boring…" "We should have a better facilitator…" "I would like to get something out of them as well …"

slide-36
SLIDE 36

DIY Retrospectives

slide-37
SLIDE 37

DIY Retrospectives

Problem: Some say the Scrum master is responsible for the retrospectives Antipattern solution: Let the SM facilitate each retrospective Consequences: The SM is a bad facilitator, because he is also focused on the

  • utput of the retrospective. The SM does not get a chance to

reflect on his own situation because he is busy facilitating Refactored Solution: Take turns in facilitating in the team. Use an outsider as facilitator

slide-38
SLIDE 38

DIY Retrospectives


Rotating the Facilitator

slide-39
SLIDE 39

Retrospective Antipatterns

Prime Directive Ignorance The Wheel of Fortune Death by Postponement Let's get it over with! In the Soup DIY Retrospectives

slide-40
SLIDE 40

Goals with this talk

Better retrospectives

Awareness of anti-patterns

Dating Patterns

slide-41
SLIDE 41

What happened to Robert and Sarah ?

Robert Sarah

slide-42
SLIDE 42

Thank you for your time ☺

slide-43
SLIDE 43

Extra subjects

  • Distributed retrospectives
  • Managers in the room
  • Silent people
  • Troublemakers
  • Using the activities for other meetings
  • Personal retrospectives
slide-44
SLIDE 44

Referencer

  • http://skycoach.be/2011/05/16/agile-retrospectives-

anti-patterns/

  • http://iljapreuss.blogspot.co.uk/2009/03/

retrospective-antipatterns.html

  • Agile retrospectives – Diana Larsen & Esther Derby
  • Anti-patterns – refactoring software, architectures and

projects in crisis – Brown et al.

  • Dating Design Patterns – Solveig Haugland
  • Project Retrospectives – Norman Kerth