<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Leo on Medium]]></title>
        <description><![CDATA[Stories by Leo on Medium]]></description>
        <link>https://medium.com/@leosc?source=rss-817289faa9d0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*XSm0TqmPkLyIllPfwkPAQA.jpeg</url>
            <title>Stories by Leo on Medium</title>
            <link>https://medium.com/@leosc?source=rss-817289faa9d0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 08:50:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@leosc/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Conectando o Jira com o Google Sheets para análise de métricas de fluxo]]></title>
            <link>https://leosc.medium.com/conectando-o-jira-com-o-google-sheets-para-an%C3%A1lise-de-m%C3%A9tricas-de-fluxo-a9ff20c13858?source=rss-817289faa9d0------2</link>
            <guid isPermaLink="false">https://medium.com/p/a9ff20c13858</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[charts]]></category>
            <category><![CDATA[metrics]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[kanban]]></category>
            <dc:creator><![CDATA[Leo]]></dc:creator>
            <pubDate>Wed, 16 Feb 2022 13:28:03 GMT</pubDate>
            <atom:updated>2022-12-14T12:51:02.972Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wx0EMPb8cmAZEAxS27fj2A.png" /></figure><p>Neste artigo explicarei como eu <strong>extraio </strong>os <strong>dados do Jira</strong> e os coloco em uma <strong>planilha de métricas</strong>, que me permite analisar alguns números dos times que trabalho. <br>O tutorial abaixo já existe no ‘<strong>README</strong>’ das planilhas, mas resolvi postar aqui para ter mais visibilidade e um alcance maior.</p><p>O processo de <strong>extração dos dados</strong> e <strong>colar </strong>no <strong>dashboard </strong>é muito <strong>simples </strong>(apesar do post <strong>extenso</strong>). <br>Tentei deixar o artigo bastante <strong>detalhado</strong>, e o <strong>processo </strong>de exportação o mais <strong>genérico </strong>possível para <strong>facilitar </strong>para todos 😃</p><p>Em um <strong>post anterior</strong>, mostrei como eu <strong>analiso as métricas dos times </strong>que trabalho: <br> — 🔗 <a href="https://leosc.medium.com/analyzing-team-metrics-11cd1cd379bb"><strong>Analyzing team metrics</strong> 📊</a> (em inglês)</p><h3><strong>📑 Conteúdo deste guia:</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/738/1*JShk1WWG3RjSm4avtkIGlw.png" /></figure><p><strong><em>❗ Disclaimer</em></strong></p><ul><li>A <strong>v01</strong> da ‘<strong>Kanban Metrics 🗄️ — data from Jira</strong>’ foi <strong>originalmente </strong>criada por <a href="https://www.linkedin.com/in/gabrielfaria/">Gabriel Faria</a>, eu apenas fui <strong>aprimorando </strong>e deixei da maneira como está <strong>hoje</strong>.</li><li>A <strong>v01 </strong>da ‘<strong>Kanban Metrics 📊 — dashboard</strong>’ foi desenvolvida <strong>originalmente </strong>pelo <a href="https://www.linkedin.com/in/rafaelzampieri/">Rafael Zampieri</a> todos os <strong>créditos </strong>para <strong>ele</strong>. <br>Eu <strong>melhorei </strong>algumas coisas e criei a aba ‘<strong>Other</strong>’ com <strong>cálculos extras </strong>para outros <strong>gráficos</strong>. 🔗 <a href="https://docs.google.com/spreadsheets/d/1YVhZ9gIqXNisRPIRF0W23u4iPYCcbf17LzRa3EbZnXA/edit#gid=2008256076"><strong>Link da planilha original — ‘Métricas</strong>’</a>.</li></ul><p>Para prosseguir, você precisará <strong>fazer uma cópia de cada uma das planilhas</strong>:</p><ul><li><a href="https://docs.google.com/spreadsheets/d/1IieENWgzYXQzHCYH7PgToXCJdJ-RpIYQ_7HuQh6JBmY/edit?usp=sharing">Template — Kanban Metrics 🗄️ — <strong>data from Jira</strong></a></li><li><a href="https://docs.google.com/spreadsheets/d/16K85B1fKLr_-mcCECWTL-yPr5PppUuLvbC1RNjwRsFE/edit?usp=sharing">Template — Kanban Metrics 📊 — <strong>dashboard</strong></a></li><li>Para facilitar, ambas ficam <strong>salvas </strong>nesta pasta do <strong>Google Drive</strong>: <br><a href="https://drive.google.com/drive/folders/1msFxPhCPKFrxM-BJWDeZEVSUNhHNbYbE?usp=share_link">📁 <strong>Connect Jira to Google sheets</strong></a></li></ul><p>De <strong>forma simples</strong> o fluxo é você <strong>extrair </strong>da ‘<strong>data from Jira</strong>’ &gt; <strong>colar </strong>os dados na ‘<strong>dashboard</strong>’.</p><h3>🗄️ <strong>Começaremos o tutorial com a 1º planilha: a Template — Kanban Metrics 🗄️ — data from Jira</strong></h3><ul><li>Link: <a href="https://docs.google.com/spreadsheets/d/1IieENWgzYXQzHCYH7PgToXCJdJ-RpIYQ_7HuQh6JBmY/edit?usp=sharing">Template — Kanban Metrics 🗄️ — <strong>data from Jira</strong></a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*01bW-DXNwgrv-I6u2QR1gQ.png" /></figure><p><strong>Como usar esta planilha? ❓</strong></p><h4><strong>1️⃣ Primeiro você precisa instalar a extensão ‘Jira Cloud for Sheets’ no Google Sheets:</strong></h4><p>👉 <strong>Complementos </strong>&gt; Instalar <strong>complementos </strong>&gt; Pesquise por ‘<strong>Jira Cloud for Sheets</strong>’</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kZF_h1QPBppkSUEkxajeGA.png" /></figure><p>📝 <strong>Siga as instruções</strong> no complemento para conectar sua conta do Jira.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xxjXV-EBUArAcEG2COEF8Q.png" /></figure><p><strong>Após </strong>a instalação, vá até <strong>Complementos </strong>&gt; <strong>Jira Cloud for Sheets</strong> &gt; Clique em ‘<strong>Abrir…</strong>’ &gt;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/863/1*AfBZC6UmffWxCAOS_Zdrew.png" /></figure><p>Agora, siga o <strong>passo a passo</strong> para conectar com o Jira.<br><strong>Depois </strong>que o Jira estiver <strong>conectado</strong>, <strong>ative </strong>o método de importação ‘<strong>=Jira()</strong>’:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/773/1*Spjh1RaN05idUn11FZ8kGA.png" /></figure><p>Ok, <strong>você conectou</strong> o Jira no Google Sheets! 🎉<br><strong>Agora </strong>iremos <strong>pegar </strong>os dados do Jira para usar em nosso ‘Template — Kanban Metrics 📊’</p><h4><strong>2️⃣ Insira a JQL do Jira para selecionar todos os dados que deseja ver na planilha Template — Kanban Metrics 📊:</strong></h4><p>Eu recomendo que você <strong>teste a</strong> <strong>JQL primeiro </strong>no <strong>Jira </strong>para ver se está <strong>funcionando</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R0TArD05JbA7-jdv8t_XVA.png" /></figure><p><strong><em>⛔ Por favor, leia com atenção: 👇<br></em></strong>Você <strong>substituirá </strong>a JQL na célula <strong>A2 </strong>da aba ‘<strong>Jira data</strong>’ (em <strong>verde</strong>), mas <strong>não modifique </strong>o trecho em <strong>vermelho</strong>, pois são <strong>campos necessários </strong>para montar a <strong>matriz de transições dos cards </strong>do Jira:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/478/1*a9M3HqcPYQdQWpR5Rn_owg.png" /></figure><p><strong>Substitua o trecho abaixo</strong>, marcado em <strong>azul</strong>, na célula ‘<strong>A2</strong>’ da aba ‘<strong>Jira Data</strong>’ com a <strong>sua JQL</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/661/1*Ya_okPb3-aLTkxT2GBe6-w.png" /></figure><p>⏳ <strong>Aguarde </strong>o <strong><em>loading </em></strong>dos dados:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/671/1*IW1v8flUV1-DFmTIyjdZkA.png" /></figure><p>✅ Dados <strong>carregados</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eVjUoVrBaIXSB7-M" /></figure><p><strong><em>🐞 Alguns problemas conhecidos:<br></em></strong>Se você tiver <strong>muitas issues</strong> e <strong>transições </strong>em seu fluxo de trabalho, talvez <strong>receba </strong>uma mensagem de <strong>‘timeout’</strong>. (nem sempre acontece).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/578/1*vW4gX_nq91VxxxsFvCoqyw.png" /></figure><p>Esse é um <strong>limitador </strong>do Google Sheets e Jira, onde a consulta deve retornar os dados <strong>em até 30 segundos</strong>, senão ocorre o <em>timeout</em>. <br>Eu <strong>sugiro </strong>você rodar mais algumas vezes a JQL para testar, e caso <strong>continue </strong>com a mensagem, você <strong>precisará </strong>pegar as <em>issues </em>em <strong>lotes menores</strong>, usando o <strong>filtro </strong>de <strong>data </strong>(eu explico abaixo).</p><h4><strong>3️⃣ Agora, insira os status do seu fluxo de trabalho do Jira na guia ‘Index’ — célula E2:</strong></h4><p>Você encontrará o status das etapas do seu fluxo do Jira aqui (<strong>Board settings</strong> &gt; <strong>Columns</strong>):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3H_wooLF3TrI9tlU" /></figure><p><strong>Adicione aqui </strong>os <strong>status </strong>do seu board do Jira. Coloque os status na <strong>mesma ordem </strong>de suas <strong>colunas </strong>do Jira. E escreva na <strong>coluna E </strong>da <strong>mesma maneira </strong>que está na <strong>coluna A</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*btjBz3L7cm0Wew1v" /></figure><p><strong><em>❗❗ Atenção:<br></em></strong>Você <strong>precisará </strong>adicionar um <strong>‘espaço’ </strong>depois de <strong>incluir </strong>o status do Jira. Caso contrário, a <strong>‘Position’ não será preenchida</strong>.</p><p>✅ <strong>Correto </strong>(com o espaço no final):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1021/0*qtvgzHWX5qHbNpSE" /></figure><p>Sem o <strong>espaço</strong>, a ‘posição’ ficará em <strong>branco.<br></strong>❌ <strong>Incorreto </strong>(sem o espaço no final)<strong>:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1021/0*GLjruhR1VRC6CaE2" /></figure><h4><strong>4️⃣ Copie os dados formatados de 4.Data ready — copy from here! para a planilha Template — Kanban Metrics 📊</strong></h4><p>Vá até a aba <strong>4.Data ready</strong> e note que seus cards do Jira estarão lá com as etapas do seu <strong>fluxo </strong>de trabalho preenchido com datas:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ijvb0jQtK6bxOfZg" /></figure><p>Agora, <strong>vá até a célula A1</strong> e selecione tudo (<strong>CTRL+A</strong>):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Gv2DFirOufSgfxHL" /></figure><p><strong>Pronto</strong>!🎉 Você <strong>preparou </strong>os dados do Jira para serem <strong>adicionados </strong>na planilha de <strong>métricas</strong>, <strong>continuaremos </strong>agora na <strong>próxima </strong>planilha. 👇</p><h3>📊 <strong>Seguiremos o tutorial na 2º planilha: Template — Kanban Metrics 📊 — dashboard</strong></h3><ul><li>Link: <a href="https://docs.google.com/spreadsheets/d/16K85B1fKLr_-mcCECWTL-yPr5PppUuLvbC1RNjwRsFE/edit?usp=sharing">Template — Kanban Metrics 📊 — <strong>dashboard</strong></a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Gat7GxFrZPtEzBBr" /></figure><h4><strong>1️⃣ Abra a sua cópia da planilha e vá até a aba ‘Team 1’ ou ‘Team 2’, que é onde iremos colar os dados da planilha anterior.</strong></h4><p><strong>Vá </strong>até a ‘<strong>célula A1</strong>’ da aba ‘Team 1’ ou ‘Team 2’:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TL6cF4Hh0e0wLZcq" /></figure><p><strong>Cole os dados</strong> na aba ‘Team 1’, célula <strong>A1</strong>.<br>Use <strong>CTRL + SHIFT + V</strong> para ‘colar<strong> somente os valores</strong>’ ou clique com o <strong>botão direito </strong>do mouse e selecione ‘Colar especial &gt; Só os valores’:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QEs8oFI7eThBdHt_NvdeHg.png" /></figure><p><strong><em>❗❗ Atenção:</em><br></strong>Caso o <strong>CTRL + SHIFT + V</strong> <strong>não funcione </strong>para você, <strong>provavelmente </strong>você precisará <strong>instalar </strong>a <strong>extensão </strong>‘<a href="https://chrome.google.com/webstore/detail/google-docs-offline/ghbmnnjooekpmoecnnnilnnbdlolhkhi"><strong>Documentos Google off-line</strong></a>’ que <strong>habilita </strong>as <strong>funções </strong>de CTRL+SHIFT+V no Google Sheets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/746/0*M0jiZXOnWOJBkUhC" /></figure><h4><strong>2️⃣ Volte para a aba ‘📊 Dashboard’ e configure sua coluna de ‘backlog’ (célula H5), ‘commitment point’ (célula J4) e ‘delivery point’ (célula J5):</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tcufoHDkCUrrsXf1" /></figure><p><strong>⏳ Aguarde </strong>a planilha carregar todas as <strong>fórmulas </strong>antes de prosseguir:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/722/0*EsyvKMafKMTMOAS6" /></figure><h4><strong>3️⃣ Verifique se todos os gráficos estão funcionando:</strong></h4><p>Eu <strong>tentei automatizar </strong>todos os gráficos, mas posso ter esquecido de algum, e erros acontecem 😬<br><strong>👇 </strong>Se der <strong>problema </strong>em <strong>algum </strong>deles, <strong>siga os passos abaixo</strong>:<br>— Verifique na <strong>origem dos dados</strong> se há algum <strong>erro</strong>:<br> — — Caso tenha, <strong>provavelmente </strong>é algum erro ao <strong>colar </strong>os <strong>dados </strong>na aba ‘Team 1’ ou ‘Team 2’</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OpTQYlc8kvPd_IHN" /></figure><p><strong>📅 Filtre o período de datas</strong> que você sabe que teve <strong>entregas </strong>para visualizar:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_2hvHjsY2mIGHdwR" /></figure><p><strong><em>❗❗ OBS</em></strong><em>:</em><br>A planilha sempre pegará dados <strong>da semana completa</strong>, ou seja, se você <strong>selecionar 3 dias </strong>de <strong>1</strong> <strong>semana</strong>, ele trará dados da <strong>semana inteira</strong>. <br>Isso acontece pois boa parte das informações estão em lotes de semana:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2_MG85labmIikK14" /></figure><h3><strong>💡 Dicas gerais</strong></h3><h4><strong>1 — Há muitos gráficos úteis nesta planilha</strong>, eu <strong>recomendo </strong>que você <strong>primeiro 🔎 ‘diminua o zoom’ (50%)</strong> para ver tudo e depois analise cada um para <strong>entender </strong>melhor:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VNSA6gNPyGUucHu_" /></figure><p>Sério, é muita coisa 😅</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2zrCBJxnNNARZywt" /></figure><h4><strong>2 — Todos os gráficos são calculados em 2 abas da planilha:</strong></h4><ul><li><strong>‘Data’ </strong>— aba original da planilha modelo, com a maioria dos cálculos;</li><li><strong>Other’ </strong>— aba que eu criei para não modificar a ‘data’ com diversos cálculos para outros gráficos que eu criei.</li></ul><h4><strong>3 — A aba ✍ Summary (beta) </strong>serve como um <strong>‘resumo’ </strong>com alguns <strong>gráficos importantes</strong> — caso queira um resumo <strong>rápido </strong>das informações, ou até <strong>enviar </strong>como <strong>‘status report’:</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*znI_eJKj9eOdViSd" /></figure><h4><strong>4 — Use 1 planilha por time / área / objetivo</strong></h4><p>A planilha <strong>permite </strong>inserir dados de <strong>várias equipes </strong>(abas Team 1, Team 2…), mas para <strong>melhor organização </strong>eu <strong>sugiro </strong>que você use 1 planilha por equipe. Mas claro,<strong> fique a vontade</strong> de usar da maneira que quiser 😃</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/925/0*HbmhFxid4VzuZD5z" /></figure><p><strong>Exemplo </strong>de como eu utilizo:<br><strong>1 planilha de exportação</strong> 🗄️ para cada equipe/área/objetivo:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/447/0*Sp5FOe6YGinNc4TT" /></figure><p><strong>1 planilha de dashboard</strong> 📊 para cada equipe/área/objetivo:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6HNsWd__Fx2fu0dT" /></figure><h4><strong>5 — Utilize o campo de data para filtrar períodos menores:</strong></h4><p>Caso você queira trazer dados do Jira de <strong>determinado período</strong> basta adicionar na JQL: <strong><em>AND updated &gt;= “&amp; E1 &amp;” </em></strong>e coloque a data na célula <strong>E1</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qe3aHFt_nH3T195A" /></figure><h4>6 — Alterar o lead time de dias corridos para dias úteis</h4><p>O <strong>lead time </strong>na planilha está em <strong>dias corridos</strong>, caso você queira ver em <strong>dias úteis</strong>:</p><p>Vá até a célula ‘<strong>AB5</strong>’ da aba ‘<strong>Data</strong>’ e altere a fórmula:<br>de <strong>=IF(W6&lt;&gt;””;W6-V6+1;)</strong> <br>para: <strong>=IF(W5&lt;&gt;””;NETWORKDAYS(V5;W5);””) <br></strong>e arraste para o restante das células AB:</p><p><strong>📅 Em dias corridos:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YhGII2-QPcz-E15O" /></figure><p><strong>📅 Em dias úteis:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uNY34ubs6WUyPfmB" /></figure><h4><strong>7— Como atualizar os dados:</strong></h4><p>Eu atualizo os dados <strong>1x por semana</strong>, para atualizar você pode ir no menu:<br><strong>Extensões </strong>&gt; <strong>Jira Cloud for Sheets</strong> &gt; <strong>Open…</strong> &gt; <strong>Get issues from Jira</strong> &gt; <strong>Get Issues Now</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XlIp2thjCmMQoML9" /></figure><p>Eu acho esse <strong>caminho acima muito longo</strong>, e atualizo da <strong>seguinte maneira</strong>:<br>Vou na <strong>célula A2</strong>: <strong>Clique duplo</strong> 👉 <strong>CTRL+A</strong> 👉 <strong>CTRL+X </strong>👉 <strong>Enter </strong>👉 <strong>CTRL+V</strong> 👉 <strong>Enter</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XMmdRDeCHl3u-xIo" /></figure><h4>📝 <strong>Note-to-self</strong>: Adicionar botão para atualizar com 1 clique 😅</h4><p>Sim, você precisa atualizar <strong>manualmente </strong>de uma planilha para a outra sempre que quiser os dados mais <strong>recentes</strong>.</p><p>Eu havia <strong>feito </strong>uma maneira de ter tudo na mesma planilha de <strong>forma automática</strong>, mas ficou muito <strong>pesado </strong>e ficou meio <strong>inviável</strong>. <br>É <strong>possível </strong>utilizando a <strong>API</strong> do Jira, mas pretendo fazer isso só mais para <strong>frente</strong> 😀</p><p>Bom, é isso! 🏁</p><p><strong>Quaisquer dúvidas</strong> podem entrar em contato <strong>comigo </strong>através do <strong>LinkedIn</strong>:<strong>💬 </strong><a href="https://www.linkedin.com/in/leonardosc/">in/leonardosc</a></p><h4>🔗 Aqui os <strong>links </strong>novamente:</h4><ul><li>📁 <a href="https://drive.google.com/drive/folders/1msFxPhCPKFrxM-BJWDeZEVSUNhHNbYbE?usp=share_link"><strong>Connect</strong> Jira to Google sheets</a> — <strong>pasta do Drive </strong>com as planilhas abaixo 👇</li><li>🗄️ <a href="https://docs.google.com/spreadsheets/d/1IieENWgzYXQzHCYH7PgToXCJdJ-RpIYQ_7HuQh6JBmY/edit?usp=sharing">Template — Kanban Metrics 🗄️ — <strong>data from Jira</strong></a></li><li>📊 <a href="https://docs.google.com/spreadsheets/d/16K85B1fKLr_-mcCECWTL-yPr5PppUuLvbC1RNjwRsFE/edit?usp=sharing">Template — Kanban Metrics 📊 — <strong>dashboard</strong></a></li></ul><h4>👉 <a href="https://leosc.medium.com/analyzing-team-metrics-11cd1cd379bb"><strong>Analyzing team metrics</strong> 📊</a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a9ff20c13858" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Analyzing team metrics ]]></title>
            <link>https://leosc.medium.com/analyzing-team-metrics-11cd1cd379bb?source=rss-817289faa9d0------2</link>
            <guid isPermaLink="false">https://medium.com/p/11cd1cd379bb</guid>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[metrics]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Leo]]></dc:creator>
            <pubDate>Wed, 13 Oct 2021 11:40:00 GMT</pubDate>
            <atom:updated>2021-10-14T03:48:46.520Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*azfY_0cWjScGv2JOSSjU9g.png" /><figcaption>I would like to thank Rafael Zampieri for originally making this Google spreadsheets.</figcaption></figure><p><strong>Disclaimer</strong>: I’m practicing my English writing skills so if you notice any mistakes please feel free to contact me 😅</p><p>In this article, I’ll show you guys what type of information (and charts) I use with the teams I work with. But first, I’ll give you a little brief about the 3 main Kanban metrics that you need to collect and have in hand before analyzing the data.</p><p>Using the definition from <a href="https://resources.kanban.university/wp-content/uploads/2021/06/The-Official-Kanban-Guide_A4.pdf"><em>The Official Kanban Guide</em></a>:</p><ul><li><strong>Lead time:</strong><br>It’s the time it takes for a single work item to pass <strong>through </strong>the system from the <strong>start </strong>(commitment point) to <strong>completion</strong>;</li><li><strong>Throughput (or delivery rate):</strong><br>It’s the number of <strong>completed </strong>work items per unit of <strong>time</strong>, such as<strong> features per week</strong>, training classes per month, or new hires per month;</li><li><strong>WIP (work in progress):</strong><br>It’s the <strong>amount </strong>of work items in the system (or a defined part of it) at a <strong>certain </strong>point in time;</li></ul><p>I won’t get into specific details about the above but if you want to know more I recommend you this: <a href="https://getnave.com/blog/kanban-metrics/"><em>What to Measure and Why: Kanban Metrics</em></a><em> (Nave)</em></p><p>I’ll start with the 🔢 <strong>throughput </strong>(or delivery rate).</p><h4><strong>Weekly throughput</strong></h4><p>The first chart I like to use is the weekly throughput, so I can visualize if the team is delivering <strong>frequently</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*de7LRX3ctmRmBKy4" /></figure><p>But what is the team delivering? How many work items are <strong>💎features</strong>? What about <strong>🐞bugs</strong>? So usually I break down the <strong>delivery by work item type</strong>:</p><h4><strong>Weekly throughput by work item type</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6MVpLHWIV7oiV9Ru" /></figure><p>Looking at this chart I can notice that this specific team was working with <strong>support </strong>items at the beginning and now they are dealing with <strong>improvement </strong>items (in our context it’s <strong>engineering </strong>and code improvements).</p><ul><li>Well, maybe we are dealing with <strong>refactoring</strong>?</li><li>Is our codebase getting more <strong>efficient</strong> with all these improvements?</li></ul><p>In the first <strong>18 weeks</strong> (or <strong>4 months</strong>) the delivery average was <strong>2,3 work items per week</strong>. Since then, we are delivering <strong>4,7 work items per week</strong>.</p><ul><li>What happened?</li><li>What caused this difference?</li></ul><p>In the last 3 weeks we delivered 3 items. Again, you can ask the team:</p><ul><li>What happened?</li></ul><p>It’s important to ask the teams these questions to <strong>bring them together </strong>looking at all these data.</p><p>When you have the delivery rate and the specific date periods, you can also track the <strong>average</strong> <strong>throughput</strong> in the period and the <strong>delivery rate per day</strong>:</p><h4><strong>Average throughput in the period</strong></h4><p>In this example, it’s total throughput in the period/qty of weeks = <strong>114</strong> items / <strong>30</strong> weeks = <strong>3.8 items per week</strong></p><h4>Delivery rate per day</h4><p>Total throughput in the period / qty of days = <strong>114 </strong>items / <strong>150 </strong>days = <strong>0.76 items per day<br></strong>Or average throughput (<strong>3.8</strong> items) / <strong>5</strong> days = <strong>0.76 items per day </strong>(to make it easy 😅)</p><p>Every team has a <strong>different context</strong>, so be careful not to be too judgmental in your analysis and how you talk to the team. The idea is to <strong>analyze the data and not the people</strong>.</p><p>I like to visualize the <strong>throughput by month</strong>, too:</p><h4>Monthly throughput</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9AT3QltbQVRApdh5" /></figure><p>Looking at the chart above, you can see that the team never delivered <strong>more than 12 items </strong>in the first <strong>7</strong> months together.</p><p>So what <strong>happened </strong>after that?</p><ul><li>What caused you to jump from <strong>12 </strong>items delivered to <strong>27</strong>?</li><li>Is the work batch <strong>smaller</strong>?</li><li>Has any <strong>expedite/urgent</strong> work happened?</li><li>Do we have more <strong>people </strong>on the team?</li></ul><p>So with these 2 charts (<strong>weekly</strong> and <strong>month throughput</strong>), you can analyze different types of suppositions you have.</p><p>When you split your deliveries by week and month maybe you want to see the <strong>total of deliveries by work type</strong>. So, the next chart is this one:</p><h4><strong>Deliveries by work type</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AaUR088DScmAecKt" /></figure><p>As you can see the team is indeed working on lots of <strong>improvement</strong>.</p><p>As an alternative, you can use the <strong>pie chart </strong>to see the <strong>% </strong>too, but usually, a pie chart with <strong>more than 5 categories</strong> is bad to visualize:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*3Q5lMWU50spdte_t" /></figure><p>Now let’s talk about 🕔 <strong>lead time.</strong></p><h4><strong>Lead time control chart</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6ndgC8yx6eyTTtac" /></figure><p>This one is a good visualization of each task lead time, I use it <strong>together </strong>with the one below:</p><h4><strong>Lead time histogram</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DwRNraJ5aFk_3s7m" /></figure><p>Histograms are great to answer the question ‘<strong>usually, the team delivers an item in how many days?</strong>’ (not only this question, ok?) and you can cross a line in certain <strong>percentiles </strong>to have a better idea of your data set.</p><p>Looking at the chart above, you can see the <strong>p75% line</strong> is at <strong>12 days</strong>. What does it mean?</p><p>👉 <strong>It means that this team delivers an item in 12 days, 75% of the time</strong>.</p><p>Usually, I like to see the <strong>average</strong>, <strong>mean</strong>, <strong>p60%</strong>, <strong>p75%</strong>, and <strong>p90%</strong>.</p><p>There are <strong>different patterns </strong>of a histogram, you can check it here:</p><ul><li>🔗<a href="https://getnave.com/blog/histogram-diagram/"> Frequency Distribution: Histogram Diagrams</a> (Nave)</li><li>🔗 <a href="https://connected-knowledge.com/2014/09/06/analyzing-lead-time-distribution-chart/">Analyzing the Lead Time Distribution Chart</a> (Connected Knowledge)</li></ul><h4><strong>Lead time by work item type</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bRfQoRlbzam7fgI-" /></figure><p>Drilling down in the lead time numbers, I like to use the <strong>75th percentile</strong> because it gives you a little more <strong>certainty </strong>about your <strong>delivery patterns</strong>. You can use the <strong>average </strong>too, but averages usually are a bit more <strong>sensible </strong>to outliers and this can <strong>skew </strong>your data set.</p><p>Let’s take a look at the chart above, you can notice that ‘<strong>support</strong>’ items have a <strong>75% chance of being delivered in 4 days</strong>. <strong>Stories, 75% of the time, are delivered in 20 days</strong>.</p><p>So when you break down your work items by type you will have <strong>a more precise analysis</strong>, just like we did analyze the delivery rate.</p><h4><strong>Time in status</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BG-XySCbXnA50Pz7" /></figure><p>I like to use this one to have a better idea of where our flow’s <strong>bottlenecks </strong>are. It’s a great tool to see if your workflow has a <strong>pattern </strong>of ‘tasks are always more than<strong> X</strong> days in this <strong>column’</strong>.</p><p>💭 My <strong>insights </strong>looking at the chart above:</p><ul><li>Most of the items went <strong>quickly </strong>through our flow, so they were <strong>created</strong>, pulled into <strong>dev</strong>, and <strong>delivered</strong>;</li><li>Despite the <strong>high customer lead time</strong> in the <strong>6 outlier items</strong>, <strong>the system lead time was low</strong>, so the work spent more time in ‘<strong>waiting</strong>’ stages before commitment (which can be a <strong>problem</strong>, too)</li></ul><h4><strong>Backlog aging chart</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/987/0*Gh19tq_Y0eUrLgpM" /></figure><p>I like to use this one to visualize how <strong>old </strong>my backlog items are. As we can see above, some items are more than <strong>330 days </strong>in the backlog.</p><p>When you look at something like this, you can ask the team:<strong> Is this work item still necessary</strong>?</p><p>Sometimes when you have an <strong>extensive </strong>backlog, you certainly will <strong>forget </strong>about less prioritized items. This is an excellent chart to start an<strong> explicit policy</strong> like ‘start discarding things that we know we won’t do’.</p><p>Maximizing the work not done is a thing.😀</p><h4><strong>Average weekly WIP</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VDXjPNCxoAmf25Fv" /></figure><p>This is one of the most important charts here. It will show you<strong> how many items are in progress</strong> (or after the <strong>commitment </strong>point) on average per week. It’s good to help you visualize if the team is <strong>overwhelmed with work on a weekly basis</strong> and the moving average.</p><p>You can see that this team had a <strong>big spike </strong>in WIP on May-21 and July-21. After the last spike, the moving average went <strong>down</strong>.</p><ul><li>Did you <strong>limit </strong>your WIP?</li><li>Maybe the team is working on <strong>pair programming</strong>?</li></ul><p>I combine the chart above with this one 👇:</p><h4><strong>Work item input vs Throughput vs Average WIP</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kMZezZY4Mb-2htqSXjF4HA.png" /></figure><p>I like to use this one to <strong>compare </strong>how many items the team is <strong>pulling </strong>and how many are being <strong>delivered</strong>. It’s a good tool to visualize the <strong>balance </strong>between work items <strong>in </strong>and <strong>out </strong>of your workflow, and the average WIP.</p><h4><strong>Cumulative Flow Diagram (CFD)</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hjbzN3XDVKxstmXg" /></figure><p>I don’t use the CFD as much as I should, I think. Usually, I look at it but I keep to <strong>myself </strong>because it can be a little <strong>difficult </strong>for the team to understand what it <strong>means</strong>. Of course, it depends on the team’s <strong>maturity</strong>, if they are <strong>used </strong>to looking and understanding the flow metrics maybe you should show them <strong>frequently</strong>.</p><p>The CFD is one of the <strong>best ways</strong> to see a lot of <strong>patterns</strong> in your team workflow and can help you with so many thing, here is a good source to help you:</p><ul><li>🔗 <a href="https://getnave.com/blog/kanban-cfd-patterns/">Reading the Signs: Kanban CFD Patterns</a> (Nave)</li></ul><p>Well, I think that’s it! This article became longer than I planned, but I hope it can help you to start looking and analyzing your team’s deliveries.</p><p>If you have any questions, you can 💬 <a href="https://www.linkedin.com/in/leonardosc/">contact me on LinkedIn</a>.</p><p><strong>🔗 References:</strong></p><ul><li><a href="https://resources.kanban.university/wp-content/uploads/2021/06/The-Official-Kanban-Guide_A4.pdf">The Official Kanban Guide</a></li><li><a href="https://getnave.com/blog/kanban-metrics/">What to Measure and Why: Kanban Metrics</a></li><li><a href="https://getnave.com/blog/histogram-diagram/">Frequency Distribution: Histogram Diagrams</a></li><li><a href="https://connected-knowledge.com/2014/09/06/analyzing-lead-time-distribution-chart/">Analyzing the Lead Time Distribution Chart</a></li><li><a href="https://getnave.com/blog/kanban-cfd-patterns/">Reading the Signs: Kanban CFD Patterns</a></li><li><a href="https://getnave.com/blog/how-to-read-the-cumulative-flow-diagram-infographic/">How to Read the Cumulative Flow Diagram [Infographic]</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11cd1cd379bb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[PSM I - Professional Scrum Master I - My study guide]]></title>
            <link>https://leosc.medium.com/psm-i-professional-scrum-master-i-my-study-guide-1c6060e9b59d?source=rss-817289faa9d0------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c6060e9b59d</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum-master]]></category>
            <dc:creator><![CDATA[Leo]]></dc:creator>
            <pubDate>Mon, 20 Sep 2021 03:46:46 GMT</pubDate>
            <atom:updated>2021-09-20T03:46:46.454Z</atom:updated>
            <content:encoded><![CDATA[<p>🆕 This article is a translated version of this one in Portuguese: <br>🔗 <a href="https://www.linkedin.com/pulse/psm-i-professional-scrum-master-my-study-guide-santos-costa/">Certificação PSM I - Professional Scrum Master I</a> (2019)<br>All links are updated to the Scrum guide&#39;s newest version.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yHcYvk7Iyuf-O5zR" /></figure><p>Hey guys! I have taken the <strong>PSM I — Professional Scrum Master I</strong> certification from <a href="https://www.linkedin.com/company/scrum-org/">Scrum.org</a>, one of the most respected for those who want to follow the path of <strong>Scrum Master</strong>, <strong>Agile Coach</strong> among others.</p><p>I will share with you my <strong>study plan</strong> to take one of my goals for the 1Q2019 off the paper 😃</p><p>The assessment has <strong>80 questions</strong>, and you have <strong>60 minutes</strong> to finish it. It costs <strong>US$150</strong> and can be done online 🔗 <a href="https://www.scrum.org/professional-scrum-master-i-certification">through this link</a>.</p><p>Below is a <strong>summary</strong> with some tips that helped me prepare for the assessment:</p><h3>1. Read and understand the Scrum Guide (not memorize, but understand it)</h3><p>If English <strong>is not</strong> your <strong>mother language</strong>, I recommend you to read <strong>first </strong>in your <strong>native </strong>language until you <strong>understand </strong>the <strong>concepts </strong>behind the guide. <strong>Then </strong>read in English. It is important to feel <strong>comfortable </strong>with the terminology used as the test is in English. (again, only if your native language isn’t English) — 🔗 <a href="https://scrumguides.org/docs/scrumguide/v2020/2020-Scrum-Guide-US.pdf">Scrum Guide link</a></p><h3>2. Read and understand the Agile Manifesto</h3><p>The assessment includes questions not only about Scrum, but Agile manifesto and Scaled Scrum (Nexus) too. — 🔗 <a href="https://agilemanifesto.org/">Agile Manifesto</a></p><h3>3. Read the Nexus Guide</h3><p>Some questions <strong>addresses Scaled Scrum</strong>, so I recommend you to read the Nexus Guide — 🔗 <a href="https://scrumorg-website-prod.s3.amazonaws.com/drupal/2021-01/NexusGuide%202021_0.pdf?nexus-file=https%3A%2F%2Fscrumorg-website-prod.s3.amazonaws.com%2Fdrupal%2F2021-01%2FNexusGuide%25202021_0.pdf">Nexus Guide</a></p><h3>4. Practice using Scrum quizzes!</h3><p>The most important thing is to<strong> practice constantly</strong>. I used these 3 websites to practice:</p><ul><li>🔗 <a href="https://www.scrum.org/open-assessments/scrum-open">Scrum Open</a> — <strong>30 random questions</strong> (it’s a database of 40 questions, so it’s pretty easy to go through them all). <strong>The official test uses the same platform as this one</strong>, so it’s worth getting familiar with the platform. About <strong>10% of the test questions</strong> are identical to this assessment.</li><li>🔗 <a href="https://mlapshin.com/index.php/scrum-quizzes">Mikhail Lapshin </a>— One of the biggest PSM I questions database (if not the biggest). Kudos to Mikhail for doing this amazing job.</li><li>🔗 <a href="https://www.volkerdon.com/bundles/scrum-certifications">Volkerdon</a> — This one is <strong>paid</strong>, but it’s <strong>worth every cent</strong>. It’s only <strong>US$17</strong>. The questions are very <strong>similar </strong>to the <strong>official exam </strong>and has a <strong>course </strong>that addresses <strong>100% </strong>of what is asked on the exam. By far, the one that <strong>prepared me the most</strong> for the test.</li></ul><p><strong>Practice </strong>until you keep getting <strong>90% ~100% right</strong>, and after that you can go to the official one very <strong>comfortable </strong>because you will be <strong>prepared</strong>. 😀</p><h3>💡 Another tips</h3><p><strong>It’s important to note</strong> that the official assessment takes into account what Scrum Guide <strong>says</strong>. We often <strong>adapt the Scrum framework to meet the company’s needs</strong>, and we can get questions wrong by answering for what we do, instead of following the guide.</p><h3>Be careful with some verbs in English:</h3><p><strong><em>“Attend”</em> and <em>“Participate”</em></strong></p><p><strong>Example</strong>: The sentence “Product Owner can <strong>attend </strong>the Daily Scrum” is true ✔️ while the sentence “Product Owner can <strong>participate </strong>in the Daily Scrum” is false. ❌</p><p><strong><em>“Accountable”</em> and <em>“Responsibility”</em></strong></p><p><strong>Example</strong>: The Product Owner can delegate some of his/her <strong>responsibilities </strong>to the Development Team. However, the Product Owner remains <strong>accountable</strong>.</p><p><strong><em>“Could” </em>and <em>“Should”</em></strong></p><p><strong>Example</strong>: The sentence “Product Owner could attend the Daily Scrum” ✔️ “Product Owner should attend the Daily Scrum” ❌</p><h3>Here are my results by focus area:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/867/0*aDlzn27Cex_XViHm" /></figure><h3>My quizzes results:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/677/0*8Z8jc9t0OH2mwNPl" /></figure><p>It’s important to say being a Scrum Master/Agile Coach certified isn’t the <strong>most </strong>important thing. How you <strong>deal </strong>with the day-to-day problems and observing your team’s environment and health, is something that sometimes can be better than Y or X certification.</p><h3>🔗 Another important links:</h3><ul><li><a href="https://www.linkedin.com/pulse/my-experience-becoming-certified-scrum-master-joris-vleminckx-pmp/">My experience in becoming a certified Scrum Master (PSM I)</a></li><li><a href="http://www.ru-rocker.com/2017/02/19/preparing-your-professional-scrum-master-1-psm1-certification/">Preparing for your Professional Scrum Master I Certification</a></li><li><a href="https://www.scrum.org/forum/scrum-forum/7198/passes-psm1-938-first-attempt-experience-share-tips">Passes PSM1 with 93.8% First Attempt (Experience Share + Tips)</a></li><li><a href="https://www.volkerdon.com/pages/psm-1-exam-tips">Volkerdon — How to pass PSM 1 exam</a></li><li><a href="https://www.infoq.com/minibooks/scrum-xp-from-the-trenches-2/">Scrum and XP from the Trenches — 2nd Edition</a></li><li><a href="https://www.scrum.org/Resources/Scrum-Glossary">Scrum Glossary</a></li></ul><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/psm-i-professional-scrum-master-my-study-guide-santos-costa/"><em>linkedin.com</em>/leonardosc</a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c6060e9b59d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>