Shared vision on organization

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 organizational vision again in one-team Scrum context and multi-team LeSS context respectively.

One-team Scrum

In this context, organizational vision is actually team vision.

Scrum is based on empirical process control, while empirical process is guided by goals. There are three instances of empirical processes in Scrum.

  1. Daily Scrum is the empirical process applied towards sprint goal
  2. Sprint review is the empirical process applied towards product goal
  3. Sprint retrospective is the empirical process applied towards process goal

While sprint goal and product goal are straightforward, what is process goal? The embedded "process goal" in Scrum is to get potentially shippable at the end of every sprint. This lies at the heart of Scrum. Initially team may not be able to achieve this, and they use sprint retrospective to reflect and improve towards it.

Thumbnail image for shared vision - 4.jpg

Another common source of process goals comes from some assessment frameworks, either created by other people or on our own. The assessment framework is usually associated with questionnaires or checklists. The above diagram is a checklist I created many years ago for my own usage to assess team and organization. Its scope is bigger than one team, but the idea is the same. This kind of framework or checklist implies that team aims to achieve the ideal state indicated by getting full score in all dimensions and questions. If all questions are written as statement and the scores are marked based on the extent that team or organization has realized, the overall statement is essentially a team vision. Team vision describes more than processes, while getting potentially shippable at the end of every sprint is one of those processes.

Similar to product vision, here we set time-bounded team goals based on team vision, and work towards them mainly through sprint retrospective.

Who owns team vision? Though it is clearly defined in Scrum that PO owns product vision, it is less clear about who owns team vision. ScrumMaster certainly plays an important role as change agent, because team vision is closely connected to change vision. On the other hand, as team is self-managing, how much should they own team vision themselves?

Thumbnail image for shared vision - 2.jpg

This relates again to the above diagram from the book "The Fifth Discipline Fieldbook", which shows the degree of shared-ness. Similar to PO sharing product vision, SM could tell/sell/test/consult/co-create team vision with the team. These various ways of engaging team will also achieve different degrees of shared-ness. Let's elaborate on this.

Suppose that we would like to create a team vision that describes what an ideal team would look like. It could happen in the following ways.

  • [Telling] SM creates a full version and simply tells the team that this is what great Scrum team would look like. SM may borrow it from others, create it based on her own experience and aspiration, or mix multiple sources.
  • [Selling] SM creates a full version and explains why to the team in trying to convince them that this is a great team vision.
  • [Testing] SM creates a full version, explains why, and asks feedback from the team about what excites them and what does not. Then, she refines the vision.
  • [Consulting] SM creates a draft version, and asks the team to contribute. However, SM still reserves the role of judge, and she chooses to accept or ignore what the team says.
  • [Co-creating] SM does not create any version at all, and asks the team to co-create. SM may prepare some inputs for the team to reference, if they want. In this case, team fully owns the decision making, and SM only acts as the facilitator.?

The co-creation is often done through a series of team visioning workshops, which leads to shared team vision. Please note that it is not a one-time effort, but an ongoing process. Every quarter or half-a-year, perhaps during normal sprint retrospectives, team shall revisit and evolve its shared vision.

Multi-team LeSS

In this context, organizational vision spans across multiple teams.

In LeSS, there is an additional event called overall retrospective, which is the empirical process applied towards organizational goal. Organizational goals support to achieve organizational vision.

What is organizational vision? There is a LeSS guide called "Organizational Perfection Vision". Even though "a perfection vision is different from a vision. The goal of a vision is to achieve it, whereas the goal of a perfection vision is to channel improvements", the general idea of organizational vision still holds true. The vision describes a future state of organization, e.g. "able to deliver or change direction at any time without additional cost", "special coordination roles are avoided and teams are responsible for coordination", etc.

In the book "The Fifth Discipline", it defines learning organizations as "organizations where people continually expand their capacity to create the results they truly desire, where new and expansive patterns of thinking are nurtured, where collective aspiration is set free, and where people are continually learning to see the whole together". In fact, this describes a future state of organization, thus, learning organization itself is an organizational vision too.

