Achieving system optimisation goals in LeSS Large-Scale Scrum(LeSS) has incorporated deep Systems Thinking ideas in its recommendations. Whether it’s the way Sprint Review is done or the recommendations around team co-ordination, LeSS recommends system optimisation over local. In this short…
This post is cross-posted from the Odd-e page at their blog Decouple Line Organization from Requirement Area After almost 10 years, I got chance again to work on a LeSS Huge adoption. Facing different challenges and reflecting on my experience…
Interview with Venkatesh Krishnamurthy in CA DevOPs Perspectives. First published in DevOps Perspectives, edition 4 “In this age of agile development, there’s an uncomfortable reality that needs to be acknowledged and that is that large scale development is still with…
I will be conducting a Nexus workshop in Boston on November 17-18, with Richard Hundhausen and Rob Maher, based on the Nexus Guide. Of interest to many, SDK, API architectures, and remediation Scrumbles, and DevOps. Many Scrum teams deliver a “done”, potentially shippable increment…
It is good practice to first write large user stories (commonly known as epics) and then to split them into smaller pieces, a process known as product backlog refinement or grooming. When product backlog items are split, they are often…
Descaling Organizations with LeSS Scrum is a successful and widespread framework, but at some point almost everyone started to talk about scaling. Large organizations want to spread this miracle and Agilize everyone. Many consider agilizing large organisations as bad, and…
Cross-posted. Find the original at the SolutionsIQ Website at this link Thanks for taking the time to read (and watch) this introduction to LeSS (Large-Scale Scrum)! If you prefer video to text for an introduction to different aspects of LeSS,…
This post is cross-posted from the Gosei page at their blog Comparing LeSS and SAFe Both Large-Scale Scrum (LeSS) and Scaled Agile Framework (SAFe) have a history with Nokia and use it as a reference. What most people do not…
Scaled Professional Scrum is based on unit of development called a Nexus. The Nexus consists of up to 10 Scrum teams, the number depending on how well the code and design are structured, the domains understood, and the people organized.…
The following was originally published in Mike Cohn's monthly newsletter. If you like what you're reading, sign up to have this content delivered to your inbox weeks before it's posted on the blog, here. Product backlog refinement—sometimes called product backlog…