[Editors note – this is a long an obscure article that made sense to me and some people I explained it to. If it is not making sense half way through abort rather than continuing … it either makes sense early on or does not make sense at all]
I was running an agile course on how to facilitate good work in agile teams. We had some great discussions about conflict being good and people being unleashed to create value rather than being held back by managers who try to control them to force them to add value.
But then we had a less comfortable conversation. Someone asked what you do with someone who is being a [bad person] in an agile team.
Continue reading “Dealing with baddies on agile projects”
I went through this quick meeting with an agile class recently and I said I would post this for the crew to refer back to.
In agile teams there are a couple of core roles and then the rest depends on the kind of work the team does. But we can give some more clarity than this, as I have previously discussed here.
Even so, the role of the Scrum Master or Product Owner or Tech Lead or even others will vary from project to project and even sprint to sprint.
So I often have people sit down together and actually tell each other what they think they are in the team for. Essentially I get them to go through these questions that I got from a book called “Stand Back and Deliver.”
Continue reading “Clarifying agile roles – speed dating?”