The previous article was written in an analytical manner, while in this article I will supplement it with an experience during the time of Nokia Networks. As it happened more than ten years ago, some details may not be as accurate as I would like them to be, but I
Recently, I ran across my old article "PO on team or PO on feature?" written about ten years ago, and found that it could be connected to the topic of limits to one product backlog. My thinking at that time touched some factors, but was still vague. Over
[RA = Requirement Area; PBI = Product Backlog Item.] In LeSS Huge, there is an additional scaling technique called RA. How to define RAs has confused many practitioners. This article tries to open a perspective. By which dimension? By which dimension do we define RAs? We know that RA is customer centric.
Our goal is to have one product backlog and all teams are working in its priority order to maximize the customer value. Our current reality is that each team has its own backlog and the so-called one product backlog is actually a collection of many backlogs. A desired backlog In
In large-scale product development organization, %(people in special roles) is a good indicator for the degree of self-organization in teams. Special roles in this measure are outside teams. There is no special role inside teams, as everybody takes the role of team member. Sometimes, the team may define "special
Frameworks as starting point If you look at the LeSS complete picture, you see that the frameworks - defined by the rules - and the principles are at the heart of LeSS. However, this is not completely true. In fact, the LeSS frameworks emerged out of the experiments, in response
Shared vision is one of the five disciplines practiced in learning organization. This is the second article on how this discipline relates to product development organization, and it is about organizational vision. You may want to read the first one about product vision as well. Let's look at
Shared vision is one of the five disciplines practiced in learning organization. I shall write two articles on how this discipline relates to product development organization. This one is on product vision, and the next one will be on organizational vision. Let's look at how shared vision relates
Context There is a rule in the LeSS Huge framework - "LeSS Huge adoptions, including the structural changes, are done with an evolutionary incremental approach". In the 3rd LeSS book, there are three related guides for LeSS Huge adoption. * "evolutionary incremental adoption" * "one requirement area
I have written a series of articles that apply systems thinking to explore various organizational design options and change strategies. The goal of this primer is to prepare you for understanding and practicing systems thinking. Besides describing basic concepts, we shall use examples in product development organization to help see
This is a session I planned to give in LeSS meetup in Apri, Agile 2020 in July, LeSS 2020 in Sept., but could not make any of them due to the COVID-19. Next attempt will be LeSS meetup in Sept. Thought that the ideas might be useful, thus, put the
Note: This article was originally published as an experience report in Agile 2011. Abstract Manager as Scrum Master? You can not do that! It goes against the conventional wisdom, which assumes command and control managers cannot lead and coach as Scrum Masters. However, as an important aspect in Agile change,
Once a team responsible for "A" (be it a function, component or customer domain) grows too big, we split it into two teams, responsible for the subsets of "A" (the left side). Why is it so natural to do this, rather than the alternative - we
I often got this question - what do you measure while adopting Agile? The conversation usually went like this: [me] What is about adopting Agile? [him] ... doing Scrum. [me] What effect do you expect after adopting Agile? [him] higher efficiency. [me] How would you define higher efficiency? [him] ... finishing more
In my previous series of article "#backlogs and multi-learning", I wrote that "the agility is to deliver highest customer value in uncertain environment. With uncertainty, the ability to deliver is not sufficient, we need the ability to inspect and adapt, in order to deliver highest customer value&
The discussion in this article assumes that we apply Scrum in large-scale (i.e. multi-team) product development, which is probably 90% of cases. Scrum adoption Scrum implies the change in organization design. The star model by Jay Galbraith defines five aspects of organization design. Let's put Scrum in