in my opinion, Goals, Signals, and Measures. is a grate way for a team to create a common understanding of our goal. also we can use signals and measures to evaluate if we are in a correct direction or not.
While I am not a project leader, using the Vision Creation Play can be helpful to get my team re-aligned with our goals and with setting new ones to get people more engaged.
The play I find the best to run with a team would be Goals, Signals, and Measures as it would help out a lot with figuring what exactly everyone is looking at before letting them go for the races. It helps to keep everyone in their perspective for a project, and I personally believe this is the one me.
I plan to implement a Team Goals, Signals, and Measures Play for my small team of developers. Using Team GSM will improve the clarity between me and the team. The outcome will solve the team's misconceptions and misunderstandings and improve communication. The play can provide insight into the team's struggles and issues. I can reinforce the team's area of weakness, add sprints to attack these issues, or address to fix the problems.
I want to bring the Goal, Signal, Measures Strategy, and DACI to my team. I would like to involve the entire team in decision-making and developing a strategy for the customer that we will be adding to our scope.
I intend to implement the DACI framework with my team. This will help improve new feature request gets the right key stakeholders involved and allow for us to deliver better products.
I would implement the: How to run the Customer Journey Mapping Play. Mapping out the journey to our customer and seeing the Pain points along the way and getting those issue resolved so the customer can see where the final product will be is a big goal.
I’m looking forward to using DACI for upcoming projects with my group. This could help us get a better understanding of whatever project we’re working on man and our goals.
I got reminded of the DACI play. Thanks. I think having this in Confluence for the many minor decisions we make over the years, will build a great knowledge base and reduce slack chatter.
342 comments