As part of the regular maintenance for teams at Pivotal we have weekly retrospective meetings, or “Retro”s.buy ultram online
For those of you that are not familiar, it is an hour long meeting which provides a space for open communication on how the team is doing. A retro is an opportunity to discuss what is working and what is causing pain of confusion. During the discussion, everyone identifies items that make them feel happy, confused, or unhappy.buy diazepam online without prescription
Retros are helpful for developers, who get to step away from the code for a while, as well as for product managers and designers, who can learn how to best enable the developers.valium online no prescription
Though there are many best practices for running a retro, I personally do one additional thing different… I start with the positives.buy tramadol without prescription
Traditionally, the first round of comments allows for every individual to add a comment to any of the three categories (Happy, Confused, Unhappy). When I run a retro, before that round starts, everyone has to contribute one item to the “Happy” column.soma online no prescription
There are two main benefits I see from doing this.
First, it provides the high level perspective that even though many items will end up in the other categories, at least there are some good aspects of the current situation.
Next, it provides the opportunity for someone who was going to add something to as confused or unhappy to see that the same exact item might actually be making someone else happy.adipex online without prescription
Comments and thoughts are appreciated…
Would this work in your retro?
Are there reasons why you think this is a bad idea?
What additional benefits are there to starting with the positives?