This post describes the steps necessary for customising the Issue Types on your own instance of Jira. The Jira documentation on Atlassian’s own Confluence Wiki is very comprehensive but I found that it was a little verbose for each action and yet at the same time it doesn’t actually indicate the full set of steps you may need to go through in order to get everything working as you would expect.
This sprint retrospective activity can be particularly useful when you feel your team is facing a lot of blockers/impediments. It helps teams identify the issues that they are facing and encourages them to develop a plan for tackling those issues.
This is a version of the basic ‘Stop-Start-Continue’ sprint retrospective activity which can be used when there is a particular need to keep tight control over timings. Each step can be strictly time-boxed and you can adjust the time allotted in each section to suit your needs.
This sprint retrospective activity is a fun way of identifying a team’s strengths and weaknesses and is based on the ‘Cool Wall’ segment of the the TV show ‘Top Gear’. In this activity, various aspects of a scrum team’s practices are presented by the scrum master and the team vote on how ‘cool’ they feel they are when it comes to that specific topic.
This simple activity can be used at the start of a sprint retrospective meeting in order to gauge people’s moods and to help the team empathise with each other.
This sprint retrospective activity is designed to help teams think of issues from the perspective of other members of the team whilst also highlighting problems and opportunities for improvements for the team.