In my recent CSPO course, I got a question about when we should focus on the whole team (team, PO and SM), and when we should highlight different roles. Some people are somewhat confused because on one hand we define different roles and responsibilities, on the other hand we talk
I realize that LeSS is a natural way to scale. And let me illustrate. LeSS is still Scrum LeSS provides two different large-scale frameworks: LeSS for 2-8 teams and LeSS huge for 8+ teams. We focus on LeSS here. LeSS is trying to reach the same purpose as one-team Scrum
While discussing some struggles of Scrum team with my friend He Mian during his Kanban course recently, i realize that Scrum team can benefit from many Kanban practices. There are 6 core practices defined in Kanban method. They are: 1. Visualize 2. Limit Work-in-progress 3. Manage Flow 4. Make Policies
Acceptance criteria vs. Acceptance tests Recently, i had an interesting discussion with my good friend Xu Yi. We discovered an interesting difference in our way of thinking about acceptance criteria and acceptance tests. In his thinking, acceptance criteria and acceptance tests have one-to-many relationship; while in my thinking, acceptance criteria
As to this topic, I am only talking about project managers in software industry. Same thoughts may not apply in other industries. Traditional project managers There is traditionally contract game between business (or product or customer) and R&D (or IT or technology or vendor). In the beginning of
Scrum framework is based on empirical process control, i.e. you inspect and adapt to achieve the goal. In my CSM course, we do an exercise to relate empirical process control with events defined in Scrum framework. The below table is one typical outcome. Event Goal Who Information for Inspection
PO (Product Owner) is defined as single person in Scrum. However, for various reasons, in practice a team may be formed to fulfill the role of PO. I am using the term of team rather freely, strictly speaking, some of them are only working groups. I'd like to
In my recent CSPO (Certified Scrum Product Owner) course, we had a discussion exercise about how PO breaks and/or gains trust from team. I'd like to share some points so that any PO can keep those in mind while working with the team. How does PO break
The purpose of Daily Scrum is for team to inspect and adapt towards Sprint goal. The mechanics seem so simple, while in practice its purpose is often not well achieved. Here's some experiments that may help you find better mechanics to achieve purpose. * Separate "inspection" and
During Agile adoption and transformation, there's an important question of "what change do you introduce next". Approaches I see a few approaches to introduce the next change. * Adopt Scrum, which means to introduce Scrum roles - cross-functional team, PO and SM; Scrum events - planning, daily
Recently, i attended a training on Kanban. To drive continuous improvement, Kanban has its main or even sole focus on shortening the lead time. I was impressed by results from a couple of case studies shared in the training. This triggered me to think further on how improvement is achieved
Recently, I attended a workshop by David Hussman, and story mapping was one of the topics. Since I had rarely used story mapping, while didn't realize its Indispensability, it made me think of why. * Why story mapping? The introduction of story mapping technique is a response to lack