Remote workshop Icebreakers & warmup activities – Remotely Interesting Ep5

👇ICEBREAKERS👇
05:03 🧻Toilet paper crusher or folder – Rakesh Kasturi
08:44 🧑‍🎨Art Remake – Margriet Buseman
12:29 🖌️Draw your Teammate – Robert Skrobe
15:21 🎨 Draw what teamwork looks like – Mehmet Karakus
18:14 🤔What is in the box GIF tournament – Sandy Lam
20:58 🐦Squiggle Birds Twist – Jason Ruud
26:19 🪑Grab a Seat & Marching Band – Andy Davis
31:39 🔢Bingo – Mardea Gartee

Agile Resources

I came across Andy Bacon his blog that lists some interesting articles and resources, you can find it here: https://andybacon.com/agile-resources/

And just in case he ever decides to take his website offline, here is a quick mirror 😉

Some Agile Basics

Agile Related Certifications

Scaling Frameworks

Retrospectives

Daily Scrum

Scrum Graphics

Checklists

User Stories

Role of Managers in Agile

DiSC Assessment (free)

Games

Metrics

Estimation, Data Driven Estimates, and Forecasting

Collaboration Tools

Happiness

Podcasts

Product Owner Resources

  • Opportunity canvas
  • Lean canvas
  • Product vision
  • Product roadmap
  • Release plan

Random Helpful Things

Technical Topics

Building the Team Manifesto

The following text was copied from: https://www.scrum.nl/blog/building-team-manifesto/

Every time a new team is formed, it takes time to grow from a group of people to a well-functioning team. In their journey to become a high-performing team, they need a shared understanding of the principles and values of each individual and the team. The most important principles and values can be summarized in a team manifesto, a social contract among the team members. A team manifesto is always built by the team itself. It contains a set of norms, values and behaviors that forms a solid ground for collaboration within the team.

Building the Team Manifesto

With every team I coach, one of the first things we do is building a team manifesto. Recently, I did this by using the Retrospective format ‘That guy, this guy’. The results were great! Therefore, I would like to share this workshop format with you.

  1. Plan a timebox of 60 minutes with the entire team
  2. Bring flip charts, sticky notes and markers with you
  3. Create two flip charts with: ‘Don’t be that guy…’ and ‘This guy rocks!’
  4. Explain to the team what the goal of this session and a team manifesto is
  5. Ask the team members to write down characteristics associated with ‘that guy’ (the person that you don’t want in your team) and ‘this guy’ (the person that is a perfect team member) on sticky notes, individually and in silence
  6. Let the team members explain what they wrote down and collect the sticky notes on the flip charts
  7. Consider to cluster the characteristics, if there is a lot of overlap
  8. Ask the team members to prioritize the characteristics, by dot voting on the ones they value the most for the team (every team member gets five dots to divide among the items)
  9. Select the five to seven most important characteristics
  10. Divide the team in three groups and give each group a set of characteristics
  11. Ask the groups to describe what each characteristic means for the team
  12. Let each group explain what they wrote down and adjust this with the feedback from the other groups
  13. Summarize all parts of the team manifesto on one flip chart and invite each team member to commit to it, for example by writing down their signatures
  14. Make sure the team manifesto is visible at all times

A team manifesto ensures that the team coherence improves. It is a common understanding about the desired behavior within the team, and what it means for them to be a team. Since the team has ownership over the team manifesto, team members will behave according to it and encourage others to do the same.

Additional examples can be found here:

by Barry Overeem

How To Kickstart A Great Scrum Team (10 practical things to do)
by Christiaan Verwijs

Retrospective: Do The Team Radar

Since it’s such a tried-and-true format, there are plenty of articles on the Team Radar, with advice and emphasis added based on the author’s position and involvement with teams. Christiaan Verwijs of The Liberators approaches the subject from a facilitation perspective with a Scrum Master-y stance in 2017’s Retrospective: Do the Team Radar, while Petra Wille’s 2019 article The Secret Weapon of Retrospectives – the Team Radar over on Mind the Product is clearly written from a product managerial perspective. Use the best of both for your team’s next (radar) retrospective.

How I Used the Spotify Squad Health Check Model

The ‘Squad Health Check Model’ is an approach that visualises the ‘health’ of a team. It covers areas like teamwork, fun, easy to release, learning, the health of codebase. While discussing the different health indicators, the team builds up self-awareness about what’s working and what’s not. The broad selection of questions helps expand their perspective. Perhaps they were well aware of the code quality issues but hadn’t really thought about the customer value perspective, or how fast they learn. It also provides a balanced perspective, showing the good stuff as well as the pain points.

Read how Barry Overeem usde the Spotify Squad Health Check Model in this article: https://medium.com/the-liberators/how-i-used-the-spotify-squad-health-check-model-f226c6fe0fdb

Road to PSMIII

Sjoerd Nijland has written a nice series of blogposts about his road to PSMIII:

Definition of Scrum
https://medium.com/serious-scrum/definition-of-scrum-2d1f224256c

Empiricism: Transparency
https://medium.com/serious-scrum/empiricism-transparency-33adad8fbba2

Empiricism: Inspection, Part One
https://medium.com/serious-scrum/empiricism-inspection-part-one-cc4cd8bf98a8

Empiricism: Inspection, Part Two
https://medium.com/serious-scrum/empiricism-inspection-part-two-fafb785bd0c0

Empiricism: Adaptation
https://medium.com/serious-scrum/empiricism-adaptation-975f044a09b2

Scrum Values
https://medium.com/serious-scrum/scrum-values-1203813e0220

The Scrum Team
https://medium.com/serious-scrum/the-scrum-team-75b8004a4bc2

The Scrum Master
https://medium.com/serious-scrum/the-scrum-master-729e223f4b64

The Scrum Master’s responsibilities
https://medium.com/serious-scrum/the-scrum-masters-responsibilities-7ee05cae707e

The Product Owner
https://medium.com/serious-scrum/the-product-owner-6b7a63fef8fe

The Development Team
https://medium.com/serious-scrum/the-development-team-575d69054a9b

The Sprint
https://medium.com/serious-scrum/the-sprint-40d0ccc895f9

Sprint Cancellation
https://medium.com/serious-scrum/sprint-cancellation-c9a9c66e8c99

Scrum’s Artifacts
https://medium.com/serious-scrum/scrums-artifacts-6f07abfab11

The Product Backlog
https://medium.com/serious-scrum/the-product-backlog-7aec7daf844f

Estimation
https://medium.com/serious-scrum/estimation-103de626551e