Now that you have your repo up, it's time to get some issues filed so that you can organize your workload. If you need help getting started, feel free to take a look at my list of sprint planning suggestions, or ask me during class. A good issue should have the following characteristics:
It should be specific. What are you doing/researching/fixing? Vague issues are no help for planning.
It should contain a single problem, instead of combining multiple problems that must be solved.
It should provide context around the problem, including information about which user story it addresses and possible starting places.
The issues you put in do not have to be immediately assigned, or be for this week. For example, you might put in additional issues as "stretch goals" to take on if your team gets through its planned sprint tasks with time left over. As each person picks up a task, they should assign the issue to themselves. Issues created during/after sprint planning should be assigned to the person who agreed to take them on.
Remember, I will be paying attention to your issues, and they should be referenced in your planning/retrospective documents. This part of the class is not optional. Good luck!
art-con-carne
commented
10 years ago
Now that you have your repo up, it's time to get some issues filed so that you can organize your workload. If you need help getting started, feel free to take a look at my list of sprint planning suggestions, or ask me during class. A good issue should have the following characteristics:
The issues you put in do not have to be immediately assigned, or be for this week. For example, you might put in additional issues as "stretch goals" to take on if your team gets through its planned sprint tasks with time left over. As each person picks up a task, they should assign the issue to themselves. Issues created during/after sprint planning should be assigned to the person who agreed to take them on.
Remember, I will be paying attention to your issues, and they should be referenced in your planning/retrospective documents. This part of the class is not optional. Good luck!