In the book "Reinventing Organizations", it describes the advance of organizational models, and the emergence of teal organizations. Teal organization operates as a living organism or living system, with three major breakthroughs: self-management, wholeness, and evolutionary purpose. Teal organization is another organizational vision that we may aspire to.

Thumbnail image for shared vision - 3.jpg

In the above diagram from the LeSS guide "The LeSS Organization", we learn that PO provides product vision. Then, who provides organizational vision? Managers and SMs focus on organizational capability improvement, while organizational and team vision guides the improvement. Therefore, manager plays a similar role in organizational vision as SM in team vision. Managers together with SMs may provide organizational vision, by telling all the way to co-creating. Co-creation would lead to the highest degree of shared-ness. Nevertheless, the quality of organizational vision is also dependent on the quality of individual's personal vision. This is why shared vision better starts with personal vision, which is the focus of another discipline "personal mastery".

How do we co-create organizational vision? It could be similar to team visioning process, but with larger group. In those sessions, divergent and convergent steps are planned to facilitate large group. Alternatively, team visioning - what do we want to create as a team - may happen first, then, we organize the sharing sessions for teams to listen to one another, and let the shared vision emerge over time. You may find more from "shared vision" section in the book "The Fifth Discipline Fieldbook".

In product development organization, shared vision is applied to both product and organization. We have explored them in the previous article and this one respectively, and hope that it will help you practice the discipline of "shared vision" in product development organization.

Read more

Scrum master ทำแค่เนี๊ยะ

Scrum master ทำแค่เนี๊ยะ

เวลามีคนถามว่า Scrum master ทำอะไร แล้วผมตอบว่าทำให้ Scrum เวิร์คสำหรับทั้งองค์กร ซึ่ง โฟกัสหลัก ๆ 4 อย่างก็จะอยู่ที่ Product owner, ทีม, engineering practices และ องค์กร บางครั้งที่ผมจะได้ยินเสียงตอบกลับมาเบา ๆ ว่า “แค่เนี๊ยะ?” ในฐานะ

By Chokchai
how to สร้าง Knowledge Management

how to สร้าง Knowledge Management

ตอนเรียน Large Scale Scrum กับ Jurgen de Smet สิ่งหนึ่งที่ผมได้เรียนรู้ คือ ปัจจัยสำคัญหนึ่งที่ทำให้องค์กรหนึ่ง ๆ จะเร็วขึ้นได้ คือ จะต้องเรียนรู้ไปพร้อม ๆ กันได้ ซึ่งถ้าอยากทำแบบนั้นได้ก็จะต้อง share ownership

By Chokchai
โลกการเขียนโค้ด ตอน ซามูไรกับสปาตั้น

โลกการเขียนโค้ด ตอน ซามูไรกับสปาตั้น

ซามูไรที่ได้รับความไว้วางใจให้แก้ core logic จะมีสัญชาตญาณซามูไร คือแก้ตรงนี้ จับยามสามตาแล้วรู้เลยว่าจะไประเบิดตรงโน้น แล้ววิ่งไปสกัดบั๊กไว้ก่อนความเสียหายจะเกิด (ถ้าเป็นในหนัง ตอนนี้เป็นบทที่บั๊กร้องว่า “มืงรู้ได้ไง?!” :D) หลังจากที

By Chokchai
ประสบการณ์ TDD

ประสบการณ์ TDD

มันมีบางชั่วขณะ ที่ผมอินกับ Test-Driven Development (TDD) มาก จนอยากจะแนะนำทักษะนี้ให้คนเขียนโค้ดทั่วโลกที่สนใจเลย ผมคิดว่า ทักษะนี้มีผลเยอะมาก ๆ กับความรู้ความชำนาญในการเขียนโค้ดของผมทุกวันนี้ แต่ที่ผมไม่เคยอธิบายเป็นคำพูดออกมาได้คือ ทำไมนะ? เมื่อเช้าตอนกำลังอ่านเกี

By Chokchai