Team Member
As a Team Member, it is your responsibility to perform the necessary work to achieve the desired goals prioritized by the Product Owner.
Review the Backlog Items
Help clarify any missing details
Reviewing a Backlog Item provides a tremendous opportunity to catch any missing details or unclear expectations. Ensure that it is clear what the expectations are, and use Conversations to clarify important details. It is better to do this before the Sprint begins as it could avoid unnecessary delays when time is at a premium.
Reviewing a Backlog Item provides a tremendous opportunity to catch any missing details or unclear expectations. Ensure that it is clear what the expectations are, and use Conversations to clarify important details. It is better to do this before the Sprint begins as it could avoid unnecessary delays when time is at a premium.
Imagine how the goals is going to be achieved
It can be valuable to "imagine" how something "might" be implemented. Tasks can be created at any phase, however doing it early can sometimes help raise questions that might otherwise only have been discovered during a Sprint. If Tasks are added this early, they are focused on necessarily on actual "implementation architecture" (in software terms), but at a high level of testable units. Use the planning time to help identify anything that might need clarification.
It can be valuable to "imagine" how something "might" be implemented. Tasks can be created at any phase, however doing it early can sometimes help raise questions that might otherwise only have been discovered during a Sprint. If Tasks are added this early, they are focused on necessarily on actual "implementation architecture" (in software terms), but at a high level of testable units. Use the planning time to help identify anything that might need clarification.
Commit to the Sprint
Generally a Sprint is considered a team effort and team commitment. As such, all the Team Members will have an opportunity to review the proposed Sprint to make sure the Sprint is actually Ready to begin.
If the Sprint is Ready
Team Members are going to often be solely responsible to perform the necessary work to build the output that will be verified by the Product Owner. Before the Sprint begins can be a great time to ensure that the team has the same expectations for what will be produced by the end of the Sprint. Double-check the Backlog Items and any Tasks and confirm the Sprint is Ready.
Team Members are going to often be solely responsible to perform the necessary work to build the output that will be verified by the Product Owner. Before the Sprint begins can be a great time to ensure that the team has the same expectations for what will be produced by the end of the Sprint. Double-check the Backlog Items and any Tasks and confirm the Sprint is Ready.
If the Sprint is not Ready
Use this review as a time to ask any questions that may be needed which may impact the ability for the team to commit to completing all the items in the Sprint in the time frame given. If the Sprint is Not Ready, then say so now, and be sure to communicate why the Sprint is Not Ready.
Use this review as a time to ask any questions that may be needed which may impact the ability for the team to commit to completing all the items in the Sprint in the time frame given. If the Sprint is Not Ready, then say so now, and be sure to communicate why the Sprint is Not Ready.
During the Sprint
Focus on the highest priority
Work on the Backlog Item in the order they appear in the Sprint, as time has been taken to prioritize the Product Backlog. You'll best meet the expectations of the Product Owner by ensuring that effort is first applied to the most important items. The team should focus on completing items before moving on to new items, if at all possible. Breaking down work into Tasks can help, especially if the team can allow multiple people to work at the same time on the same goals.
Work on the Backlog Item in the order they appear in the Sprint, as time has been taken to prioritize the Product Backlog. You'll best meet the expectations of the Product Owner by ensuring that effort is first applied to the most important items. The team should focus on completing items before moving on to new items, if at all possible. Breaking down work into Tasks can help, especially if the team can allow multiple people to work at the same time on the same goals.
Staying on the same page
Keeping good notes can be very helpful to ensure that the entire team is on the same page. It also provides a good way to pick up where you left off. Leverage the Task description and comments to help keep good notes about the work that is being done.
Keeping good notes can be very helpful to ensure that the entire team is on the same page. It also provides a good way to pick up where you left off. Leverage the Task description and comments to help keep good notes about the work that is being done.
Blocked by missing information
Sometimes making assumptions can allow a team to move more quickly based on known standards. When details are subjective and unclear, this can cause a variety of results. Depending on which assumptions are made, the results may or may not meet the expectations of the Product Owner. When in doubt, it is best to start a Conversation and possibly block the current Task until the decision is made. This will likely help ensure that expectations are met when the work is all completed, and helps to avoid re-work.
Sometimes making assumptions can allow a team to move more quickly based on known standards. When details are subjective and unclear, this can cause a variety of results. Depending on which assumptions are made, the results may or may not meet the expectations of the Product Owner. When in doubt, it is best to start a Conversation and possibly block the current Task until the decision is made. This will likely help ensure that expectations are met when the work is all completed, and helps to avoid re-work.
Manage dependencies
There are times when it is discovered that one thing cannot be done until something else is done. While this causes some things to get done out of expected order, it is sometimes necessary. Also, it can often end up in doing the work once instead of in two separate places. Scrumly can track these dependencies and block one Task until another Task or Backlog Item is done first. This helps keep the whole team informed about the appearance of a diversion. It can also allow for simplification of an otherwise overly-complicated work.
There are times when it is discovered that one thing cannot be done until something else is done. While this causes some things to get done out of expected order, it is sometimes necessary. Also, it can often end up in doing the work once instead of in two separate places. Scrumly can track these dependencies and block one Task until another Task or Backlog Item is done first. This helps keep the whole team informed about the appearance of a diversion. It can also allow for simplification of an otherwise overly-complicated work.
Working through a problem
Many things cannot be anticipated in advance. We live in a dynamic world with many moving parts. It is important to handle all problems that arise in an organized way so that they don't disrupt the team and progress more than they must. Determine what problems must be solved now, and which can be deferred until after the Sprint, and keep the team focused on the goals.
Many things cannot be anticipated in advance. We live in a dynamic world with many moving parts. It is important to handle all problems that arise in an organized way so that they don't disrupt the team and progress more than they must. Determine what problems must be solved now, and which can be deferred until after the Sprint, and keep the team focused on the goals.
Finish the Sprint
The intention of a Sprint is that it has a clear beginning and end, and provides valuable end-caps for the team to plan, review and improve.
Deliver everything that is finished
The outcome of a Sprint should be that the Backlog Items which were part of the Sprint are finished and can be delivered. How these items are going to be delivered and to what audience is up to each team and project type. But delivery is important because it is the purpose for the project in the fist place.
The outcome of a Sprint should be that the Backlog Items which were part of the Sprint are finished and can be delivered. How these items are going to be delivered and to what audience is up to each team and project type. But delivery is important because it is the purpose for the project in the fist place.
Inherit any unfinished work
When a Sprint ends and there are any unfinished Backlog Items, Scrumly will automatically move those to the top of the next Sprint. The team should consider discussing this after the Sprint to try to understand whether this was due to problems, misunderstandings or just underestimated. While it may be a goal to finish everything that was started in the Sprint, look on the bright side: at least it's partially completed at the start of the next Sprint. It doesn't have to be disastrous, but since it can be a common source of frustrations since expectations were not met between the team and the Product Owner, it is best to try to learn how to improve in this area.
When a Sprint ends and there are any unfinished Backlog Items, Scrumly will automatically move those to the top of the next Sprint. The team should consider discussing this after the Sprint to try to understand whether this was due to problems, misunderstandings or just underestimated. While it may be a goal to finish everything that was started in the Sprint, look on the bright side: at least it's partially completed at the start of the next Sprint. It doesn't have to be disastrous, but since it can be a common source of frustrations since expectations were not met between the team and the Product Owner, it is best to try to learn how to improve in this area.
After the Sprint
A team needs an opportunity to reflect on the Sprint that just finished. This can include celebrations of accomplishments, sharing finished work with interested observers and stakeholders, but can also include an excellent time to review what worked and what didn't in hopes to improve the team's performance.
Review what worked well
Openly discuss what aspects of the team are working to help reinforce good habits. Provide positive feedback to team members where appropriate and honor those who performed exceptionally. This can tremendously boost team performance in future sprints.
Openly discuss what aspects of the team are working to help reinforce good habits. Provide positive feedback to team members where appropriate and honor those who performed exceptionally. This can tremendously boost team performance in future sprints.
Identify what didn't work well
You may have encountered some problems during the Sprint that caused disruption or slowed down performance. Be clear about what the problems were and how the team thinks they can be resolved. It may be a good idea to add items to the Product Backlog for the purpose of tracking any actions that are being taken to help resolve any problems. This can ensure that the team can prioritize when the actions occur and track that they did occur to help prevent the problem from happening again.
You may have encountered some problems during the Sprint that caused disruption or slowed down performance. Be clear about what the problems were and how the team thinks they can be resolved. It may be a good idea to add items to the Product Backlog for the purpose of tracking any actions that are being taken to help resolve any problems. This can ensure that the team can prioritize when the actions occur and track that they did occur to help prevent the problem from happening again.
Prepare to improve
Remember that the next Sprint is not the last Sprint, especially when the last Sprint had some problems. Head into the next Sprint with a refreshed attitude and strive for improvement in all areas.
Remember that the next Sprint is not the last Sprint, especially when the last Sprint had some problems. Head into the next Sprint with a refreshed attitude and strive for improvement in all areas.
Start the Next Sprint
This cycle continues again, and the team continues to do great things. Make each Sprint your best Sprint ever!