100 Practices to Form Your Dream Scrum Team

by Avienaash Shiralige

Today I would like to share few practices that I have seen working wonders to teams following scrum. Not all the practices are followed by all the scrum teams. But by and large you see highly successful teams has many of them from this list.

Below is a mind map which you can download to see in it a bigger view or click zoom after you click on the image to see larger view.

I would like to hear from all of you regarding what else you would like to add to this list or modify any of them. Depending upon your feedback I will update this diagram and share updated version of this for everyone to use.

On purpose, I have not included XP practices just to keep focus only on Scrum.

What practices you would like to see or have experienced in your dream scrum team? Please write to me in the comments section.

Scrum Team Best Practices

About Avienaash Shiralige


Avienaash Shiralige is an Agile Coach, Trainer, Business Optimisation and Agile Transformation Consultant @ AgileBuddha. He has been on senior leadership positions in various companies and comes with very rich 17+ years of experience in product and service companies. He has consulted companies in India, US, Europe and Australia on Agile/Scrum/Lean/Kanban and successfully set-up various distributed agile teams across timezones. He can be reached at avienaash@gmail.com.

{ 2 comments… read them below or add one }

Olaf Lewitz August 6, 2012 at 12:26 pm

Avie,
thank you for collecting this comprehensive list.
I would hesitate to call these “best practices” as this assumes they would be applicable in all or most Scrum teams. Complexity science tells us (cf. Cynefin model, for instance) that best practices only exist for “simple tasks”, where we know the best solution in advance. Most issues a Scrum team is dealing with do not belong to that space. We need experimentation, good practices that work in a specific context, and emergent solutions that are questioned to get better every day.
Let me illustrate with a few examples:
- remaining estimates on tasks: what if your team decides not to need tasks any more because they collaboratively finish a story every day?
- everyone answers three questions in daily scrum: what if your team decides to try a “walk the board” approach? Or to change the questions so that they can more quickly get to a tactical plan for their day?
- planning poker: what if they decide they don’t need to estimate because they achieved a single piece flow of small enough stories?
Some of the things you mention are quite generic (and these I find more important):
- team members ask for help (before they actually need it)
- demo shows working application
- team delivers after every sprint
I’d focus on these more generic achievements, and for the more specific ones, be clear on what we want to achieve instead of what we expect the team to do.
Does that make sense?
Take care,
Olaf
Olaf Lewitz recently posted..Magnificence Mantra

Reply

Avienaash Shiralige August 6, 2012 at 5:00 pm

Thanks Olaf for sharing your thoughts. I agree with your points, changing title to practices. I liked examples that you have shared.

Avie.

Reply

Leave a Comment

{ 9 trackbacks }

Previous post:

Next post: