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

In this post, Christiaan Verwijs shares his experiences on how to best Kickstart, Lift-off or Launch a (new) Scrum Team.

  • Understand team development (and your role in it)
    • Forming phase
    • Storming phase
    • Norming phase
    • Performing phase
    • Adjourning phase
  • Reserve time for the Kickstart
  • Getting to know each other is half the work
  • Teach Scrum
  • Formulate a Team Vision
  • Create a Team Contract
  • Pick a Team Name
  • Set expectations
  • Retrospectives, retrospectives, retrospectives
  • Involve management to support the Kickstart
  • ‘Bring it to the team’

Read the complete article here: https://medium.com/the-liberators/how-to-kickstart-a-great-scrum-team-10-practical-things-to-do-2143bdde1a8d

A Fun Way of Giving Feedback – The 360 Dinner

How does it work?

#1: Invite your team to a nice dinner: Let colleagues know in advance this will be a special 360 Degree Feedback Dinner.

#2: During the meal you’ll give each other feedback: One person will start and the rest of the team will take a few minutes telling that person both positive and negative things. The feedback must be honest and genuine with the aim of moving people forward, not roasting them or pounding them into the ground. 

#3: The person on the receiving end can answer questions or comments and then thank everyone for their thoughts. Once that person is done move on to the next. This can take a long time so carve out a few hours.

#4: This feedback works best if afterwards each person comes up with a few takeaways/themes based on the feedback they got for what they want to improve. They should then communicate that to the team so that colleagues can hold each other to account and check in every few months to see how they’re progressing. 

Change doesn’t happen in a vacuum, in fact when we tell people we’re trying to change it happens 90 percent faster than if we don’t tell anyone.

The Team Manifesto: the foundation every team needs

Ideally, teams get the chance to select their own members, organize a kickoff and define a strategy to reach the given goal. Most of the time teams are created top-down and there’s no time available for a decent kickoff. Teams just start with the realisation of the project and everything seems to be going smoothly. But when the first serious impediments arise the foundation of the team will be tested. Teams with a solid foundation will also struggle in the beginning but survive and become stronger than before. Teams without this foundation might also survive after a harsh period, but chances are they fall apart and the project is killed and the team dissolved.

The first step in becoming a solid team is establishing a solid foundation. This foundation consists of a shared vision about teamwork and the required quality standards.

For this purpose, creating a team manifesto is the ideal instrument. It is an agreed way of working among the team members that ensures mutual understanding. Years ago I got inspired by this blog post, since then I’ve changed it slightly to fit new insights. With every team I start, creating the team manifest is the first thing I do, success guaranteed!

The steps are:

  1. Set a time box of one hour. Pick a flip over, some sticky notes and markers
  2. Ask the team the question ‘What does team mean to you?’
  3. Let them answer this question in silence and write it down on a sticky note. One answer per sticky note.
  4. Gather all notes and ask the team members to present it to each other
  5. Cluster the ideas and identify and prioritise the themes by voting
  6. Write down ‘Team Manifesto’ on a A3 poster and the 5 most important themes on the left side
  7. Give the team some time to brainstorm about the other extreme of the earlier defined themes. For example: the extreme of ‘fun’ might be ‘boring’.
  8. Write down all the extremes on the right side of the poster with in the center the word ‘above’.
  9. The last important step is to invite everyone to affirm their commitment to the team manifesto by writing down their signature below the poster.
  10. Make sure the team manifesto is well visible in the team area.

The same exercise can be done by posing the team the question ‘what does quality mean to you?’ This creates awareness about the required quality and stimulates craftsmanship.

What are the advantages of creating a team manifesto? Read the full article here: https://medium.com/the-liberators/the-team-manifesto-the-foundation-every-team-needs-c1d72ccfe689

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

Asking the right questions; how to help a Scrum Team switch from a technical to a functional Backlog

One of the biggest challenges for a Scrum Team is to switch from a technical to a functional perspective on their work. Christiaan Verwijs has developed a set of helpful questions that often trigger teams into a functional frame of mind.

  • Why is it important that we implement this?
  • What problem of stakeholders and/or end-users do we solve by doing this?
  • What personas benefit from this, and why? (given that you have personas)
  • How would sales explain the benefits of this to customers and/or users
  • What reasons would an end-user have to want this?
  • How would you explain this to a colleague who is not part of this project?
  • How would you explain this to your spouse, at home, after a hard of work?
  • What would you show during the review to demonstrate that this is working?
  • If you are a user, how would you test if this works?
  • What changes would a user notice after implementing this?
  • What stakeholders benefit from this, and why?
  • If we wouldn’t do this, what would end-users and or customers miss or be unable to do?
  • What compliment would a happy user of customer give after delivering this?
  • How would you explain this to a potential end-user?
  • What steps would you go through in the application to test if this works?
  • If we’d put this in release notes that will be read by end-users, how would we announce it?

Read the original article here: https://medium.com/the-liberators/asking-the-right-questions-how-to-help-a-scrum-team-switch-from-a-technical-to-a-functional-bee6c1598487