Agile Scrum is easy and makes us happy
We learn Scrum through the Agile Manifesto, which teaches us to value people over tools, and through the intuitive universal Scrum Process Diagram which shows how the Scrum ceremonies, roles, and artifacts work together.
Practicing Scrum with Jira is hard and makes us sad
We need and use Jira because it is powerful and reliable but Jira was originally developed for bug tracking, not Scrum. Shoehorning Scrum into Jira causes cognitive overload because “Jira Scrum” is…
INCOMPLETE: Jira partially models the scrum process but omits major scrum ceremonies such as the retrospective, showcase, and estimation poker.
INEFFECTIVE: Jira starts with low-level stories without grounding us with the high level and universal Scrum Diagram. Thus, we must mentally maps the diagram to Jira, filling in Scrum Ceremonies not included in Jira
NON-VISUAL: Jira relies heavily on text. Visualizations are in an ancillary section outside the daily flow so many teams don’t use them enough. Moreover, the visualizations require teams to find and notice the relevant actionable meaning. They do not provide direct insights, i.e., Jira is better at the What than the So What.
See Scrum makes us happy again
The See Scrum tool augments Jira and helps teams follow the scrum process and highlights actionable insights about the health of their team and their sprints. See Scrum leverages the universal Scrum diagram to model the full Scrum process and it encourages the team to explore with interactive visualization
See Scrum looks like this
