This is the fourth article in the series of seeing system dynamics in organizational change. In this and next articles, we are going to look at one specific change in the large-scale product development organization: de-scale to scale. This means to simplify the organization to achieve agility, and this is
This is the third article in the series of seeing system dynamics in organizational change. Even though we have agreed on the change vision and is progressing during the norm, we lose the plot when crisis comes. During the norm There is always a gap between our change vision and
This is the second article in the series of seeing system dynamics in organizational change. We shall learn where the local optimization comes from, and how important it is to define a clear system optimizing goal and use that to guide the change. Local optimization "It is more cost-efficient
I have written a series of blogs focusing on seeing system dynamics in organizational design. Now, i'd like to start a new series, focusing on organizational change. In this first one, let's understand three common problems in organizational changes: 1. change stalls after it is initiated,
Zooming out and seeing the big picture is a form of systems thinking, and we see how it helps to understand Scrum roles. Distributed project management "Distributed project management" is a very powerful exercise regarding Scrum roles. We start to write down all project management tasks in post-it
As part of the LeSS trainer application, I was asked to give a graphical representation of LeSS. Here's the result showing my view of LeSS. A series of choices LeSS is a series of choices for the large-scale product development. We could make any choice if we were
[Team Leader = TL; Product Owner = PO; ScrumMaster = SM] The real Scrum requires significant organizational redesign. I have seen two common settings to pilot Scrum: 1) project group and 2) component team, as those are existing structures thus convenient to just use them. However, without organizational redesign, you could not adopt
This sounds like an easy choice in Agile development, however, single-functional team such as testing team is still prevalent in many organizations. There are forces favoring in it. By understanding the factors and dynamics behind different choices, we make more informed decisions. Efficiency & Quality vs. Cycle time Why do
Two years ago, I wrote a blog article called "Revisit feature team". I felt not quite complete, thus, the thought went on, until I discovered what was missing recently. Collective ownership Let me recap the scenario here. There is one so-called feature team, in which small groups work
In part 1, we looked at the case of platform as product. Now, we are going to look at the case of product area as product. Those products all have customer views, but there is possibility to define a broad product, then the products become product areas in the broad
What is the product? This is a critical question in organization design. You define the product narrowly or broadly, and the scope of the product is a continuum. We are going to see the factors and dynamics behind different choices in two parts. In part 1, we shall look at
One important leverage in coaching Agile teams is to increase the focus on requirement, rather than task. This article describes the dynamic behind it. Traditional project tracks the progress at two levels. One level is the milestone, which is often associated with stages such as requirement analyzed, ready for integration,