Author: Satya Narayan Dash

The ‘black mountain’ forced in,    broke Konark’s iron gates,Drank the water of Mahanadi river,     and ate from the golden plates. – Narrated by my parents in Odia, loosely translated into English Growing up, from the above paraphrased poem, I learned of the destruction of Konark Sun Temple in Odisha, India by “Kala-Pahada” (meaning Black Mountain), a person presumably named so for his black deeds. But what inspired and stuck with me is not the destruction of Konark (Kona meaning corner, Arka meaning sun), but its construction. Destruction is easy, construction is not. Destruction takes minutes, sometimes seconds, but great construction demands tough love, sometimes despair of not knowing the path, but still pursuing the mission. It’s painful, yet beautiful. The construction of 228-foot-tall Konark sun temple in 13th century was done by 12,000 craftsmen toiling for 12 years to build the monument. A 12-year-old boy, with his knowledge over existing Odia construction manuscripts, gave the final touch to the construction. Now, any large construction such as the stoneware in Konark, or software as built by engineers, will require scaling. It’s inevitable. This article is about the scaling of teams using the Kanban framework. In this article, we will learn how to build multiple Kanban Boards with the MS Project Agile software tool and how to use these boards across multiple Kanban teams. Scaled Scenario – Multiple Kanban Teams We have three separate teams – Team A, Team B, and Team C – working on different Kanban work items for a Home Renovation Project. All the work items are part of a single Kanban Backlog. However, the team visualizations are different. It’s shown below with various teams working on respective items. The below video [duration: 5m:25s] prepared in support of this article explains more on the foundational aspects of scaling using Kanban. To get the most out of this article, watch the video before reading the rest of this article. For the best experience, go full-screen HD mode and plug-in your earphones. The initial plan created for this Scaled Kanban Project is shown below in Task Board Sheet view. Backlog Sheet or Gantt Chart views can also be used to visualize the plan. Each team wants their work to be managed separately to avoid issues with overlapping, resource assignment and tracking. However, there can be dependencies among the work items. Hence, for each team, we will have individual boards – Team A Task (or Kanban) Board, Team B Task Board, and Team C Task Board. As we have separate boards, we need to have separate filters to segregate the team-specific tasks. Each task added into the overall project plan will have custom fields associated, e.g., if the tasks are for Team A, then they will have associated custom fields. With this background, let’s proceed and learn how these boards can be used separately by individual teams, Kanban Flow Masters (equivalent to Scrum Masters in Scrum) and Kanban Service Request Managers (equivalent to Product Owners in Scrum) to manage and track the work items. Scale the Kanban Teams for Tasks In our first step, we will create a Team custom field, taking the text custom field for tasks. You can create this field by going to Backlog Sheet (Task Board Sheet) tools > Format tab > Columns group > Custom Fields command > Task custom fields. It also can be done from the Gantt Chart tools. As shown, we have taken the Text 1 task custom field and renamed it as Team. This custom field will now have a lookup table. The lookup table can be seen by clicking on the Lookup… command button, highlighted above. In the lookup table, will have four values: After you have populated the lookup table, it will appear as shown below. Do note that the default one has been highlighted in blue. The custom field created must be associated with tasks, e.g., Team A field value will be for tasks which will be executed by Team A. Similarly, for others. I could have used individual custom Boolean flags for three teams, but then it’s not very efficient. What happens when you have three, five, or nine teams? Are you going to add nine flags? You get the idea! So, next we will associate these fields with the individual tasks of the Scaled Kanban Project. To associate, simply add the Team custom field as one of the columns in the view and choose the respective team, as depicted below. While I’ve used the Backlog Sheet, you can use any other views such as Task Board Sheet, Task Board, or Gantt Chart view. The custom field won’t be available by default as a column in the tabular part of the view, hence you have to add the related column in order to associate. Scale the Kanban Filters Our next step is to build custom filters, which will be associated with separate Kanban team boards. These custom filters will have the custom flags enabled for them. The below figure is for Team A Task Board and named as Team A Task Board Tasks Filter. To create the filter, go to View tab > Data group > Filter > More Filters… command. If you are in the Sheet views for this Scaled Kanban Project, you can select the “Highlight Filter” drop-down list as the default filter option would be disabled. For the Team A Task Board Tasks shown above: If you want, you can enable the ‘Show in menu’ highlighted above. Similarly, create two more filters for Team B and Team C as Team B Task Board Tasks filter and Team C Task Board Tasks filter, respectively. You can create the Copy command in the More Filters dialog box to quickly create the filters. After you create all the filters, it can be seen as follows.   If you have selected the ‘Show in menu’ checkbox while creating the custom filters and it’s a good idea to do so, you can see all the filters under Custom part of the list of available filters. Scale the Kanban Tables In this step, we will create three custom tables and these tables will be applied to the board views that we are going to create. We will learn the steps to create the custom views shortly. To create the tables, go to View tab > Data group > Tables > More Tables… command.  From there create a new table. The below figure is for the Team A Task Board Tasks Table. As shown: Similarly, create two more tables for Team B and Team C, which are Team B Task Board Tasks Table and Team C Task Board Tasks Table, respectively. Post creation, you will have the tables available under the custom part of Tables drop-down menu. Again, though I’ve used the Task Board Sheet view above, you can use either Backlog Sheet or Task Board Sheet view for a Scaled Kanban project. This I’ve explained in my webinar series: Practical Kanban with MS Project. Scale the Kanban Boards In our final step, we are going to create the Task Board Views for all the teams. To do so, go to View tab > Task Views group > More Views… command. From there, create a new Single View (not a Combination View) from the View Definition dialog box. As shown: Similarly, create two more Task Board views. For Team B, it’ll be Team B Task Board view and for Team C, it’ll be Team C Task Board view. Next, when you assign resources to the tasks and apply the view, the following one comes up, which is for Team C. Did you notice Team name (Team C) has been highlighted in the cards above? That’s another advantage you can have in Scaled Kanban Projects with MS Project Agile! For more detailed tracking in sheet views, one can create individual sheet views (e.g., Team A Task Board Sheet view) for each team. Such views can be created in a similar manner as we have created the board views. Demonstration: Scaled Kanban in a Practical Way Let’s have a demonstration of what we have learned so far with our practical scaled approach using Kanban to deliver a product or service. The below video [duration: 6m:50s] demonstrates scaling with MS Project Agile. Do not forget to go full-screen HD mode and to plug-in your earphones. Conclusion Pause for a moment… Go back 900 years in time and imagine what it would have taken to build something like the Konark Sun Temple with over ten thousand craftsmen. The planning, scheduling, tracking and completion would have been a colossal task. But they succeeded. Remember the 12-year-old kid that we began with? After completing his work, the young boy jumped into the nearby big ocean giving up his life to protect the reputation of others! Other craftsmen didn’t have the know-how of the final placement of the ‘kalasha’, meaning temple top. But the kid knew and made the supreme sacrifice for his team. In today’s world, however, with right learning content, certifications and project management software, one can have the know-hows and expertise. As the project manager and hence the leader of your team, many times you plan for and lead multiple Kanban teams, which can be distributed and/or dispersed. Knowing how to scale definitely helps. As we just learned, MS Project with its Kanban features is eminently capable of scaling to a number of Kanban teams. You can confidently build products or services using Scrum or Kanban frameworks available in MS Project Agile and deliver them at scale in a practical, hands-on manner. This article is dedicated to the memory of my father, the late Harendra Nath Dash, who passed away 5 years ago on June 11, 2019. He, along with my mother, Mrs. Bidyut Prava Dash, first narrated the story of Konark Sun Temple to me. The temple still stands today, nearly 900 years later and is considered to be one of the seven wonders of India. Next to Sanskrit, Odia has the highest number of ancient manuscripts, including construction, among all Indian languages. References [1] Practical Kanban with MS Project Agile, by MPUG.com [2] Online Course: Mastering MS Project Agile, by Satya Narayan Dash [3] PMI-ACP Live Lessons – Guaranteed Pass, by Satya Narayan Dash [4] Sun Temple, Konark, World Heritage Sites, by UNESCO, France [5] The Rhythmic Dance of Agile with Cadence, published by MPUG.com