tag:blogger.com,1999:blog-194522122024-02-06T20:31:50.507-06:00Zen, Product Management, and LifeA look at how we deliver value, incorporating diverse ideas that can be applied to organizations.Bob Tarnehttp://www.blogger.com/profile/09907970828978458221noreply@blogger.comBlogger353125tag:blogger.com,1999:blog-19452212.post-28298565117531417282023-03-11T11:51:00.000-06:002023-03-11T11:51:45.265-06:00What is a Team<p></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjdwdLyVCa6uyoldKbFuyCG8lW6G7cz75_rlYLFRU4EJVMCERgGkh7FASCjYZitNjAIdioH_ClTDBAUgiUYpH6No8xB1Eog05Ymhv-UQaJ64NAOKzsRQdkEBS-HFNepLJmb20j4Y36g1WBoJxF-8CHBl2PY_ZhE5BG4ynqbtIK5BCnFWM1BtA/s1024/people%20running.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" data-original-height="1024" data-original-width="1024" height="200" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjdwdLyVCa6uyoldKbFuyCG8lW6G7cz75_rlYLFRU4EJVMCERgGkh7FASCjYZitNjAIdioH_ClTDBAUgiUYpH6No8xB1Eog05Ymhv-UQaJ64NAOKzsRQdkEBS-HFNepLJmb20j4Y36g1WBoJxF-8CHBl2PY_ZhE5BG4ynqbtIK5BCnFWM1BtA/w200-h200/people%20running.png" width="200" /></a></div><br />The last couple posts have focused on teams, but I haven't addressed a basic question; What is a Team? <p></p><p>I ran cross-country in college, so I was on the team, but was it really a team? On days we had meets, it was really everyone for themselves out their on the course. Once we left the starting line, I would see little of my other teammates until we all finished the race. I could have completed without the rest of my team, and it wouldn't have had an impact on my performance. Sure, we had a coach shouting encouragement, but having a coach doesn't make us a team. </p><p>I recently came across the book <a href="https://www.amazon.com/Leading-Teams-Setting-Stage-Performances/dp/1578513332/ref=sr_1_1?crid=8CUB37UYM70T&keywords=leading+teams&qid=1678555124&s=books&sprefix=leading+team%2Cstripbooks%2C186&sr=1-1" target="_blank">Leading Teams</a> by J. Richard Hackman. In the book, he outlines the five conditions that need to be in place for a high-performing team. Among the list is the idea that it has to be a "real" team. He defines this as meaning the team has shared responsibilities, clear boundaries, and stable membership. </p><p>I have worked with more than one team where there was no shared responsibility. Each person had their own role. User stories were assigned to the person that knew how to complete that specific type of work. When I encounter a team like this, my first inclination is to start pairing people on work. In the short run, it makes the team less productive but in the long run the team becomes more agile because each person has built additional skills and they don't get stuck because only one person can complete a certain task. </p><p>Boundaries are important because it keeps the team from being inundated with work. In <a href="https://www.amazon.com/Team-Topologies-Organizing-Business-Technology-ebook/dp/B09JWT9S4D/ref=sr_1_1?crid=2E8GC28LEBEUH&keywords=team+topologies&qid=1678557037&s=books&sprefix=team+topologies%2Cstripbooks%2C117&sr=1-1" target="_blank">Team Topologies</a>, Skelton and Pais talk about cognitive loads. If you put to much work on a team, it diminishes their ability to deliver, just like to many things in my "doing" column causes me to suffer from task-switching. </p><p>Clearly, there has been a lot written on teams. Going back to the example I started with, my cross-country team doesn't fit into the category of a real team, but a basketball team would. If we start looking at our work teams thru the lens of Hackman, we can start seeing how we can build more effective teams. </p>Bob Tarnehttp://www.blogger.com/profile/09907970828978458221noreply@blogger.com0tag:blogger.com,1999:blog-19452212.post-76038494676846345282023-01-22T12:16:00.000-06:002023-01-22T12:16:44.573-06:00What is the Right Team Size?<p><table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="float: right; margin-left: 1em; text-align: right;"><tbody><tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjHH77ueAeyyakv3uHkpGcoKORM4LPaZYJCXLXfN9gD3n8qQWIqxx-XJgSNDaU_nfcVaO6e7ULK4vFs7WhuX_Ti58ZrNOw375ZCYrwKch6uHh90ZjcAq0uctW57SZRMSVmDPRHRvMcon8PZ1Gb5VpwpvXmEqxBNsiyqsI_n2i6jRuR102YClA/s1024/DALL%C2%B7E%202023-01-22%2012.28.15%20-%20sketch%20of%204%20people%20of%20mixed%20gender%20standing%20around%20a%20blackboard%20with%20computer%20code%20on%20it.png" imageanchor="1" style="clear: right; margin-bottom: 1em; margin-left: auto; margin-right: auto;"><img border="0" data-original-height="1024" data-original-width="1024" height="200" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjHH77ueAeyyakv3uHkpGcoKORM4LPaZYJCXLXfN9gD3n8qQWIqxx-XJgSNDaU_nfcVaO6e7ULK4vFs7WhuX_Ti58ZrNOw375ZCYrwKch6uHh90ZjcAq0uctW57SZRMSVmDPRHRvMcon8PZ1Gb5VpwpvXmEqxBNsiyqsI_n2i6jRuR102YClA/w200-h200/DALL%C2%B7E%202023-01-22%2012.28.15%20-%20sketch%20of%204%20people%20of%20mixed%20gender%20standing%20around%20a%20blackboard%20with%20computer%20code%20on%20it.png" width="200" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;">Team in front of Computer Code, generated by DALL-E 2</td></tr></tbody></table><br /> What is the right size for a team? Can it be too big or too small? I worked with a team once that had 3 developers. They spent most their time mob programming in front of a 42 inch monitor, taking turns at the keyboard. They didn't need to do traditional stand-ups because they were swarming around one thing at a time. The Scrum Master kept an eye open for impediments, but otherwise was focused on the next thing that would improve the team's productivity. </p><p>I also worked with a team of 15. My first thought was that was too big, but as I watched the team work, I saw that wasn't the case. The team was doing data-science kind of work. They needed people who could write SQL to pull data from legacy systems and put it in data lakes and people who could take that data and package it in a report with Tableau. For this team, having all the skills on one team meant they didn't have dependencies with other teams. </p><p>An <a href="https://en.wikipedia.org/wiki/The_Magical_Number_Seven,_Plus_or_Minus_Two" target="_blank">often cited paper by George Miller </a>states the magic number at 7 +/- 2 people (sometimes referred to as Miller's Law). The 2-pizza rule says a team should be small enough to feed with 2 pizzas. <a href="https://www.sciencedirect.com/science/article/abs/pii/004724849290081J">Robin Dunbar's research</a> suggests 15 is the upper limit of the number of people we can deeply trust. </p><p>There are other considerations beyond just the number of people. As I pointed out in my last post, dependencies slow teams down. My 15 person team was big, but still effective at delivering because they didn't have dependencies on other teams. </p><p>This larger team also had true cross-functional skills. My smaller team was effective because they were developing in a narrow field and didn't need a broad range of skills. However, if they found they were having dependencies on another team because of a missing skill, enlarging the team to include this skill could be a smart move. </p><p>In the book <i><a href="https://teamtopologies.com/book" target="_blank">Team Topologies</a></i>, Matthew Skelton and Manuel Pais talk about cognitive overload. Teams can only handle a limited number of different areas of focus. If the team is asked to do too many different types of work, the effectiveness of the team will suffer. Just like individuals can't multi-task effectively, neither can teams. So when deciding on the team composition, this should also be taken into account. My 15 person team was probably suffering from cognitive overload, but I wasn't looking for that at the time. </p><p>Too often I see teams put together without much thought. Worse yet is when people are partially allocated to more than one team. I think regardless of what framework or methodology you are using, you need to start off with deliberate thought about how to set up teams. I would recommend the book <i>Team Topologies</i> for guidance on this topic. </p>Bob Tarnehttp://www.blogger.com/profile/09907970828978458221noreply@blogger.com0tag:blogger.com,1999:blog-19452212.post-11928386291437727962023-01-04T16:18:00.000-06:002023-01-04T16:18:37.741-06:00Even the Best Chefs can't make a bad recipe taste good; why someone else's Agile Transformation recipe may not work for you<p></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi_Q7kRM7q4FQKCnjZ1cVJGDW8u7XuhXOtMyay5XuRePqRBrEW88UxgqQAiAoYC_u5YRvLYM20Q0J1qnCD-3sPshyiBFEewuHtFYwaI16B0P51N5vZanKXgRwdXmso_xCYVREg86ALBJrClYFFsSHfMiVdmBNy53kHsHOZWzR2jBrehGe29IA/s1309/MarchingBand%20-%203%20(1).jpeg" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" data-original-height="1309" data-original-width="1133" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi_Q7kRM7q4FQKCnjZ1cVJGDW8u7XuhXOtMyay5XuRePqRBrEW88UxgqQAiAoYC_u5YRvLYM20Q0J1qnCD-3sPshyiBFEewuHtFYwaI16B0P51N5vZanKXgRwdXmso_xCYVREg86ALBJrClYFFsSHfMiVdmBNy53kHsHOZWzR2jBrehGe29IA/s320/MarchingBand%20-%203%20(1).jpeg" width="277" /></a></div><br /> I've been reflecting on some of the agile transformations I've been involved in over the past few years. In some cases, I see some real progress made. Other times it seems like just re-arranging the deck chairs on the Titanic. An organization follows some recipe, but they don't get the results. Why?<p></p><p>I was working with a large financial institution. They had adopted the "Spotify Model" (yes I know, it's not a real thing) and after that they adopted another scaling framework. I came in and started looking at what was going on and discovered they had a huge challenge with dependencies across teams and products. They failed to realize how much the dependencies on other teams was slowing any one team down.</p><p>I took some on-line training recently, a course called <a href="https://www.focusedobjective.com/courses/take/agile-physics-the-math-of-flow/lessons/32278706-welcome-and-about-this-course" target="_blank">Agile Physics - the Math of Flow</a> led by Troy Magennis. In it, he talks about <a href="https://en.wikipedia.org/wiki/Amdahl%27s_law" target="_blank">Amdahl's law</a>, which was developed in the late 60s to explain parallel processing. The bottom line is that there is always going to be a limit on how much additional output you can get by adding more processing power. Troy points out the law applies to people and teams as well as CPUs.</p><p>One source of the limit is how much can be done in parallel, or said another way, how much dependency there is between teams. So two processors (teams) in parallel with no dependencies can produce twice the output of one. However, as less of the work can be done in parallel (ie, dependencies), the output drops. Using the formula Amdahl developed, if you have 4 teams and 80% parallelization, your output is 2.5 (not 4). If you want to learn more, take the course...it's free and some really interesting ideas.</p><p>Back to my client with all the dependencies. What could have helped them? Maybe if before they applied the recipe for scaling, they took some time to look at how their teams were set up and came up with a better approach there, that is, one that reduced/eliminated dependencies. More on this idea in a future blog post. </p>Bob Tarnehttp://www.blogger.com/profile/09907970828978458221noreply@blogger.com0tag:blogger.com,1999:blog-19452212.post-8774309983328858332020-11-21T14:47:00.007-06:002020-11-21T14:58:54.832-06:00Is it Time for Holacracy?<p class="p1" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px;"><span style="font-family: times;"></span></p><div class="separator" style="clear: both; text-align: center;"><span style="font-family: times; font-size: medium;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjoqr2OJkgYJrxnJMd_naeQuvD52Ag-Qeu_8o_1mHWMa41CIhkNSv8ucUCB83JktpYVnQLnvObEuFr6ec76ZgLvom6-wThpgFziHJm_06BgSxKCpmtd_5970m7NmelQU6mYRxqq/s2048/E7EE0642-A4B6-43AC-AB52-D86825193F05-11873-0000079CB66DEC89.jpeg" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img alt="Tile Circle" border="0" data-original-height="1365" data-original-width="2048" height="133" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjoqr2OJkgYJrxnJMd_naeQuvD52Ag-Qeu_8o_1mHWMa41CIhkNSv8ucUCB83JktpYVnQLnvObEuFr6ec76ZgLvom6-wThpgFziHJm_06BgSxKCpmtd_5970m7NmelQU6mYRxqq/w200-h133/E7EE0642-A4B6-43AC-AB52-D86825193F05-11873-0000079CB66DEC89.jpeg" width="200" /></a></span></div><span style="font-family: times; font-size: medium;"><br />I was doing some research last weekend on <a href="https://en.wikipedia.org/wiki/Holacracy" target="_blank"><span class="s1" style="color: #dca10d;">Holacracy</span></a> for a course I’m developing for <a href="https://ce.uci.edu/" target="_blank"><span class="s1" style="color: #dca10d;">University of California - Irvine Extension</span></a>. I have been teaching for them for about 8 years now and I’m helping update their agile class offering.</span><p></p><p class="p1" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px;"><span style="font-family: times; font-size: medium;"><br />Holacracy really turns the industrial revolution style of organization on its head. Rather than leadership making the decisions for the workers to execute, the decision making is really pushed down to the people doing the work. The traditional hierarchy is thrown out the window. No more managers reporting to department heads reporting to business unit managers reporting to Vice Presidents…you get the idea.<br /><br />Instead we have circles. For example, IT may be a circle. In it, each role has a description that gives clear direction on the responsibilities for that roll. There are simple rules that guide people, what they can and can’t do. It is a form of a <a href="https://en.wikipedia.org/wiki/Complex_adaptive_system" target="_blank"><span class="s1" style="color: #dca10d;">complex, adaptive system</span>.</a> Everyone focuses on the purpose of the organization, which goes beyond making money.</span></p><p class="p2" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px; min-height: 14px;"><span style="font-family: times; font-size: medium;"><br /></span></p><p class="p1" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px;"><span style="font-family: times; font-size: medium;">So what can Holacracy do for us now? With Covid-19 and work from home, the landscape of the work environment has changed. Will Covid-19 be the forcing function that changes the leadership model at companies? Does a remote workforce change how decision making occurs in an organization?<br /></span></p><p class="p1" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px;"><span style="font-family: times; font-size: medium;"><br /></span></p><p class="p1" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px;"><span style="font-family: times; font-size: medium;">When companies first tried the work from home approach a number of years ago, there were often strings attached. Companies would use the instant messaging app to track when people were at their desks, showing a lack of trust in employees. Are companies ready to stop monitoring output (hours at a desk) and start looking at outcomes?<br /><br />Holacracy isn’t for everyone. <a href="https://medium.com/" target="_blank"><span class="s1" style="color: #dca10d;">Medium</span></a> moved away from it when they felt it didn’t scale like they needed. After Zappos moved to Holacracy, they offered employees a severance package. Some of those that took it cited holacracy as the reason they were leaving. Today, Zappos has moved away from a pure Holacracy (<a href="https://finance.yahoo.com/news/zappos-quietly-backed-away-holacracy-090102533.html?guccounter=1&guce_referrer=aHR0cHM6Ly9kdWNrZHVja2dvLmNvbS8&guce_referrer_sig=AQAAAEWYW7_n07el9YLHHM7p7pPhj1MAGrPQalIWywhyOZ_xSHxzk--OVJv7TlB7WHgdg3icelskN1ZrBucxZFC9rCOG-E0wPnbN971wWXKDghTCi1Rr1Fy9_xwsNNumq573919mmZnzLoot2DsrR-MIA6aSzVaKz2tvsHKyPPnojFpM" target="_blank"><span class="s1" style="color: #dca10d;">article</span></a>). They are still self-organized, but in a slightly different way.</span></p><p class="p1" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px;"><span style="font-family: times; font-size: medium;"><br />Amy Edmondson and Michael Lee wrote a <a href="https://www.hbs.edu/faculty/Pages/item.aspx?num=53193" target="_blank"><span class="s1" style="color: #dca10d;">paper</span></a> on the topic of Self-Managing Organizations. One of the quotes from the paper was this: “Longstanding research tradition suggests that managerial hierarchy functions more effectively in stable conditions, but faces serious challenges in dynamic conditions.”<br /><br />In the latest update to the <a href="https://www.scrumguides.org/scrum-guide.html" target="_blank"><span class="s1" style="color: #dca10d;">Scrum Guide</span></a>, Jeff Sutherland and Ken Schwaber have moved from saying self-organizing teams to self-managing teams. In his book <a href="https://www.amazon.com/Reinventing-Organizations-Frederic-Laloux/dp/2960133501" target="_blank"><span class="s1" style="color: #dca10d;">Reinventing Organizations</span></a>, Fredrick Laloux provides several models of companies in some form of self-managing. So maybe Holacracy isn't for everyone, but it seems like organizations are moving to more self-managing models.</span></p>Bob Tarnehttp://www.blogger.com/profile/09907970828978458221noreply@blogger.com0tag:blogger.com,1999:blog-19452212.post-53296885196402542542018-12-17T18:30:00.000-06:002018-12-17T18:30:19.869-06:00What the Military can teach us about Sprint PlanningAs a coach, I've seen many Sprint Planning sessions. Some are more effective than others. When it comes to planning, the military has a long history and we can learn a few things from them.<br />
<blockquote class="tr_bq">
<span style="font-size: large;">Plans are worthless, but planning is everything</span></blockquote>
<blockquote class="tr_bq">
- Dwight Eisenhower</blockquote>
I have always interpreted the meaning behind this quote by Eisenhower to mean that through the act of planning, we gain a shared understanding of what we are attempting to do; the plan itself may change, but the goal won't<br />
<br />
The military talks about "<a href="https://en.wikipedia.org/wiki/Intent_(military)">Commander's Intent</a>" which looks at the mission, the desired end state, and the purpose of an operation. While this seems to be bigger than a sprint goal, a good sprint goal will help the team understand the end-state of the sprint.<br />
<br />
If the team has a good sprint goal, it will help them deliver on the intent but still give some flexibility on how they deliver. Without following any specific military planning technique, here are some other aspects of a military plan that we can borrow in our sprint planning:<br />
<br />
<ul>
<li><b>Resources & People: </b>Do we have all the equipment we need? Are test environments ready? Do we have test data? Do we know who is going to be available? Any planned vacations or holidays that impact the sprint? I encourage my scrum masters to keep a spreadsheet to keep track of the team so they can tailor their capacity to the available developers. </li>
<li><b>Lessons Learned:</b> Have we included kaizens from the last retrospective into our plan? Do we have them on the sprint backlog?</li>
<li><b>The Plan</b>: The team should self-organize around the work that needs to be accomplished.</li>
<li><b>Contingencies:</b> Once we have a plan, do we thing about what could go wrong, a technique the military calls <a href="https://en.wikipedia.org/wiki/Red_team">Red Teaming</a>. What do we do if the test environment goes down? What if that snow being predicted for the end of the week is worse than they predict?</li>
</ul>
<br />
Taking the extra time to discuss all these aspects to the plan will build a stronger understanding of the plan, which will help the team make better decisions when things don't go according to plan.Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-19452212.post-77565361044114776092018-12-04T17:37:00.001-06:002018-12-04T17:37:41.983-06:00Getting Rusty<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgX6QCzmqYeRwXvLQW5HQamtgmwhtYu1D3EOQ3R_b47MrlVAVj5hubh1EEHbFVzOpjkhvATF9_vCTbm1C8edLmsbT1hM_ZUdyujQUkpGsgZiWTI2AeiC4QnBiFk9iL_qujy0aLs/s1600/IMG_0113.jpg" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" data-original-height="1600" data-original-width="1262" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgX6QCzmqYeRwXvLQW5HQamtgmwhtYu1D3EOQ3R_b47MrlVAVj5hubh1EEHbFVzOpjkhvATF9_vCTbm1C8edLmsbT1hM_ZUdyujQUkpGsgZiWTI2AeiC4QnBiFk9iL_qujy0aLs/s320/IMG_0113.jpg" width="252" /></a></div>
I was in the Moab, Utah area last weekend and got some mountain biking in. I haven't spent a lot of time mountain biking this year so I was a bit rusty. By the second day I was starting to get my rhythm but it took a little time.<br />
<br />
Just like mountain biking, our agile skills can get rusty. I ran a Lean Coffee last week and before it I read a couple articles because I hadn't done a Lean Coffee in a while and wanted to make sure I didn't miss anything.<br />
<br />
I've been working with some of my newer Scrum Masters on facilitation techniques, another skillset that can easily get rusty if you don't do enough of it.<br />
<br />
One of my favorite facilitation tools is POWER;<br />
<br />
<b>Purpose </b>- why are we having this meeting/workshop.<br />
<br />
<b>Outcomes</b> - what do we expect to walk away with.<br />
<br />
<b>What's in in for me</b> - Why will participants want to attend and what can they get out of it<br />
<br />
<b>Engage</b> - how will you as the facilitator engage the participants. Think about activities, items on the tables to play with, or even snacks.<br />
<br />
<b>Roles & Responsibilities</b> - What can the participants do.<br />
<br />
I like using this as a way to prepare for workshops so that I can make sure the workshop provides value to the participants. Using this keeps me from getting Rusty on my facilitation techniques.Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-19452212.post-31459137976609788372018-11-29T09:15:00.001-06:002018-11-29T09:15:18.093-06:00If You're Going to Offshore, Get it RightIn general, I prefer having fully co-located teams but I've been working with a number of organizations that use off-shoring as part of their delivery model. Some have the right approach, others are missing the mark.<br />
<br />
When one organization I worked with decided to move to a <a href="https://www.scrum.org/resources/scrum-guide?gclid=Cj0KCQiAuf7fBRD7ARIsACqb8w4f02fLxa2wqdQ4Y_RYCGEPRfnKdh4G49rbiO2eF7Madt2hy82heysaAliUEALw_wcB">Scrum</a> framework, they were also setting up an off-shore model with developers in India. In this case, they brought those developers to the U.S. to be part of the team formation process; learning the Scrum framework, setting up a team operating agreement etc.<br />
<br />
When these individuals went back to India, they were set up with the right equipment; good audio and video capability that gave then a tele-presence ability. Each morning the US based part of the team would go to a video conference room and spend the first part of their day with the India part of the team. They could see/hear each other well, share documents, and even walk through code together. It was a pretty effective approach.<br />
<br />
Counter this with another client of mine. They also have India-based developers, but they have not had the opportunity to travel to the US. They don't have any real tele-presence, just conference calls and screen sharing. They don't really participate, just listen in on discussions from a US based conference room. Self-organizing is also absent, they are assigned tasks by the lead developer, who is in the US. My observation is that they aren't getting much value out of this approach.<br />
<br />
I'm a fan of the <a href="https://en.wikipedia.org/wiki/Media_richness_theory">Media Richness Theory </a>and have used it with my clients. I have also taken a page from <a href="https://en.wikipedia.org/wiki/Crew_resource_management">Crew Resource Management (CRM) </a>and their communications practices. One of my favorite assertive communications tools is <a href="https://en.wikipedia.org/wiki/SBAR">SBAR</a> (situation, background, assessment, recommendation). I have taught this technique to a number of teams as part of a focus on building up their teaming capability.<br />
<br />
Given the choice, I would have all my teams co-located. When that isn't possible, I try to bring them together as often as possible and use good tele-presence tools when they are not together. Regardless of your model, you still have to teach them good communications and teaming techniques so they can be as effective as possible in any configuration.Bob Tarnehttp://www.blogger.com/profile/09907970828978458221noreply@blogger.com0tag:blogger.com,1999:blog-19452212.post-73838785593293049472018-09-24T18:35:00.000-05:002018-09-24T18:35:23.201-05:00How to Budget For Your Company’s Technical Debt<div>
<blockquote style="caret-color: rgb(34, 34, 34); color: #222222; font-family: Arial, Helvetica, sans-serif;" type="cite">
<strong><br />Guest post by Dr. Mik Kersten</strong><br /><br />While “technical debt” is a term that’s frequently used by technologists, the implication and understanding of it tends to be opaque to the business until it’s too late - just look at how Nokia lost the mobile market that it helped create.<br /><br />The business and finance side of Nokia had the usual tools for assessing financial risks - but why do we not have an equivalent tool for the operational or existential risks when the debts come from the more intangible investment in technology?<br /><br /><strong>What’s technical debt?</strong><br />Technical debt refers to the refactoring "shortcuts" taken in IT to meet requirements like time to value (TtV) and speed-to-market. Technical debt is like cholesterol; the more it accumulates, the more it impedes the flow of value.<br />
Legacy systems are a perfect example of technical debt. We are all too familiar with that system that everyone dreads to touch and hopes that it doesn’t malfunction because any modifications to improve its business value will cost time and money. Yet the longer you wait, the costlier it will get due to lack of knowledge and support.<br /><br />Speed-to-market pressures also increase the debt – such as first-to-market, responding to time-critical customer needs, and faster customer feedback to improve performance and value. Compromises are made with the notion of dealing with the consequences later.<br /><br />Sometimes it’s as simple as realizing the technology or architecture chosen for a particular product is no longer scaling and needs refactoring. All of these technical decisions impact delivery speed and must be managed to ensure any future changes or products are not delayed. Taking on technical debt is not necessarily a bad thing, as long as it is understood by the business decision makers who put in place a plan for that debt to be paid down.<br /><br /><strong>Why should the business care – isn’t this a cost that IT manages?</strong><br />Technical debt additionally impacts delivery teams by bloating their work-in-progress (WIP) with neglected work. Neglected work can impact a team’s ability to focus and complete value-adding work. Less completed work leads to longer time to delivery, lower product quality, and less value, impacting customer satisfaction and business performance.<br /><br /><strong>How can IT make technical debt visible to the business?</strong><br />In a project-oriented view, where changes to IT systems are just another initiative, it’s difficult to prioritize and fund critical changes that will improve the speed of future changes. Yet software needs to go through a period of refactoring to maintain performance.<br /><br />A product-oriented view enables the business to understand how all work interlinks, providing the ability to predict and fix for the impact of technical debt. However, you can’t measure what you can’t see, so it’s crucial to make technical debt visible. The Flow Framework – a new way of seeing, measuring, and managing product delivery – introduces two metrics that help increase visibility of technical debt:<br /><br /><strong>Flow Distribution</strong><br />This metric shows the distribution of the different types of work that the IT team has delivered, such as value-adding work like features and functionality, and revenue-protecting work like defects, security related work. Yet the more new functionality they deliver, the less time they have to do the other types of work like defect resolution, working on security features etc. It’s important to keep an eye on what the levels are for technical debt in this equation. Has the level of completed tech debt work fallen in the last few releases? If so, it is leading indicator of more defects/delays in the future releases. In addition, the Flow Framework expands on the notion of technical debt to include infrastructure debt (e.g., data centers and servers), and debt in the value streams themselves (e.g., lack of automation).<br /><br /><strong>Flow Load</strong><br />Flow Load is a Flow Framework metric that shows the amount of work that a team or seat of teams have taken on. How much work do they have and what proportion of it is technical debt? Is there a lot of technical debt left in the backlog accepted but unfinished because new work is taking precedence? Accumulating technical debt on the backlog can have an increasingly negative impact a company and its products.<br /><br /><strong>Budgeting for technical debt</strong><br />There are two parts to budgeting for technical debt.<br /><br />1) Correlating the impact of tech debt with value-adding work can help business understand its danger on the bottom line. Time and resources must be set aside every financial year to tackle technical debt as debt often accumulates due to a lack of funding and sponsorship.<br /><br />2) IT and business should look at trends that determine an appropriate level for when appropriate action must be taken to “pay back". It’s similar to the error budget in Systems Reliability Engineering that helps product development and system reliability teams work together on a level of unreliability that can be tolerated.<br /><br />If technical debt is not actively monitored, it will gradually impact the flow of value to customer-facing products. Neglect the build-up and a cardiac arrest is inevitable. Make sure technical debt is visible and measured so that the business and IT can team up to proactively tackle and reduce technical debt to ensure a healthy product portfolio that can sustain the business.</blockquote>
</div>
<div>
<blockquote style="caret-color: rgb(34, 34, 34); color: #222222; font-family: Arial, Helvetica, sans-serif;" type="cite">
<em>Dr. Mik Kersten is the CEO of Tasktop and author of <a href="https://www.amazon.com/Project-Product-Survive-Disruption-Framework-ebook/dp/B07F3DJMZ1">Project to Product: How to Survive and Thrive in the Age of Digital Disruption with the Flow Framework</a>. For more information, please visit, <a data-saferedirecturl="https://www.google.com/url?q=http://www.tasktop.com&source=gmail&ust=1537625881145000&usg=AFQjCNHvJ9QMHG_7mayNE8-44_cLivqYgQ" href="http://www.tasktop.com/" style="color: #1155cc;" target="_blank">www.tasktop.com</a>.</em></blockquote>
</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-19452212.post-57943421248788371422018-09-05T19:49:00.003-05:002018-09-05T19:49:43.881-05:00Interview at Agile2018A long-time colleague and friend, Dave Prior, interviewed me at Agile2018 about my presentation on being an agile coach at Toyota. You can find it <a href="http://drunkenpm.blogspot.com/2018/09/lessons-from-coach-at-toyota-w-bob.html">here.</a>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-19452212.post-21818945363440711032018-08-09T21:21:00.000-05:002018-08-09T21:21:22.109-05:00Agile 2018 wrap upI'm on my way home after spending the week at Agile2018. It's been a great conference. I reconnected with old friends, met some new ones, and attended some great presentations.<br />
<br />
Monday's keynote was Dom Price (@domprice) from Atlassian. He shared how Atlassian tracked team health via their <a href="https://www.atlassian.com/team-playbook?utm_source=teamtour" target="_blank">playbook</a>. One interesting statistic he shared was that 78% of people don't trust their team mates. He also hit a theme that was repeated by many of the speaker; focus on outcomes, not outputs.<br />
<blockquote class="tr_bq">
<span style="font-size: large;">Focus on outcomes, not outputs</span></blockquote>
Wednesday's keynote was a focus on metrics by Troy Magennis. At first I considered not attending, but I'm glad I did. Troy talked about data as a people problem. He said a good way to get "crappy" data is to embarrass people. The data isn't enough, we have to be able to tell a story with it.<br />
<br />
There were a number of other sessions that I took something away from;<br />
<br />
<ul>
<li><a href="http://www.ambysoft.com/scottAmbler.html" target="_blank">Scott Ambler</a> talked about architecture. A key message was that there are no "best practices" and the approach you apply depends on the context.</li>
<li><a href="http://www.leadtotheedge.com/bio/" target="_blank">Tricia Broderick</a> gave a session on facilitation. A point that stuck with me was that if we need to select mentoring or training or coaching based on the situation we're in and our desired outcome.</li>
<li><a href="https://medium.com/@davidjbland" target="_blank">David Bland</a> gave a session on experiments as they relate to new products. He turned the cycle in Lean Startup around and said we should start with Learn. From there, we decide what we want to measure, and based on that we decide what to build. </li>
</ul>
<div>
This is just a snapshot of the fours days I attended. I have other notes and ideas of things I'm going to use when I get back to my "day job" of coaching. I recommend anyone looking for an infusion of new ideas to consider attending next year. </div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-19452212.post-77678820027005375592018-08-03T13:18:00.000-05:002018-08-03T13:18:05.094-05:00Regression to the Mean or High PerformingI had an interesting conversation with one of my Product Owners this week. She thought that over time, planning poker values feel prey to <a href="https://en.wikipedia.org/wiki/Regression_toward_the_mean" target="_blank">Regression toward the Mean</a> because human nature was such that people didn’t want to stand out and therefore tried to give estimates in line with what they thought others would.
<br />
<br />
I countered by saying if people were afraid to state what they truely thought the value should be, there is probably a psychological safety issue going on. The purpose of using poker cards during the activity is to avoid anchoring; having everyone influenced by one person stating aloud their estimate.
<br />
After the conversation, another idea crept into my head. I tell teams that small stories are better. I am even a proponent of <a href="http://noestimates.org/blog/2014/07/vasco-duarte/" target="_blank">#noestimates</a> in the right situation. So from this perspective, as a team moves towards high performance, they will get good at vertical slicing and that will lead to smaller stories, and therefore smaller estimate values.
<br />
<br />
So in response to the original statement, I don't think on a well-functioning team, the estimates are prone to regression toward the mean. However, I can see it happening on a team that is dealing with psychological safety issues. The real test is to watch the velocity over time. If regression toward the mean were happening, the velocity would be dropping over time. If the team is healthy, they will have a steady, or even increasing velocity.
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-19452212.post-69389410331752956812018-05-18T11:13:00.004-05:002018-05-18T11:13:53.881-05:00IllusionsI am still reading <a href="https://www.amazon.com/Thinking-Fast-and-Slow/dp/B005Z9GAJG/ref=sr_1_1?ie=UTF8&qid=1526658591&sr=8-1&keywords=thinking+fast+and+slow" target="_blank">Daniel Kahneman's <i>Thinking, Fast and Slow</i></a>, and I came across an interesting quote<br />
<blockquote class="tr_bq">
People can maintain an unshakable faith in any proposition, however absurd, when they are sustained by a community of like-minded believers. </blockquote>
He used the example of stock traders, who think they are successful in picking stocks even though evidence points otherwise. Two out of three mutual funds underperform the overall market in any given year. However stock traders still believe in their approach.<br />
<br />
I thought of the example of project management. I went to my first <a href="https://www.pmi.org/" target="_blank">PMI</a> conference in 1999. I was surrounded by like-minded believers in the waterfall methodology for project management, even though evidence such as the <a href="https://getlevelten.com/wiki/chaos-report" target="_blank">Chaos Report</a> showed that our approach was not effective.<br />
<br />
Will we see the same effect with agile approaches? Will we fool ourselves into believing we are successful even if the evidence suggests otherwise? Maybe not.<br />
<br />
Philip Tatlock did research for his 2005 book <i><a href="https://www.amazon.com/Expert-Political-Judgment-Good-Know/dp/B00GN5XA3U/ref=sr_1_1?ie=UTF8&qid=1526659972&sr=8-1&keywords=expert+political+judgment" target="_blank">Expert Political Judgment: How Good Is It? How Can We Know?</a></i> Tatlock interview 284 people covering 80,000 predictions and even though these people were "experts" their results were worse then if these predictions were simply assigned probabilities. To compound the effect, the experts were very reluctant to admit that they were even wrong.<br />
<br />
Kahneman sums it up pretty nicely. He says that the "errors of prediction are inevitable because the world is unpredictable." (p. 220) He goes on to say that short-term trends can be predicted but not longer term ones; though even the dividing line between the two is unpredictable. The implication to planning is clear; keep the planning horizon short and don't fool yourself into believing you are better than you really are.<br />
<br />Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-19452212.post-48909923952372439462018-04-15T10:31:00.000-05:002018-04-15T10:31:41.464-05:00PrimingI'm working on the book <i><a href="https://www.amazon.com/Thinking-Fast-and-Slow/dp/B005Z9GAJG/ref=sr_1_2?ie=UTF8&qid=1523805911&sr=8-2&keywords=think+fast+and+slow" target="_blank">Thinking, Fast and Slow</a></i> by Daniel Kahneman, who won the Nobel Prize in Economics. As you might guess, the book is about how the brain works, based on years of research. He talks about the mind as two systems, the first being fast and intuitive and the second being more deliberate.<br />
<br />
One of the ideas he discussing is that of <a href="https://en.wikipedia.org/wiki/Priming_(psychology)" target="_blank">Priming</a>. Priming happens when something such as a set of words impact our thought and actions. He gave a great example of an experiment with two sets of participants. One set was given a set of words associated with being old (gray, wrinkle, Florida) and another group had words not associate with being old. They were asked to create sentences with the words. They were then asked to walk down the hall for the next experiment. The group with the "old" words walked down the hall much slower than the other group...these were all college students so it had nothing to do with their actual age. One group was primed; they had the idea of old planted in their minds and they acted differently because of it without knowing it.<br />
<br />
In another experiment, people were asked to put money into an "honesty box" based on how much coffee or tea they drank. There were different posters placed on the wall above the money box. On weeks when the posters had eyes looking down, people paid more money than on weeks when the posters were of flowers.<br />
<br />
Think of how easily priming could impact a team. Imaging a team trying to overcome a complex technical challenge such as getting a test case to pass. They aren't sure why it isn't passing and they are discussing solutions. One person's comments could lead the team all in the wrong direction without them even realizing it. <br />
<br />
So how do we combat this? The reason priming happens is because our fast, intuitive mind takes over. To combat it, we need to rely on our more cognitive side, which Kahneman points out is also lazy and willing to let the intuitive side run the show. For this imaginary team, using a <a href="http://zen-pm.blogspot.com/2017/10/red-teaming.html" target="_blank">red teaming</a> approach might work, or an analytical took such as <a href="https://en.wikipedia.org/wiki/5_Whys" target="_blank">Five Whys</a>. Anything that will get the team to look beyond intuition and engage their more deliberate thinking patterns.<br />
<br />
As far as <i><a href="https://www.amazon.com/Thinking-Fast-and-Slow/dp/B005Z9GAJG/ref=sr_1_2?ie=UTF8&qid=1523805911&sr=8-2&keywords=think+fast+and+slow" target="_blank">Thinking, Fast and Slow</a></i>, I'm only about a quarter of the way through and have come across a lot of interesting ideas, so I am sure I'll have more to post on the book.Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-19452212.post-14950545421872954212018-03-13T18:56:00.000-05:002018-03-13T18:56:19.789-05:00Team of TeamsI recently completed the book <a href="https://www.amazon.com/Team-Teams-Rules-Engagement-Complex/dp/1591847486" target="_blank">Team of Teams by Stanley McChrystal</a>, a retired Army General and former commander of the Joint Special Operations Task Force, operating in Iraq. It's the story of how he transformed that command in order to more effectively execute their mission.
<br />
<br />
The book explores the ideas of complicated and complex. I kept thinking about the <a href="https://en.wikipedia.org/wiki/Cynefin_framework" target="_blank">Cynefin framework</a>, though McChrystal does not specifically mention it in the book. The book starts by talking about the work of Fredrick Taylor around the start of the 20th century (complicated). He then gives some examples of complex problems. My favorite was the introduction of <a href="https://en.wikipedia.org/wiki/Cane_toads_in_Australia" target="_blank">the cane toad in Australia</a>.
<br />
<br />
The book then goes into how McChrystal moved his command away from a strict command structure and to a team of teams structure. This change made them more resilient, allowing them to more effectively respond to the enemy. McChrystal makes a point to show how efficient and resilient are on opposite ends of a spectrum, and being resilient was more important than being efficient. The move to a team of teams was done by cross-pollinating individuals across teams. There was also a liaison program to work with external organizations.
<br />
<br />
The parallel between Team of Teams and <a href="https://www.amazon.com/Accelerate-Building-Strategic-Agility-Faster-Moving/dp/1625271743" target="_blank">John Kotter's book Accelerate</a> are interesting. Both recognize the hierarchy can't support today's environment. McChrystal saw the team of teams as a way to be more resilient so that the organization could respond quicker to threats. Kotter viewed it as a way to implement strategy. In both cases, the hierarchy remains, but it is supported by the teams.<br />
<br />
The agile world is catching on as well. The <a href="https://www.scrumatscale.com/scrum-at-scale-guide/" target="_blank">Scrum@Scale guide</a> references McChyrstal's book when describing the Scrum of Scrums. I've been trying to build this with my teams. For example, shifting from a status meeting where people report to the manager one at a time while everyone else has their nose in their computer to everyone interacting and building a shared consciousness. The first step, banning computers from meetings so people pay attention.
<br />
<br />
Another idea I'm trying is similar to how Spotify uses guilds to share across teams. I'm bringing together developers from across all the teams to discuss technical topics of their choice. We kicked off the initiative by creating an operating agreement, identifying the topics of interest, and picking a topic for the next meeting. I believe this can lead to a number of outcomes: a better shared understanding of the department's work, the ability to move developers more effectively from one team to another to meet changing priorities, and improving skills across all the teams...again, along the line of team of teams.<br />
<br />
I recommend Team of Teams for anyone that is working with more than one team and trying to figure out how to create a resilient organization that can keep up with a rapid pace of change.Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-19452212.post-27661485607089525192018-02-08T18:59:00.000-06:002018-02-08T19:10:23.702-06:00Situational AwarenessI have been exploring techniques to help my Scrum teams become more effective and one of the techniques I've been looking at is <a href="https://en.wikipedia.org/wiki/Crew_resource_management" target="_blank">Crew Resource Management</a> (CRM).<br />
<br />
CRM came about because of a number of airplane crashes in the 70s that were attributed to human error. More recently, it is cited as one of the reasons there were no causalities in the <a href="https://en.wikipedia.org/wiki/US_Airways_Flight_1549" target="_blank">US Air flight 1549 (Miracle on the Hudson)</a>.<br />
<br />
One component of Crew Resource Management is Situation Awareness. A simple definition of situation awareness is how well your perception matches reality. There are a number of factors that can impact situation awareness such as complacency (I've done this so many times…), task saturation (too much work in progress), channelized attention, or poor communications.<br />
<br />
I had a situation recently where my scrum master lost situation awareness. We were at the end of the sprint and he told me the team had completed 45 story points, more than any previous sprint. However, a conversation with the product owner a short time later revealed that really wasn't the case. The product owner wasn't satisfied with how some of the work was done.<br />
<br />
What happened? The scrum master was fixated (channelized attention) on what the developers were telling him because he wanted to be able to show all the stories done for the sprint. He lost site of the definition of done, which included a review with the product owner before a story was marked done.
<br />
<br />
Our kaizen for the week was a review of our definition of done and re-commit that nothing would be marked done without a product owner review. We took this idea into planning and included tasks for product owner review in each story so we could track these tasks to completion on our board so that the scrum master had additional visual cues to help him with his situational awareness.<br />
<br />
So how can the team keep better situational awareness? Having a good visual board helps. In addition to tracking work thru the To Do/Doing/Done path, the board also has a place for impediments, the definition of done, release plan, and a burndown. For this team, the board is also in the team room, and any time I walk in, I stand near the board when I'm talking to the team and encouraging them to look at the whole board, similar to how a pilot is constantly scanning all their gauges so they don't miss anything (as opposed to the crew of <a href="https://en.wikipedia.org/wiki/United_Airlines_Flight_173" target="_blank">Flight 173</a>, who fixated on a landing indicator light and forgot to keep check on their fuel).Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-19452212.post-13967609495244170352018-01-31T19:59:00.002-06:002018-02-08T19:14:36.918-06:00Psychological SafetyI had an interesting experience recently. I was working with a team as they went thru their sprint planning. They had figured out their capacity based on yesterday's weather and their average amount of interrupt. The product owner suggested the sprint goal and they started picking stories based on the goal. They reached the point where one more story met the sprint goal, but put them over their estimated capacity. The scrum master pulled it into the sprint and said he thought they could get the story done.<br />
<br />
At this point I stepped in and commented that it was up to the developers to decide if they wanted to commit to the work. The developers remained silent. I made a comment about not over-committing and finally some comments were made by the team to keep the story out and pull it in if they get everything else done.
<br />So what happened here? Why didn't any of the developers speak up when the extra story was first pushed on them? Based on this and other observations in the organization, I attribute it to a lack of psychological safety. The developers didn't feel safe to say "No, that's more than we can get done." <br />
<br />
I wrote another article recently talked about<a href="http://zen-pm.blogspot.com/2017/10/red-teaming.html"><span style="-webkit-font-kerning: none;"> group think</span></a>. The two ideas are related. Group think exists in situations where people don't feel safe stating an opposing view. But psychological safety goes much further than that. A team without psychological safety will be reluctant to take chances, it impacts their ability to learn, they will be afraid to admit mistakes. In general, it keeps them from becoming a high-performing team.
<br />
<br />
So how does a team fix this? The reality is they can't. It's not the team but the organization around the team that will or won't create a space of psychological safety for the team to exist in. Product owners and chief product owners need to be coached to understand how their actions impact the environment. It's starts with them showing they are vulnerable, by admitting their mistakes. They need to encourage teams to take risks and not punish failure but show how it can be used as a learning event. It's only when teams see these kinds of behaviors that they will start feeling safer, and next time a developer will speak up and say "No, that's more than we can get done."Bob Tarnehttp://www.blogger.com/profile/09907970828978458221noreply@blogger.com0tag:blogger.com,1999:blog-19452212.post-8358504663392299482017-12-05T10:04:00.001-06:002017-12-05T10:15:27.331-06:00NemawashiI am speaking this
week at the <a href="https://www.p2pevents.net/">Projects to the Point (P2P) conference</a> in Cairo, Egypt. The focus
of the conference is the book "How Successful Organizations Implement
Change" and the speakers (myself included) each wrote one of the chapters
of the <a href="http://marketplace.pmi.org/Pages/ProductDetail.aspx?GMProduct=00101602801">book</a> by the same title.
<br />
<br />
We have an
interesting approach for implementing change where I'm working, a technique
call Nemawashi. It's a Japanese term that literally translates to "digging
around the roots" but the meaning is much more than that. Nemawashi is
laying the groundwork for a change.
The work starts
before any formal meeting is conducted. Ideally, the person proposing the
change will have already worked on building the relationships with the people
who's support is needed. They will know the formal and informal organizational
structure so when it comes time to start informal discussions, they know who to
speak to.
<br />
<br />
When it comes time
for a change, the change agent determines who the key stakeholders are. The
change agent has informal discussions about the proposed change. It may be a
quick talk over coffee accompanied by a drawing on a napkin. The discussion may
include a history of the proposed change, others that have been consulted, and
options. The discussions are a way to solicit feedback and adjust the plan
before moving forward. In some cases, they may need to move backwards, having
follow-on discussions with stakeholders they've already talked to as the plan
evolves.
<br />
<br />
When it does come
time for a formal meeting, all the key stakeholders have already heard the idea
and provided their input. The formal meeting should just be a formality. If
someone hasn't been included in the nemawashi process, they may reject the
proposal just because they feel they were ignored.
<br />
<br />
This form of
consensus building may not be the fastest way to introduce a change but like
the meaning of the word, it will ensure that a new change gets to the roots to
improve the chance it will take hold.
Bob Tarnehttp://www.blogger.com/profile/09907970828978458221noreply@blogger.com0tag:blogger.com,1999:blog-19452212.post-73132237710475069142017-11-09T15:59:00.001-06:002017-11-09T16:00:01.702-06:00PMI Conference observationsThe PMI Conference was held this past weekend in Chicago. They've changed the format a bit and even changed the name to reflect the changes. When I first started attending almost 20 years ago, it was the PMI Symposium, then Global Congress and now the PMI Conference.<br />
<br />
They had 3 different keynote speakers (though I only saw 2 of them), one each day. On Saturday, the speaker was<a href="https://en.wikipedia.org/wiki/Tim_Berners-Lee"> Sir Tim Berners-Lee</a>, the person that developed the technology that made the world wide web possible, specifically hypertext transfer protocol (HTTP). He talked about how a goal was to make the web a "permission-less place" where anyone could put up a site.<br />
<br />
The web developed first through creativity, then collaboration as the world wide web consortium evolved. He did highlight a point of complex systems, that the behavior at the macroscopic level is different than on the microscopic level. While I thought the talk was interesting, some of my non-IT colleagues had trouble following it.<br />
<br />
Sunday's keynote was very interesting. The speaker was <a href="http://faculty.chicagobooth.edu/nicholas.epley/">Nicholas Epley</a>, author of <a href="https://www.amazon.com/Mindwise-Understand-Others-Think-Believe/dp/0307595919">Mindwise </a>and professor at University of Chicago. His presentation was on communications, along the lines of <a href="https://www.huffingtonpost.com/nicholas-epley/how-behavioral-science-ca_b_5073085.html">this article he wrote for Huffington Post</a>. He ended with 4 take-away's:<br />
<br />
1) Be wary of any gimmicks when it comes to trying to understand others. Always ask for evidence.<br />
2) Cut down your confidence in how well you think you understand what someone else is thinking, you understand them less than you think.<br />
3) Learn to ask questions well, it's the best way to gain an understanding of what someone else is thinking.<br />
4) To communicate well, be painfully clear. Don't assume the other person will easily understand your message.<br />
<br />
The best session I sat in on was delivered by Ahmed Sidky. He talked about how the leadership structure of agile teams evolved at <a href="https://www.riotgames.com/">Riot Games</a>. Rather than assigning roles such as scrum master or product owner to individuals, they identified 4 key leadership roles;<br />
<br />
Team Captain - responsible for overall delivery<br />
Product Lead - responsible for the direction of the product<br />
Delivery Lead - responsible for development<br />
Craft Lead - responsible for the engineering<br />
<br />
Each team would associate key responsibilities with the four "hats" as they call them. A team member can wear more than 1 hat but the team decides all of this.This approach takes self-organizing teams to a new level.<br />
<br />
I also took part in an interactive session on the new Agile Practice guide that came out with the latest PMBoK. It was led by Jesse Fewell and Mike Griffiths, both long-time agile names in the PMI community.The session was a good way to start understanding what is in the guide.<br />
<br />
PMI tried to improve he quality of the sessions. As a speaker, I had to go through a few additional hurdles including creating a story board that was reviewed by an SME and practicing my presentation on the phone with a experienced speaker. I don't know if PMI got the results they wanted. There were regular speakers that did not speak because they didn't want to go through the additional steps. At the same time, I still had 2 sessions I walked out on because they didn't meet my expectations.Bob Tarnehttp://www.blogger.com/profile/09907970828978458221noreply@blogger.com0tag:blogger.com,1999:blog-19452212.post-5488884204527474862017-10-18T19:04:00.000-05:002018-01-31T20:18:39.461-06:00Red TeamingOne of the things we talk about at work is eliminating group think and an approach to do this is using red teaming.
<br />
<br />
For those not familiar with the term, red team comes from the military and originally stood for a team that represented the opposition. It has since expanded to include any team that might challenge the status quo..aka, group think.
<br />
<br />
So how does this apply to the agile world? Even agile teams can get stuck in group think. A great example is during story estimating. If you don’t use planning poker cards, the senior developer might say “oh, that’s a 5” and everyone else agrees, they become anchored to his estimate. Someone else might have had a different opinion (that’s going to be a 21 because we have to create a new database table) and they may be right, but they succumb to group think and let the 5 point estimate go. The obvious solution here is to use planning poker cards but sometimes as a coach I need to point this out to teams.
<br />
<br />
Group think can happen during any agile activities. During retrospectives, I coach my teams on the approach of each person writing ideas on post-it notes in silence and then discussing them as a group.
<br />
<div style="color: #454545; font-stretch: normal; line-height: normal; min-height: 19px;">
<span style="font-family: inherit;"><span style="font-kerning: none;"></span><br /></span></div>
<div style="font-stretch: normal; line-height: normal;">
<h3>
<span style="font-family: inherit;"><span style="font-stretch: normal; line-height: normal;"> </span><span style="font-kerning: none;">Think, Write, Share</span></span></h3>
</div>
<br />
This way, ideas can surface before group think can crush them.
<br />
<br />
Red Teaming can be applied elsewhere as well. Another place I like to use it is at the end of a planning session. The team has finished selecting stories to work on for the iteration, they have set their sprint goal and they’re ready to start. At this point I stop them and ask “what could go wrong with this plan?” This is another good place to inject “ think, write, share” and start a discuss about risks and responses to them.
So be on the lookout for group think and bring in a red team if you need to counter it.
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-19452212.post-10738227695010273742017-09-26T20:28:00.000-05:002017-09-27T05:55:13.608-05:00Debriefs<div style="font-stretch: normal; line-height: normal;">
<span style="color: #454545; font-family: .sf ui text;">I’m working on a new assignment as part of an agile coaching team leading a transformation at a large organization. One of my fellow coaches is also a former Navy officer. We’ve had a number of conversations about how many of the techniques developed by the military can be applied to make any team a high-performing one.</span><br />
<span style="color: #454545; font-family: .sf ui text;"><br /></span>
<span style="color: #454545; font-family: .sf ui text;">One particular tool is debriefing. I’ll admit, I didn’t do a lot of this in my military career, but the idea is to take time after any activity to review how it went. Kind of sounds like a retrospective, doesn’t it?</span><br />
<span style="color: #454545; font-family: .sf ui text;"><br /></span>
<span style="color: #454545; font-family: .sf ui text;">As an agile coach, I find this is a great tool. Just the other day I observed one of my teams run a stand-up. As soon as they were done, I gave them a debrief. It only lasted a minute. I highlighted what they did well and where they could improve. I have used the same approach with other teams on everything from iteration planning to retrospectives...sounds kind of “meta” but why shouldn’t you evaluate how effective your retrospective was? This technique is based on the approach of learning a new idea, practicing it, and getting feedback to reinforce the idea.</span><br />
<blockquote class="tr_bq">
<span style="font-size: large;"><span style="color: #454545; font-family: .sf ui text;"><br /></span><span style="color: #454545; font-family: .sf ui text;">Learn, Practice, Reinforce</span></span></blockquote>
<span style="color: #454545; font-family: .sf ui text;"><br /></span>
<span style="color: #454545; font-family: .sf ui text;">One key to debriefs, and I think this is important for a good retrospective, is to start by stating the goal of the activity. At the end of the iteration, can your team members state what the iteration goal was? How else can you evaluate how you did without thinking about what you set out to do. </span></div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-19452212.post-75980652533313305112017-05-22T08:06:00.000-05:002017-05-22T08:06:27.399-05:00EstimatingI was flying home from a client visit last week at the airport getting ready to board the plane when the gate agent announced that the flight was gonna be delayed by ten minutes due to some unspecified mechanical issue. Ten minutes later they announcement another ten minute delay. They did this two more times.<br />
<br />
So what was going on? Did the airlines not want to admit upfront that they had a 40 minute delay so they fed the delays to us ten minutes at a time? Or did the person who is doing the work really not understand how long it was going to take? I started thinking about how common it is for people to not be able to provide good estimates. Sometimes they underestimate the complexity, or maybe <a href="https://en.wikipedia.org/wiki/Student_syndrome" target="_blank">student syndrome</a> sets in, or they're just overly optimistic.<br />
<br />It was ironic, but part of the work with my client that week was explaining the technique of relative estimates using t-shirt sizes and story points. The team I was working with was new to agile and used to the old way of doing absolute estimates, which as we all know are not as accurate because of things like student syndrome or <a href="https://en.wikipedia.org/wiki/Parkinson%27s_law" target="_blank">Parkinson's Law</a>.<br />
<br />So how do we get better at estimating? I think the real question should be how we recognize estimates for what they are. An uncertain prediction of a future event. Even when we use story points, we won't know our true velocity until after a couple iterations when the team has time to come together. At the beginning of the project, we need to recognize how much uncertainty we have. So instead of saying "that will take about 2 months" we should say "that may take 2 months, but it could take as long as 3 months." So we provide not only the estimate but some measure of the uncertainty that goes with it. Similarly, if we think a story might be 13 points, but there's a lot of uncertainty, we should state that and make the story 20 points (or 21 if you're being strict with your Fibonacci sequence). Now if only I could get the airlines to provide a more accurate estimate the next time there's a delay...or at least how certain they are!Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-19452212.post-43833301589243301822017-03-30T15:52:00.002-05:002017-03-30T15:52:53.965-05:00The Bullet Journal<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgNTEbQeXKfe-h0V89Qvp8que-XsjVCjnWVOIJf2njN384-q3H4s2SxFJ1cXOyqaIKde48XMbI7iU8If20Ie3dRbMygYzTWTzIYWyJS_9B4aaacxShyphenhyphenZ6bhnqlrFCwttgrOZHMd/s1600/bullet_journal.JPG" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="240" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgNTEbQeXKfe-h0V89Qvp8que-XsjVCjnWVOIJf2njN384-q3H4s2SxFJ1cXOyqaIKde48XMbI7iU8If20Ie3dRbMygYzTWTzIYWyJS_9B4aaacxShyphenhyphenZ6bhnqlrFCwttgrOZHMd/s320/bullet_journal.JPG" width="320" /></a></div>
I started something new in February, a <a href="https://www.buzzfeed.com/rachelwmiller/how-to-start-a-bullet-journal?utm_term=.xkAyoMDZb#.uw3GwVQY9" target="_blank">bullet journal</a>. I've played with different tools to help me keep organized and remember stuff, and this is my latest.<br />
<br />
I went back to using paper over electronic tools for notes over a year ago based on <a href="http://www.npr.org/2016/04/17/474525392/attention-students-put-your-laptops-away" target="_blank">research</a> that showed you remembered things better when you took notes the old fashion way. Even then, I wasn't sure of the best approach. For a long time I was using standard legal pads, but I didn't want to take them with me when I traveled. I had a small organizer that allowed me to put paper in and out. I had tabs for different projects and clients but I found I was flipping pages to much.<br />
<br />
I've adopted a way to combine the legal pads and my bullet journal. I still keep a legal pad at my desk and write down about everything. At the end of the day, I review my notes and copy everything over to my bullet journal. This serves as a review, makes sure I don't forget any action items, and gives me a chance to jot down some reflections at the end of the day.<br />
<br />
I am using a Moleskin 5x8.5 dot grid soft cover notebook and a set of Sharpie fine point pens in 4 colors. I use different colors when I change subjects or otherwise want to highlight an idea. I have pages to capture books/movies/music I want to get, a page to capture things I'm grateful for, and a page where I have a year-long calendar.<br />
<br />
We'll have to see how long I keep this up. I've got the book "<a href="https://www.amazon.com/Doodle-Revolution-Unlock-Power-Differently/dp/1591847036" target="_blank">The Doodle Revolution</a>" sitting on my bookshelf, maybe I need to dust it off so I can add doodles to my journal.Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-19452212.post-56748031226501681332017-02-08T10:43:00.002-06:002017-02-08T10:48:04.469-06:00The Canvas Strategy<div class="p1">
I’m making my way through the Tim Ferris' book <i><a href="https://www.amazon.com/Tools-Titans-Billionaires-World-Class-Performers/dp/1328683788" target="_blank">Tools of Titans</a></i>. It’s well over 600 pages but it has a lot of useful, interesting advice, though I'll admit some of it is a bit out there. He breaks the book up into three areas; Healthy, Wealthy, and Wise. The book is really just a summary of podcasts done over the years with some other advice added in.</div>
<div class="p2">
<br /></div>
<div class="p1">
One piece of advice I appreciated is what he called the canvas strategy. The idea really came from Ryan Holiday. The name refers back to when apprenticeships were common; a budding painter learns his craft by serving under a master and doing such things as preparing his canvas. </div>
<div class="p2">
<br /></div>
<div class="p1">
In today’s terms it’s about serving the people you work for…sounds like servant-leadership! Some examples he gives includes ideas such as giving your boss an idea you came up with and not looking for credit or finding out the job no one else wants to do and taking it on yourself.<br />
<br /></div>
<style type="text/css">
p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px 'Helvetica Neue'; color: #454545}
p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px 'Helvetica Neue'; color: #454545; min-height: 14.0px}
</style>
<br />
<div class="p1">
This strategy will accomplish a number of things. It will keep your ego from getting to big. As you make those around you successful, you will also become more successful; the adage "a rising tide lifts all boats." Finally, if you're feeding ideas to your boss, or coworkers, then you will start steering the direction they are going.</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-19452212.post-19061870257428331412016-10-11T14:31:00.001-05:002016-10-11T14:31:28.546-05:00How to Measure ValueAgile is about delivering value, so it is important to understand the value you are delivering within an iteration or release. However, I seen many teams that focus on how many story points they deliver but not really thinking about the value of those story points.<br /><br />So are there ways to measure value? The answer is, of course there is. One way would be to use the Planning Poker approach, but instead of estimating the effort for each story you can estimate the value of the story. In this case, the team doing the work would include the product owner, any <a href="https://www.ibm.com/design/thinking/keys/sponsor-users/" target="_blank">sponsored users</a>, and other users or subject matter experts. Just as you would start with estimating effort, you would pick one feature or user story and assign it an arbitrary value, such as eight points. Then you would go through and assign values to each of the remaining features or user stories relative to that one.<br /><br />
From here, there are a couple more things you can do to refine your value measurement. One approach would be to divide the value of a story by the story estimate. For example if you had a three story point story with a value of three, you would have a feature of 1 value point/story point. Likewise if you had a one story point story with a value of three you would get a answer of three value points/story point, which would indicate that this would be a more valuable story based on the value per points.<br /><br />Another approach would be to calculate the cost of each user story. If you have a team that is pretty stable you can estimate how much it cost to perform an iteration. You should also know your velocity, so it's a simple math equation to come up with your cost per points. So for example if you had a five person team and average cost per person of $200/hour, you work that out for a two-week iteration you're looking at $80,000. if your velocity is 50 points then your cost per store is $1600 so an eight point story would cost $12,800.<br /><br />
So these are just a couple ways in which you can measure the value of what you're delivering. You could do something as simple as the T-shirt sizing approach, where a story may be small, medium, large, or extra-large in value. In any case you should look at someway to ensure that you are measuring the value you are delivering and not just the effort being completed. Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-19452212.post-61992476016645928912016-07-29T14:25:00.002-05:002016-07-29T14:25:26.922-05:00Empathy Mapping I ran an exercise at the beginning of a new project last week; Empathy Mapping. This is part of an overall approach of using Design Thinking along with agile development.<br />
<br />
The idea to empathy mapping is to get to understand your users. Per the diagram below, you want to get an understanding of what your user thinks, says, feels, and does (though I have seen other examples that are slightly different than this). You would do this mapping for your main users for your product or the problem you're trying to solve.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiXrVyQdGJXTJe5xUWfo5h0B4906uEVae5BSIbjNOBmeYVIIyle3kldzIIegKkOXYZ5LG9oUvwwmObaeDGjQfW2R3mU3rkjMhN_Ct-CdchycOBxigvMrmH29d6c_YYSPudBIPa6/s1600/Screen+Shot+2016-07-29+at+3.07.03+PM.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="211" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiXrVyQdGJXTJe5xUWfo5h0B4906uEVae5BSIbjNOBmeYVIIyle3kldzIIegKkOXYZ5LG9oUvwwmObaeDGjQfW2R3mU3rkjMhN_Ct-CdchycOBxigvMrmH29d6c_YYSPudBIPa6/s320/Screen+Shot+2016-07-29+at+3.07.03+PM.png" width="320" /></a></div>
<br />
<br />
To do this, you first want to identify the roles you are going to map. For each role, give them a name to personify it more. So don't call it Budget Approver, call her Laura. Draw out your map on a flipchart and draw a little sketch on Laura in the middle. Have the team talk a little about what Laura does, then have them start capturing these ideas on post-it notes and putting them on your flip chart. What you get is something like this:<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEisKrHVg4ub7RSc7VkbJP8PtvFYypHPMHmLqwH7viM5Qzf5Flm1CyiofcHzvlVQ5VLoX9K15d-J1L6kef-Qh6auHU_Ht6WX8wvhyphenhyphenYVBgRzpKae2uOmaqcbHdUIDKG4yrjzQfKP6/s1600/Screen+Shot+2016-07-29+at+3.12.04+PM.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEisKrHVg4ub7RSc7VkbJP8PtvFYypHPMHmLqwH7viM5Qzf5Flm1CyiofcHzvlVQ5VLoX9K15d-J1L6kef-Qh6auHU_Ht6WX8wvhyphenhyphenYVBgRzpKae2uOmaqcbHdUIDKG4yrjzQfKP6/s320/Screen+Shot+2016-07-29+at+3.12.04+PM.png" width="253" /></a></div>
<br />
<br />
Going through this exercise will help make some discoveries about what your users are going through. You can take this as a first step in identifying pain points; things you want to solve with your solution, but don't go into solutioning just yet. Take the observations and identify the themes that pop out. You can apply <a href="https://www.mindtools.com/pages/article/newTMC_86.htm" target="_blank">Affinity Diagraming </a>for some structure if needed.<br />
<br />
So now you are ready to get to insights. What does this really mean? Maybe it's time for the <a href="https://en.wikipedia.org/wiki/5_Whys" target="_blank">5-Whys</a> to help understand the situation. This is really the problem we're trying to solve. Now it's time to start discussing solutions.<br />
<br />
As you get into development, don't throw out your maps. Keep them posted on the walls in your team room. As you are making decisions later in the project, they may help guide you.Unknownnoreply@blogger.com0