I've made this interesting picture about Scrum. It shows the product backlog, product owner, sprint backlog, team and definition of "done" in one clear picture.
I think I'll make it in a powerpoint and add to my standard training material.
Recently, while discussing with a potential client, I learned of their interest in adopting a Product Operating Model. This prompted me to study the concept in greater depth. It wasn’t my first encounter with Marty Cagan’s work; I had read his book Inspired long time ago and have
Baseline vs. change is an important distinction in product development. Missing that contributes to a common misguided practice in creating RAs (Requirement Areas) around product modules. Product module is about baseline, while RA is about change. Instead of creating RAs around product modules, we create RAs around product changes. Let’
I have often been explaining how a LeSS adoption gets started on various occasions, so I decided to write it down as an article, not to avoid doing it any more - I will still do it as the interaction alongside it is irreplaceable - but to make it a
I have advocated to balance framework focus with experiment focus in the use of LeSS. As the framework focus is already strong, I’d like to elaborate more on the experiment focus. Is it possible to adopt LeSS without adopting its frameworks? I think yes, as that is actually continuous