Back to Forum

Task board for scrum masters / scrum master interaction

Last post 05:26 pm May 24, 2014 by Ian Mitchell
1 reply
Florian Straub
04:12 pm May 24, 2014

Hi there, in our company we have four scrum teams each with 100% PO and SM. Daily meetings are scaled: first the teams, then the POs, afterwards SOS with rotating team members and afterwards the scrum masters.

There are boards for SOS, the POs and the SMs. SM board is grouped by topics like "Linux know how", "recurring tasks", "method know how" and so on. I have the impression that some tasks remain open for days, if not weeks and there is no clean focus on which topics SMs should attack and and which should be delayed. All in all it feels very chaotic lately.


1. I thought about re-doing the task board as Kanban board with a limited number of work in progress items. Any experiences on this?


2. Do scrum masters even "need" to have their own board?


3. Should we only have cross-team topics/impediments there or should it be basically a copy of the impediment boards/lists of all teams?


4. I didn't find anything about scrum master interaction on the web. Any hints?


5. Is there something else about scrum master interaction you would like to share?


Thanks,

Flo

Ian Mitchell
05:26 pm May 24, 2014

The problem with boards like this is that the tickets are often very open ended, and there is no clear Definition of Done that can be applied to them.

They can be used, but you need very fine grained items that are demonstrably achievable within a short cycle time, and which ultimately add empirical value. Remember that if you can't formulate viable acceptance criteria, then the item doesn't belong on the board in the first place. The ordering of items can be approached from the perspective of risk mitigation.

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.