JIRA is everywhere. Everyone talks about it, everybody wants it, but not everybody can have it – why is that? In my first article, I announced that a series of articles will follow in which Scrum tools will be reviewed. This blog entry is the first of many in which I will evaluate currently available … weiterlesen →
Category Archives: Scrum Artefacts
Advanced Christmas Tree Decorating
With Christmas just around the corner I was able to experience a really nice “Retro”. “Retro” in quotes, as not all elements were there, but in this case that was not so important. What was valuable was the respect shown for work completed by individual team members. This meant a lot of preparation time for … weiterlesen →
Definition of Done / Level of Done / Constraints
The last couple of days I experienced how difficult the topic of Definition of Done can be. I was confronted with many misunderstandings, ambiguities and confusing thoughts. We differentiate between three different aspects that are logically separated from each other: Level of Done – The Level of Done describes the achievable degree of completion of … weiterlesen →
Impediment Backlog | Sources to fill my Impediment Backlog
The Impediment Backlog is a living document, which reflects what the ScrumMaster does for his team. He continually updates this Backlog carefully. Where do the items for this ever changing Backlog come from? Results of the retrospective provide important and valuable items. The Daily Scrum puts pressure on the ScrumMaster every day. Long walks New … weiterlesen →
Start with the Why
A common model for writing UserStories is the UserStory after Mike Cohn [1]: As Who do I want What, so that Why. For example, “As a consultant I want to publish articles so I become famous.” When working as a ScrumConsultant for bor!sgloger I find time and again that the UserStories of our customers usually … weiterlesen →
5 min on Scrum | Business Value
Luke Hohmann has explained in his article “Why Prioritizing Your Product Backlog for ROI Doesn´t Work” [1] that it is necessary to priorize a backlog item: “identify stakeholder preferences, understand which backlog items align to corporate strategy, and demonstrate which backlog items drive profit.” Whether you go along with his ideas, which he is stating … weiterlesen →
Scrum Tools | Tobias Mayer wrote about the Taskboard
This is a review and a comment about the great article of Tobias Mayer: “The Heart of Scrum.” [1] “The longer I teach and coach Scrum, the more I become convinced that the task board is the heart of Scrum. Without the task board there is no center, no focus, no hub.” I completely agree. The … weiterlesen →