Conversations
It is very easy to get lost in emails and instant messages and all the other forms of communication available to teams today. As such, we can easily lose focus and forget what we're supposed to be doing, or have endless discussions that never seem to result in any decisions being made. Scrumly includes a Conversation feature that allows the team to have a much more structured conversation focused on making a decision.
Begin a Conversation
A good Title and Description
Conversations are usually for asking a question, and if so, the Title can be a great place to enter a clear, simple form of the actual question that needs to be answered. The Description is a good place to explain some background information that may be relevant for the team to understand before being able to participate in the discussion. It is recommended to be clear and focus on one question at a time. It allows for a more focused discussion and makes it easier to make a decision.
Conversations are usually for asking a question, and if so, the Title can be a great place to enter a clear, simple form of the actual question that needs to be answered. The Description is a good place to explain some background information that may be relevant for the team to understand before being able to participate in the discussion. It is recommended to be clear and focus on one question at a time. It allows for a more focused discussion and makes it easier to make a decision.
Provide some proposals
When possible, enter some Proposed Solutions to help the team understand their options. This also makes it easy for the decision maker, as they can simply accept one of the Proposed Solutions rather than have to type it all out themselves. When creating a conversation, you can optimally enter the first Proposed Solution, but more can be added from the Conversation Summary page at any time.
When possible, enter some Proposed Solutions to help the team understand their options. This also makes it easy for the decision maker, as they can simply accept one of the Proposed Solutions rather than have to type it all out themselves. When creating a conversation, you can optimally enter the first Proposed Solution, but more can be added from the Conversation Summary page at any time.
Propose the conversation to the team
Before other team members can see this Conversation, you must Propose it to the team. You can do this while creating it, or from a saved draft. Creating a Conversation that is not proposed to the team creates a draft which can be refined until it is ready to share with the team.
Before other team members can see this Conversation, you must Propose it to the team. You can do this while creating it, or from a saved draft. Creating a Conversation that is not proposed to the team creates a draft which can be refined until it is ready to share with the team.
Determine who should decide
You can assign a Conversation to one or more individuals who are responsible to make a decision. If you do not assign it, then you are responsible to make a decision, or the Scrum Master. This can be useful when you are simply capturing a question, even if you are the one who will be doing the research and answering it.
You can assign a Conversation to one or more individuals who are responsible to make a decision. If you do not assign it, then you are responsible to make a decision, or the Scrum Master. This can be useful when you are simply capturing a question, even if you are the one who will be doing the research and answering it.
Discuss as a Team
Focus on the topic
The comments provide an area for the team to discuss, as well as a historical record that can be reviewed later to get more context. It is important to stay on topic of the Conversation, and if necessary, create new Conversations with their own topic as new questions are raised that are not part of the original question being asked.
The comments provide an area for the team to discuss, as well as a historical record that can be reviewed later to get more context. It is important to stay on topic of the Conversation, and if necessary, create new Conversations with their own topic as new questions are raised that are not part of the original question being asked.
Make a Decision
Accept a proposed solution
You can make a decision by accepting a proposed solution. This can be the easiest as you don't have to repeat anything. If necessary you can edit the final decision afterwards to fine-tune the decision.
You can make a decision by accepting a proposed solution. This can be the easiest as you don't have to repeat anything. If necessary you can edit the final decision afterwards to fine-tune the decision.
Enter a new decision
You can also make a decision yourself if none of the proposed solutions seem fitting. The final decision can also be edited later if necessary.
You can also make a decision yourself if none of the proposed solutions seem fitting. The final decision can also be edited later if necessary.
Keep the Team Moving
There can be Conversations which are blocking team members from working on Tasks and Backlog Items. It is important to discuss the blocking issues quickly to keep the team on track.