With the excitement from the ice breaker, moving to the retro activity I found we were more engaged. I am a gamer at heart and found out one of them enjoy the same game that I love.īy doing this I get them going and hopefully start building a more trusting/transparent relationship. As a result, I started getting to know them beyond as a colleague. I know the game mechanic might be flawed but we tried to make it our own. Once we identified the person or he/she revealed them self, they would then provide the back story of the word. We would then draw a word attempt to guess who it belongs to. For this, I make sure we have 15 mins ice breaker activity for each retro to get our blood moving.įor example, the last retro I put together a game, each team member write up a word in a sticky that resonated with them. We communicate well and get the job done but have our guards up. I notice because our team is relatively small and have been hit with many restructure many of us do not truly know one another. Secondly, I attempted to make the retro ceremony our own and unique to the team. Anyways, I ensure each activity are time bound with purpose. I notice our retro over the course of the years have become a stale and chore-like activity and some feel it was an unnecessary activity that we follow because that is what the team thought agile should function. Firstly, I tried to be more prepared and organized for the meeting. I am in the same boat as you and ponder about the same thoughts. I'm starting to feel like I'm getting a good understanding of estimation, complexity, and when a story is really a cluster of stories". Should it have? How could it have gone differently? Another example: "I knew we were going to break down that 13 story into a bunch of 1's and 3's. You can talk about why unheeded advice didn't "take". Did it come true? Did it not come true? Was it good or bad? Examples: "Dave said on the 3rd day of the sprint that we would regret trying to do this in COBOL. Point out something you (the person) said. You can / should do this as both variations. Everyone says "I hate to say I told you so", but everyone secretly LOVES to point out when they predicted something. I told you so: This one can generate a lot of laughs and some embarrassment "Oh, I can't believe I acted that way four weeks ago". Time machine: If we could go back to day X at the beginning of the sprint, knowing what we know now, what could we do differently? You could pick days during the sprint, days right before the end of sprint, the day a particular story was written, the day of sprint planning etc. And by the way, I have no problem doing the same Retro activities over again, or at least frequently. My two favorite activities both point out the value of knowledge over time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |