<?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 Janee Sanders McConnell on Medium]]></title>
        <description><![CDATA[Stories by Janee Sanders McConnell on Medium]]></description>
        <link>https://medium.com/@janeesandersmcconnell?source=rss-d73b84512731------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*xS8z4okOV41RUU9q.</url>
            <title>Stories by Janee Sanders McConnell on Medium</title>
            <link>https://medium.com/@janeesandersmcconnell?source=rss-d73b84512731------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 21:41:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@janeesandersmcconnell/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[Embracing Change — Our Journey from Scrum to Kanban]]></title>
            <link>https://medium.com/@janeesandersmcconnell/when-this-little-start-up-with-big-dreams-was-born-a-couple-years-ago-i-wasnt-even-an-agile-coach-b10761de6d6c?source=rss-d73b84512731------2</link>
            <guid isPermaLink="false">https://medium.com/p/b10761de6d6c</guid>
            <category><![CDATA[scrum-master]]></category>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrumban]]></category>
            <dc:creator><![CDATA[Janee Sanders McConnell]]></dc:creator>
            <pubDate>Fri, 27 Jul 2018 18:54:08 GMT</pubDate>
            <atom:updated>2018-07-27T22:49:35.332Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PxJWKAkLCMRCdcBqBe2o3w.jpeg" /></figure><p>When this little start up with big dreams was born a couple years ago, I wasn’t even an Agile coach yet, I was a preschool teacher. (<em>which, coincidentally, has really served me surprisingly well in this new role, but more on that some other time.</em>) So if you had asked me what Agile was, I would have probably said, “Making a butterfly out of tissue paper at the art table while setting up snack and resolving a toddler toy dispute all at the same time” And while that’s not a <em>wrong</em> answer, it’s not the particular kind of Agile that I use to define myself these days, even though my craft skills do still come in handy from time to time :)</p><p>Fast forward to my arrival on my current team as an Agile Coach newbie; ready and eager to learn <strong>all</strong> the things, and put them into practice wherever and whenever I could. I’m told that the development processes that the original engineering team were using to start out with were fairly informal, and a light mix of ad hoc Agile practices, which was all they really needed at the time. After taking the time to better understand the team, their scope of work, how they had evolved in their development processes, I suggested that we start using a more traditional Scrum model and just try it out. So, we tried Scrum for a while, but it didn’t feel like a great fit for our team for a variety of reasons. I got my Scrum Master certification so that I could learn more, and I really loved having the opportunity to chat with other Agile Coaches, Project Managers, Product Owners and Scrum Masters and learn from all of their anecdotes and stories from the trenches. I was soaking it all up, and I felt like I had a much better understanding of how Scrum worked for so many teams.</p><p>Next on the list was to learn more about Kanban. I got my KMP certification and started diving into everything I could find; reading books, following all the Kanban disciples on Twitter, and widening my knowledge about Lean, Scrum, Kanban, and the difference between them all. After a few more releases doing Scrum, we were at a point where we were ready to bring on two new developers to our team. I decided that this transition was as a good a time as any to try Kanban on for size and see what we could learn from it. I spent the next two days building a physical board and mapping out a kanban system that I thought we could implement pretty easily. I am very lucky to have had the support of a leadership team that trusted me in making this decision, but I also wanted to be sure that they understood the “why” behind it. After all, when you have stakeholders who are really only familiar with engineering practices and metrics that are based in Scrum, it can be daunting (at first) to explain why you are choosing to “let go” of processes that feel like they are keeping everything on track and holding everyone accountable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PDkP3GYbqhwVbNX4pkD0pw.jpeg" /><figcaption>WIP it.</figcaption></figure><p>But here’s the thing — In talking to people at my various trainings or just in my personal network, I found pretty quickly that the things that people <em>outside </em>of those processes had come to care about most; story points, velocity, and even sprints — were the very things that were driving developers mad and sometimes having a negative effect on morale. Being a teacher at heart, I wanted to communicate our little experiment in process change in a way that would hopefully increase understanding and trust for our team, but also for the very important stakeholders outside of the team who are supporting their work. So what you will be reading in the rest of this article is just that; an account of our journey, so to speak.</p><p><strong>And so it begins…</strong></p><p>Agile principles and values will <em>always</em> be at the heart of what our team does and how we work on developing software. The sprint-based Scrum process, however, wasn’t going to be a good long term fit. For a mature team like ours, I could tell that Scrum was going to end up feeling a bit too heavy and rigid of a process. Even though we only used it for a few months, it was already creating an uncomfortable amount of overhead in the form of time spent in meetings, task breakdown, and story grooming etc. It demanded a lot of time that we felt would be better spent writing code, and we could see the very real potential for this process to cause stress and burnout. We’re a very small team at a Lean start-up. Put simply, we need to be able to move fast, shift priorities when necessary, and operate in an Agile environment that is based on current or potential business needs and partnerships.</p><p>As we grew the team from two to four developers, I wanted to be able to design and implement a workflow system that would honor their various skill sets and overall strength and reliability as a team. We needed something that could be responsive to how our workload, as well as the various <em>types</em> of work we were doing, would likely change over time as the business grows. The name of the game with Kanban is <strong>continuous improvement</strong>, as opposed to taking a one size fits all approach in our process, which sounded <em>perfect</em> for a start-up like ours. <strong>Enter Kanban!</strong></p><p>Kanban is a <strong>Pull-based </strong>work system where stories are completed with a focus on improving the <strong><em>flow</em></strong> of work. Kanban software development focuses on continuous delivery and drives efficiency by making the work visible, limiting how much work can be done at once focusing on the flow of that work, and always being mindful of opportunities for improvement and reducing waste. It is lightweight, flexible, process-driven, and owned by the Engineering team. Allowing and encouraging our team to self-organize around the work that they are doing as opposed to having to stick to a more externally driven, prescriptive delivery process is empowering, and conveys respect in their ability to properly collaborate and prioritize the work that needs to get done.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-Zp_QVfwTzz_8nEe" /><figcaption><em>Twitter — @johncutlefish</em></figcaption></figure><p><strong>Bottom Line</strong> — A continuous delivery model means there’s no looming “deadline” but instead an ever-present pressure for velocity, flow and improvement. Having a continuous delivery system like Kanban supports the team in doing quality work so that we deliver excellent, high quality code that brings the best possible value to our business.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tnUqrgeoDho8e872" /><figcaption><em>Our original Kanban Implementation Presentation w/the team</em></figcaption></figure><p><strong>Why don’t we do story points/estimation for our work?</strong></p><p>This was a big one, and a question that we discussed at great length as a team. I loved hearing more from the developers perspective about the pros and cons of story points.</p><p>Scrum encourages productivity by imposing a time limit on a batch of work. A sprint is a bucket of available work hours that gets filled with issues based on time you think it will take to complete them. When it comes to estimating the time and effort needed to complete the work, most teams have some over-estimators and many under-estimators. The reality is that no matter how smart we are, or how long we’ve been doing this work, most of us are probably <em>bad</em> estimators, and that’s not meant to be insulting, it’s just human nature. This isn’t an exact science and it <em>never</em> will be. Time spent trying to debate and decide on the size of a feature or story feels like wasted time because chances are, you are going to be wrong, or something will come up that will throw your perfect estimation off anyhow. Most importantly, this flawed estimation can have a huge effect on morale and burnout because it will lead to unrealistic expectations over time, causing the team to miss their sprint commitments. Retrospectives then turn into meetings that highlight “<em>what the team did wrong</em>”, and this often comes back to bad estimation, priority changes, and/or lack of clear feature specifications. The Business will feel as though Engineering missed their targets, and Engineering will feel like the Business kept moving the ball, when in reality, the entire system isn’t setting anyone up for success or to truly trust one another.</p><p>As a result, a team could feel pushed to cut corners, rush work, or sit on a mountain of tech debt just to maintain velocity within those timeboxed sprints. So in the end, scope gets “rigged”, which creates (you guessed it!) more meetings. All this to match the artificial construct of a sprint, and gaming the process which will bring no value to the business other than a vanity metric that you can broadcast to people who won’t know any better or question what’s happening “under the hood” in your actual software development process.</p><p>So, with all of this in mind — While Scrum drives productivity by limiting thework time available in a sprint, Kanban drives productivity and velocity by limiting the number of active, concurrent, stories/issues that are on the board at any given time. The power of running a Kanban process comes from its focus on continually delivering fewer, high quality items faster through honoring those WIP limits.</p><p><strong>How do we replace the traditional Scrum ceremonies?</strong></p><p><strong>Standup</strong> — We still do daily standup because it gives our team transparency and helps to eliminate blockers. Also, coffee and high fives.</p><ul><li><strong>Kanban Bonus</strong> — We use a physical kanban board that lives in our Engineering office and keeps the work and the workflow visible to the team as well as any other stakeholders from the business. Items to the right of the board, those furthest along, get higher priority. This creates an important core value for the team;</li><li><em>Observe all workflow policies as you move work across the board.</em></li><li><em>Finish what we’re already working on, before you take on more work.</em></li><li><em>Minimal multi-tasking.</em></li><li><em>No context switching.</em></li><li><em>Swarm a story when necessary in order to pull work through in an expedited manner.</em></li><li><em>Always be mindful of opportunities for improvement and reducing bottlenecks and waste in the system.</em></li><li><strong>Bottom Line</strong> — The things that are of highest value to the business are the things that get done, and done well.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8AByoeBGRjJ8RyyeOtcveA.jpeg" /><figcaption>The Board — But don’t forget…Kanban is SO much more than a board! Even Jeff Goldblum agrees.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*ggLw_v9KGK-lKtioaLD9LQ.jpeg" /><figcaption>Developing Workflow Policies with the team</figcaption></figure><p><strong>Story Grooming and Task Breakdown</strong> — We write stories and do task breakdown on an as needed basis. Our team is great at writing “right sized” stories “just in time” for the board that are relative to the skills of the team, and the scope of the work that needs to get done at that point in time. This “just in time” process of writing stories can feel a bit like a freefall for anyone who is used to proudly creating and grooming several months worth of stories and popping them into the backlog. I get it, because having what feels like solid plan in place certainly seems to make sense in so many ways. So I ask you to consider this — doing all that hard work before you can even pull it in and get started on it is most likely a waste of time and effort because shifting priorities and the need to pivot are not just a faint possibility in this world, they are a <em>reality. So, </em>if we are applying truly Agile practices, shouldn’t we be ready to not only accept but <em>embrace</em> the fact that changes will happen and adjust our tools and processes so that we can be ready to tackle those changes as enthusiastically as possible? I’m going with yes.</p><p>In addition to changing the timing of our story writing, we have also improved upon how we write stories by breaking everything down to <strong>minimum viable features</strong>. Breaking work into minimum viable features gives our engineers a sense of progressing continually and successfully. These small-step iterations help us improve as we learn more about what we are building and how people will be using it. Changing the timing, the way we write stories, and how we prioritize our work in this way ensures that we can stay light on our feet and aligned with business needs and direction at all times.</p><p><strong>Retrospectives</strong> — We still do regular retrospectives on larger releases, and we discuss how the development process should be modified to improve velocity and quality, while reducing overhead. Instead of looking <em>back</em> and critiquing what we did, all the energy is forward-looking and focused on process improvement. Ad-hoc retrospectives happen from time to time as well when issues are identified.</p><p><strong>Product Demo / Production Releases — </strong>At the end of daily stand-up, we always ask the questions “Do we have anything ready to demo?” and “Is anything ready to go to production?”, thus creating continuous awareness of the highest value work items to the business, those that are actually <em>done</em>.</p><p><strong>What metrics do we track and why?</strong></p><p>Metrics are just one part of understanding and building a team culture. They provide <em>quantitative</em> insight into the team’s performance, provide measurable goals for the team, and hold everyone accountable. Metrics and KPI’s are important and there is definitely a place for them as an aid to making smart business decisions, but we can’t allow them to be the only thing we pay attention to. We’ve all heard that “<em>you can’t manage what you don’t measure</em>”, but I am also a firm believer that “<em>not everything that counts can be counted</em>”.</p><p>Listening to the team’s feedback during retrospectives and in daily stand up is equally important in growing trust across the team, maintaining quality in the product, and improving flow and speed of development throughout the release process. We want to use <strong>both</strong> the <em>quantitative</em> and <em>qualitative</em> feedback to drive change.</p><ul><li><strong>Cycle Time</strong> — Cycle time is measured as the average number of days it takes a work item to move across the board from started (<em>Develop</em>) to finished (<em>Done</em>).</li><li><strong>Lead Time — </strong>This measures the average number of days that it takes a story to move across the board from the ready to be worked (<em>Dev Ready</em>) column to the finished (<em>Done</em>) column.</li><li><strong>Reaction Time </strong>— The average amount of time an items stays in (<em>Dev Ready</em>) before it gets picked up to start work and move through our flow. A rolling stone gathers no moss…you get the picture :)</li><li><strong>Throughput — </strong>This is the total number of work items that are completed in any given time period, which for us is typically two weeks, but we can also look at daily Throughput.</li></ul><p><strong>Cumulative Flow Diagram (CFD) Chart — </strong>The<strong> </strong>Cumulative Flow Diagram shows the total items that are in progress, as well as the time it takes to complete them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4Y6fGe6xjj5TkYwK" /><figcaption>Intial Metrics Snapshot — Screenful Rocks My World</figcaption></figure><p><strong>Have we found a downside?….Kind of.</strong></p><p>Let’s just say it — At first glance, there seems to be a loss of an organized focus on urgency, but is that true?</p><p>Here’s what I think — It’s true that having clarity of vision creates focus for a team, any team, running <strong>any</strong> process whether it’s Scrum, Kanban, Scrumban, Waterfall, or their own unique ad hoc process. <em>You do you!</em></p><p>In Scrum, that clarity and urgency exists in the form of timeboxed sprints. Everyone feels the pressure to get their work done before the sprint ends, and urgency is baked in, with everyone feeling the heat of the sprint burndown, and listening to the tick of the clock. I know that with some teams, this truly does work best and that’s great! It’s just important to understand your team, the scope of work, and implement a system that will support them in doing their best work. That’s it.</p><p>In Kanban, urgency is more abstract and doesn’t apply pressure in the same way as Scrum. Our clarity and vision starts at the story/task/issue level, so our priorities and focus as a team are much more distinct. We realize that a sense of urgency needs to be felt in our team through culture and management, and on an individual as well as a team basis. The outcome is that the team <em>owns</em> that sense of urgency and are able to think critically about what work is getting done and why. Instead of being nagged, or forcing them to stick to commitments, they are elevated to be a truly self managing team of adult professionals, not cogs in a software development machine.</p><p>This can be harder to see and feel from the business side of things, but for this particular team, it has been healthier. Why? Because the team has more ownership over the work and the process we use to get it done every day, which is a much more potent driver for <em>sustainable change</em>, and I beleive that the impact of that will be significantly better for the team and the business going forward.</p><p>The bottom line is that <strong>people support what they help to create</strong>, and using Kanban is helping us foster a team environment that values accountability, confidence, and trust in our process and in our people. So far so good, and we are excited to keep going with the flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/260/0*N3YNssorkRCCh_WG" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b10761de6d6c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>