Again, more often than not.
What can you do to make sure transparency is used to your (and the teams) advantage?Realize that transparency is a good thing. Really. That being said, some enterprises do not accept transparency within their culture (see above). If you are starting a Scrum team in a heavy command-and-control environment, where the leaders (Chickens) are rewarded for acting that way, you may have a tough ride up the hill. Let’s assume for a moment that your environment is that perfect little happy place where transparency is embraced. How would that look?
The team understands the impact of transparency and can communicate it to the outside stake-holders (Chickens). The team has been trained by the ScrumMaster and learned by “doing” Scrum what transparency means. It has learned that they can indeed expect middle managers and muckity-muck executives to actually attend stand-ups, understand a burn-down chart, and participate in a Sprint Review. Wow. And it has learned it through trial and error, working with both the Product Owner and ScrumMaster in communicating with the outside stake-holders I affectionately call “Noise.” It is not like the comic strip above, where you can request anything — or anyone. But Scrum is set up to help the team ask for help from the Chickens when the team realizes this is necessary.Not the other way around. Think about it. Close you eyes and imagine the above scenario in the two different ways it could play out. I’ll be here when you get back. Go.
Welcome back (smile). What questions did that bring up in your mind? Now, what are you going to do to answer them?
I will have some suggestions in another article.
The story continues soon. Come back for more….As you can tell, the site is starting to reach some regular feel to the delivery and content presented. Please send comments, questions, criticisms, ideas, or whatever here. You can also enter The Scrum Community to discuss this cartoon and other Scrum topics. Thank you!
October 16, 2006