Outcome Based Product Backlogs in Large-Scale Scrum
Many organisations are struggling to setup outcome based Product Backlog for their teams, they were stuck in output or scope based backlogs before and kept that behavior. Even though scope isn’t a bad thing, understanding its link to business outcomes and what assumptions are behind is (to me) better. I do address this working with Product […]
How to run multi-site Scrum events without tooling?
Today I am frequently working with larger organisations and continually have to deal with people in different locations across the country or globe. This kind of context brings its own challenges and many people hope to find solutions in tooling and so did I, but hey, did I think wrong! Before going into running multi-site events, a […]
20 New Year’s Resolutions for Scrum Product Owners
The end of the year is nearby, time for some New Year’s resolutions! As I experienced a lot of stress within the role of Scrum Product Owner, and as I know you’re busy, I’m going to help you get started… Here are 20 New Year’s resolutions to get you started: Update the product’s vision (or […]
Prioritize with your stakeholders – Innovation Games® Buy a Feature
Back in the old days, I took up the role of a Agile Product Owner within a Healthcare environment and soon discovered that “responsible for setting priorities”, as it is announced in Agile literature, does not mean that doing it by yourself is the right approach. Not surprisingly, we see and hear about similar settings […]
Tooling: How to manage your to-do’s over multiple projects?
In previous article “The Product Owner Iteration – Limit Your WIP” I described one way for a person to manage his/her work on a 2-weekly basis and avoid generating waste in the system. This time I will give you a simple spreadsheet to support you with: – Requirements management that avoids generating waste – Team […]
The Product Owner Iteration – limit your WIP
As the teams are having 2 week iterations to build solutions to problems, the Product Owner has 2 week iterations as well to produce just enough new detailed input for his/her team as the team can handle within a single iteration. The rest is all about communication, collaboration and transparency towards the results and planning […]