Collaboration: the action of working with someone to produce or create something. An essential skill for high performance agile and scrum teams.
Try this experiment: Give your teams time and space to play.
That’s it. Don’t expect something shippable. Don’t plan to judge their output on the basis of business value. There will be no “right or wrong.” There will be no award for “the best idea.”
How long does it take to say “Thanks….” – to express your appreciation, regard, recognition, and encouragement to a team member for something they’ve done? What the person has done doesn’t have to be a huge thing. In fact, it could be one of those tiny, everyday occurrences that may seem relatively …
How many of us look forward to the traditional annual performance review? I mean really, whether you are on the presenting or receiving side of things… it is not the highlight of the year for anyone I know. I believe there’s a better way – Team Roundtable Reviews.
One of the 12 principles behind the Manifesto for Agile Software Develop is: At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. This adjustment of behavior can take many forms: from stopping a practice that is not fruitful to simply doing more or less …
It takes many different mindsets and behaviors to make a team hum. I am appreciating a view of collaborative behaviors developed by David Kantor (as part of his work on Structural Dynamics), and am finding it useful as a way to hold up a mirror to a team that is interested in understanding and improving their communication.
