Introducing the Zombie Scrum Symptom Checker

Is your team suffering from Zombie Scrum? And if so, what can you do to improve? Do you wonder how other teams work with Scrum? How many members they have? What the usual length of a Sprint is? Is Scrum really helping teams deliver value to stakeholders faster and making them happier as a result? Find out with the first version of the Free Zombie Scrum Symptoms Checker.

The mission of our app “Our mission with this app is to use an empirical approach to better understand how teams and organizations work with Scrum, what it makes possible for them, what enables or impedes their success and how to better support them.“

Other content:
Based on a scientific approach
Receive your team’s profile
Open-source data and replication
Next steps for our research
Give it a try!

Author = Christiaan Verwijs (Scrum.org)

https://www.scrum.org/resources/blog/introducing-zombie-scrum-symptom-checker

Fight Zombie Scrum!
Link to the Free Online Tool to Diagnose your team

Author = The Liberators

https://survey.zombiescrum.org

8 tips for better agile retrospective meetings

Here’s how to get more positive results from your retro meetings, and build a stronger team while you’re at it.

What’s a retro supposed to look like?
When retros implode

8 tips for better retrospectives

  1. Amplify the good! Instead of focusing on what didn’t work well, why not begin the retro by having everyone mention one positive item first?
  2. Don’t jump to a solution. Thinking about a problem deeply instead of trying to solve it right away might be a better option.
  3. If the retrospective doesn’t make you feel excited about an experiment, maybe you shouldn’t try it in the next iteration.
  4. If you’re not analyzing how to improve, (5 Whys, force-field analysis, impact mapping, or fish-boning), you might be jumping to solutions too quickly.
  5. Vary your methods. If every time you do a retrospective you ask, “What worked, what didn’t work?” and then vote on the top item from either column, your team will quickly get bored. Retromat is a great free retrospective tool to help vary your methods.
  6. End each retrospective by asking for feedback on the retro itself. This might seem a bit meta, but it works: Continually improving the retrospective is recursively improving as a team.
  7. Remove the impediments. Ask how you are enabling the team’s search for improvement, and be prepared to act on any feedback.
  8. There are no “iteration police.” Take breaks as needed. Deriving hypotheses from analysis and coming up with experiments involves creativity, and it can be taxing. Every once in a while, go out as a team and enjoy a nice retrospective lunch.

Author = Catherine Louis

https://opensource.com/article/18/3/tips-better-agile-retrospective-meetings

Retromat

Retromat is a great free retrospective tool to help vary your methods.

https://retromat.org/en/

8 steps to a Definition of Done in Jira

DoD = Definition of Done = a clear and concise list of requirements that software must adhere to for the team to call it complete.

8 steps to a Definition of Done in Jira

  1. Create a DoD in Jira
  2. Break it down
  3. Make it Global
  4. Manage it over time
  5. (No 5)
  6. Make the product owner responsible and the team accountable
  7. Enforce it
  8. Create an acceptance criteria list in Jira

Author = Dave Meyer (Atlassian)

https://www.atlassian.com/blog/jira-software/8-steps-to-a-definition-of-done-in-jira

10 Tips For Creating Agile Personas

Personas are a powerful technique to describe the users and customers of a product in order to make the right product decisions.

  1. Get to Know the Users
  2. Keep your Personas Concise
  3. Distinguish User and Buyer Personas
  4. Choose a Primary Persona
  5. Make your Personas Believable
  6. Focus on the Main Benefit or Problem
  7. Connect Personas and User Stories
  8. Visualise your Personas
  9. Don’t Forget to Adjust Your Personas
  10. Recognise when Personas are not Appropriate

Author = Roman Pichler

https://www.romanpichler.com/blog/10-tips-agile-personas/

A Simple Persona Template

Personas are a great way to capture our knowledge about the users and customers and their needs. But writing effective personas and providing enough but not too much information can be challenging. This blog post introduce a simple yet powerful template that helps you write great personas.

Author = Roman Pichler

https://www.romanpichler.com/blog/persona-template-for-agile-product-management/

PDF | Persona Template

Download Persona Template

Author = Roman Pichler

https://www.romanpichler.com/tools/the-persona-template/