How to track issues and its progress that occur during sprint execution. Is there any template? Will it be good practice if we put some team members name highlighting issues on his/her end?
How to track issues and its progress that occur during sprint execution.
Is there any template?
Will it be good practice if we put some team members name highlighting issues on his/her end?
Example: some time sprint is started but its difficult to always ask team members and make aware of action items that are discussed in last retrospective meetings. It may feel as if we are trying to target that person. So i need template/ or some way to tackle it which can do my work of team working on action items and also they should not be feeling bad about it.
Saving Changes...
If your team is following Scrum guidelines closely then the work they do including blockers or impediments which are not specific to a backlog work item are owned by the team not by individuals.
In practice, usually there would be someone taking the lead.
How that is reflected really depends on the team's way of working.
If they are using a work management platform, issues could be represented as just another type of work item. Alternately, they could elect to use a traditional issues log, or an information radiator such as a "pain snake" or "snake on the wall" technique.
Smita Mane Tracking sprint issues should be smooth and team-friendly. Use a simple tracker with columns for issue, owner, priority, status, and updates. Keep it open in Jira, Trello, or Excel so the team updates it themselves. Instead of pointing fingers, focus on "How can we solve this together?". Use stand-ups to check progress and support each other. A shared dashboard keeps things clear without making anyone feel targeted. Want a ready-to-use template? Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
The first thing to take into account is what method are you using. I deduced from your post that you are using Scrum. Impediments in general (risk and issues) must be part of the daily scrum or daily stand up. Lot of people continue running the event using the 3 questions that were in the old versions of the Scrum Guide without notice that from the very begining they were a proposal and they never work. Put focus on impediments and then do not make the mistake to try to solve in the daily, make a meet after. Adding to that, impediments must be a work item in your backlog because giving them visibility mainly in other events like sprint planning to take them into account in calculate things like capacity. Saving Changes...
Community Champion
