<?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 Derek Huether on Medium]]></title>
        <description><![CDATA[Stories by Derek Huether on Medium]]></description>
        <link>https://medium.com/@derekhuether?source=rss-213c67fe5e93------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*zzCSxpTkDuJcyIrWh-SqVQ.jpeg</url>
            <title>Stories by Derek Huether on Medium</title>
            <link>https://medium.com/@derekhuether?source=rss-213c67fe5e93------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 04:38:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@derekhuether/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[Stop asking and start saying]]></title>
            <link>https://medium.com/@derekhuether/stop-asking-and-start-saying-bae0f2f1740e?source=rss-213c67fe5e93------2</link>
            <guid isPermaLink="false">https://medium.com/p/bae0f2f1740e</guid>
            <category><![CDATA[zoom]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[tips]]></category>
            <category><![CDATA[meetings]]></category>
            <dc:creator><![CDATA[Derek Huether]]></dc:creator>
            <pubDate>Mon, 18 May 2020 12:33:08 GMT</pubDate>
            <atom:updated>2020-05-18T12:33:08.245Z</atom:updated>
            <content:encoded><![CDATA[<p>I came from a meeting this week where the developers demo’d what they had finished in the last 2 weeks. Due to the pandemic, the meeting was held via <a href="https://zoom.us/">Zoom</a>. Every developer (with the exception of one) would ask if people could see their screen. We would then wait 5–10 seconds in silence, as people would either give a thumbs up or do nothing.</p><figure><img alt="A quote from Derek Huether. Don’t ask “can you see my screen?” Instead, say “let me know if you can’t see my screen”." src="https://cdn-images-1.medium.com/max/1024/1*MYg1-GN6Y6ntRKnS_2AmHg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bae0f2f1740e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Working in Quarantine Week 3]]></title>
            <link>https://medium.com/@derekhuether/working-in-quarantine-week-3-9e4672f85226?source=rss-213c67fe5e93------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e4672f85226</guid>
            <category><![CDATA[quarantine]]></category>
            <category><![CDATA[youtube]]></category>
            <category><![CDATA[covid19]]></category>
            <category><![CDATA[wfh]]></category>
            <dc:creator><![CDATA[Derek Huether]]></dc:creator>
            <pubDate>Sat, 18 Apr 2020 00:00:00 GMT</pubDate>
            <atom:updated>2020-04-18T19:25:28.821Z</atom:updated>
            <content:encoded><![CDATA[<p>What’s it like, now that we’re on our third week of quarantine? Has it been awesome, allowing us more time than we could have ever hoped for with spouse and family? Was it pretty awesome at the beginning but now it’s getting kind of old? Or, are we looking for an exit!? Dave Prior and I offer tips on how to not totally lose your $h!t while we all continue working from home.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LejOmwWVFTi16b_M" /><figcaption>Derek Huether and Dave Prior discuss what week 3 of the quarantine was like</figcaption></figure><p>Enjoy the first 30 seconds, where I test out my new adjustable standing desk.</p><p><em>Originally published at </em><a href="https://www.derekhuether.com/blog/2020/4/18/working-in-quarantine-week-3"><em>https://www.derekhuether.com</em></a><em> on April 18, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e4672f85226" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cost versus Value of Certifications]]></title>
            <link>https://medium.com/@derekhuether/cost-versus-value-of-certifications-ffedd9279330?source=rss-213c67fe5e93------2</link>
            <guid isPermaLink="false">https://medium.com/p/ffedd9279330</guid>
            <category><![CDATA[work]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[certification]]></category>
            <dc:creator><![CDATA[Derek Huether]]></dc:creator>
            <pubDate>Tue, 31 Mar 2020 00:00:00 GMT</pubDate>
            <atom:updated>2020-04-11T14:09:19.689Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Photo by Fabian Blank on Unsplash" src="https://cdn-images-1.medium.com/max/1024/0*wUQixx4oI_XyXc-a" /></figure><p>Earlier in my career, I didn’t have years of experience or a strong network of working relationships. When looking for work, I played the game just like everyone else; Write a really good resume and load it up with acronyms or words that a recruiter can do a keyword search on.</p><p>Many recruiters don’t have the luxury of knowing if you are really qualified or not. They get told there is a vacancy. Their job is to help fill that vacancy as quickly as possible. Unfortunately, when needing to comb though 100 resumes to find one qualified candidate, they need a method to separate the wheat from the chaff. Queue the value of the certification!</p><p>A friend once told me,</p><blockquote><strong>Cost is only an issue, in the absence of value.</strong></blockquote><p>Value is such a subjective thing. People pay what they perceive something is worth, not what it’s actually worth. I believe the effort of getting a certification can artificially inflate perceived value for years.</p><p>Let’s use the PMI Project Management Professional (PMP) certification as our working example.</p><p>In order to pre-qualify to take the PMP certification exam, I had to have several years of experience. I then had to pass an audit and was required to provide proof of experience by obtaining signatures from former colleagues and bosses. I then took the exam and passed. The exam was awful, as it really didn’t test knowledge of being a good project manager. Instead, it was several hours of trick questions. But upon passing, I felt like I had really accomplished something. I leveraged the certification to get an interview, got the job, and then was an active member of the PMI community for several years. At the very beginning, it had actual value to me. I got the return on the investment with the first job. But after getting that first job, I never leveraged the certification or the learning outcomes again. I maintained the certification because it was such a pain in the ass to get and there was such a perceived <a href="https://www.investopedia.com/terms/s/sunkcost.asp">sunk cost</a> of getting it.</p><p>I’ve helped create certifications since then. I was a track founder for <strong><em>Agile at Scale</em></strong>, for the International Consortium of Agile. I was a content contributor for <strong><em>Agile Certified Practitioner</em></strong><em>, </em>for PMI. I even went so far as contributing to the Software Extension of the Project Management Body of Knowledge.</p><p>But regardless of contribution, certifying organizations still want their money. They do not care who you are or the contributions you make. So, over time, I have let all of my certifications expire, as my thinking has evolved way past the basics the certifications present. As an investment, there are sunk costs (that are excluded from future business decisions because the cost will remain the same regardless of the outcome of a decision) and there are relevant costs (which are future costs that have yet to be incurred). Looking at certifications as investments and not getting emotionally attached makes decision making easier.</p><p>But back in February, I was informed by <a href="https://www.linkedin.com/company/project-management-institute/"><strong>Project Management Institute</strong></a> (PMI) that my Project Management Professional (PMP) certification, which I earned back in 2006, had been suspended for not paying the renewal fee. It was an honest mistake on my part but I actually stopped being a paid member of PMI several years ago, as I found myself not getting any value out of the membership. I continued to maintain the certification, until February.</p><p>To get an idea what other think, I launched a <a href="https://twitter.com/derekhuether/status/1226495729381859329">Twitter poll</a>, where over 83% of the respondents thought,</p><blockquote><strong>After years of experience, there is no value in maintaining certifications.</strong></blockquote><p>But what are your thoughts? Do you think the Twitter poll is on point or just the voice of a select few? Do <strong><em>you</em></strong> think there is value in maintaining certifications?</p><p><em>Originally published at </em><a href="https://www.derekhuether.com/blog/2020/3/31/cost-and-value-of-certifications"><em>https://www.derekhuether.com</em></a><em> on March 31, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ffedd9279330" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Value of Having a Stable Team]]></title>
            <link>https://medium.com/@derekhuether/stable-teams-should-be-non-negotiable-59af0972f77?source=rss-213c67fe5e93------2</link>
            <guid isPermaLink="false">https://medium.com/p/59af0972f77</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[quality]]></category>
            <category><![CDATA[people-management]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[predictability]]></category>
            <dc:creator><![CDATA[Derek Huether]]></dc:creator>
            <pubDate>Sun, 20 Jan 2019 22:06:41 GMT</pubDate>
            <atom:updated>2019-01-20T22:06:41.262Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iob9iRY4VXuCyjN6Tn6Z1Q.png" /><figcaption>How can delivery vary so much in time and quality?</figcaption></figure><p>A few years ago, we had a house built in rural Maryland. Working through a builder, we designed the layout of our home and painlessly moved into our newly constructed home about 6 months later. After we took full ownership of the house, there were minimal construction issues (a few nail pops). Fast-forward a year. A family went through the same builder and purchased land next to ours. It took about 9 months for the builder to complete the house and for them to move it. After they moved into their house, they had major construction issues (plumbing, electrical, HVAC). We were surprised and delighted by the builder and our overall experience. Our new neighbors were not. Considering our houses had the same builder, we wanted to understand why their house took an additional 3 months to complete and had so many quality issues. After comparing notes, we had our answer.</p><p>The root cause? The builder foreman left the company after our house was completed and there was nearly a 100% turnover of the main construction team and the sub-contractors (electricians, plumbers, HVAC, cabinet makers…). All of the optimizations the team had accumulated from building homes together were gone. Instead of taking the usual 6 months to build the house, they had to train new people (which slowed the original team members down) and mistakes were made along the way (requiring rework).</p><h3>STABLE TEAM DEFINED</h3><p>A stable team is a team that stays together (no adds or drops) over a period of time, ideally for at least 3 months. The construction team for our neighbors’ house had drops and adds throughout the 9-month construction, most importantly the building foreman. We had none.</p><p>Stable Teams have a few characteristics:</p><ol><li>Individuals on the team only belong to one team.</li><li>The team has one backlog or queue of work.</li><li>The team has limited dependencies on other teams.</li><li>The team stays together (unchanged) for at least 3 months.</li></ol><h3>CONTEXT</h3><p>Stable teams can be applied to any organization and at any level, from delivery teams to program teams, to portfolio teams. If they meet the 4 criteria listed above, they are a stable team.</p><h3>RESULTS</h3><p>Plenty of surveys and studies have been done noting how stable teams are “better” than non-stable teams.</p><p>Particularly, I’m going to reference a 2014 research study by <a href="https://www.linkedin.com/in/larrymaccherone/">Larry Maccherone</a>. With over 50,000 respondents, let’s note a few key points that it concluded:</p><ol><li>Teams that stay together are more productive.</li><li>Teams that stay together are more predictable.</li><li>Teams that stay together are more responsive.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZaNY2DrFVukmlmhuhB4roA.png" /><figcaption>Results from Maccherone research</figcaption></figure><p>If we modify teams regularly or staff teams with people who are merely temporary members, we will never allow ourselves the opportunity of high performance. If we consider <a href="https://en.wikipedia.org/wiki/Tuckman&#39;s_stages_of_group_development">Tuckman’s stages of group development</a> (forming, storming, norming, and performing), we will continuously be forming and storming. We’ll never have the opportunity to norm and perform at the same level as a stable team.</p><h3>STABLE TEAMS SHOULD BE NON-NEGOTIABLE</h3><p>Having unstable teams hurts productivity, which makes sense. If we shift people around (think re-orgs), we have to train the new team members in the norms of the existing teams. While we are ramping up new teams or team members, we’re also not getting work done. The changes, though well-intended, will have negative impacts in the short-term.</p><p>When trying to improve an organization, some start with a practices-first approach, installing Scrum, SAFe, Kanban, or some other framework. But whatever your framework, stable teams should be non-negotiable, if you want a predictable system. Have a backlog of work, build and maintain a team, and then deliver value. As noted in the Maccherone research, stable teams resulted in throughput improvements (as much as 60%), increased predictability (variability of throughput effect improved as much as 40%) and quicker responsiveness (time in process improved as much as 60%).</p><p>Good organizational design should include stable teams. Leadership should be incentivized to keep teams together and incrementally improve them. Remember, if you make too many organizational changes too often, it will be at the expense of customers and the business.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59af0972f77" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Productivity Patterns]]></title>
            <link>https://medium.com/@derekhuether/productivity-patterns-fa2e4898ad66?source=rss-213c67fe5e93------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa2e4898ad66</guid>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Derek Huether]]></dc:creator>
            <pubDate>Wed, 14 Dec 2016 14:18:28 GMT</pubDate>
            <atom:updated>2016-12-14T14:18:28.800Z</atom:updated>
            <content:encoded><![CDATA[<h3>My Past Experience</h3><p>Be it get-rich-quick schemes or rapid-weight-loss solutions, the Internet is littered with a million improvement schemes. In my many years of attempting to improve productivity for my clients and myself, I’ve tried just about everything. Regardless if the post, podcast, or book is promising to do twice the work in half the time or that you can cram an entire work week into 4 hours, there is something out there for everyone. My first venture into this productivity-focused world was way back in the early 90s, when I watched this horrible movie titled <em>Taking Care of Business</em>, starring Jim Belushi and Charles Grodin. In the movie, an uptight advertising exec has his entire life in a filofax organizer which mistakenly ends up in the hands of a friendly convict who poses as him. The movie is still horrible but the organizer idea seemed to work for me.</p><h3>Franklin Covey Planner</h3><p>From this movie, I discovered the Franklin Covey Planner. Yep, my world was filled with A1, B1, C1’s. Alas, I couldn’t make it work. Much like the guy in the movie, everything was in a little leather book with special pages (that were not cheap). Unfortunately, if I didn’t have the book in my field of view to constantly remind myself, things didn’t get done. I think I lasted a year, until I discovered the cost of refilling the book with new pages.</p><h3>GTD</h3><p>I then discovered GTD (Getting Things Done) by David Allen. This was 15–20 years ago. Again, it worked for a little while but I then found myself doing too much <em>organizing</em> and too little <em>doing</em>. Things were going away from paper filing and everything in that system was all about paper filing. Maybe I was doing it wrong. It just wasn’t clear to me. I didn’t see any real progress or productivity improvement so I just stopped doing it.</p><h3>Personal Kanban + Pomodoro Technique</h3><p>In mid 2009, in a moment of Internet serendipity, I ventured into the world of <a href="http://www.derekhuether.com/2009/08/18/my-personal-kanban-story/">Personal Kanban</a>. I think I searched “<a href="http://www.agilezen.com/">Zen</a>” and up popped a website for a Kanban tool. I started using it and loved it. Alas, that company got purchased by Rally Software and now they are no longer taking registrations. But, this has become the first system I have been able to stick with. Just to try other tools, I soon switched over to <a href="https://leankit.com/">LeanKit</a> Kanban. I’ve been using it ever since. I like that it doesn’t make any promises it can’t keep. “Visualize your work, optimize your process and deliver faster”. Around the same time in 2009, I also began using the <a href="http://www.derekhuether.com/2010/12/08/pomodora-relationship/">Pomodoro Technique</a> to optimize my productivity.</p><h3>Productivity Rosetta Stone</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Km0Od_ZQbqois8bQdeelTQ.png" /></figure><p>So, why do some methods work and some do not? Why did I abandon the Planner and GTD systems so long ago but still use Personal Kanban and the Pomodoro Technique? Well, I started by listing common traits on a whiteboard and saw relationships and discovered some patterns. Not only are there three things I believe every productivity system needs to work, I also see three things that are necessary to prevent you from abandoning that system.</p><p>I describe it as a <em>Productivity Rosetta Stone</em>. For those unfamiliar, the <strong>Rosetta Stone</strong> is a rock slab, found in 1799. It was inscribed with a decree that appears in three scripts: Ancient Egyptian hieroglyphs, Demotic script, and Ancient Greek. The stone presents essentially the same text in all three scripts and provided the key to the modern understanding of Egyptian hieroglyphs. I’ve applied my productivity Rosetta Stone to Scrum, Kanban, Pomodoro Technique, Lean Startup, and even organizational transformation frameworks. All of them check out and it provided me with a key to better understand productivity patterns.</p><h3>3 Things to Increase Productivity</h3><p>1. <strong>A system</strong> is a set of principles or procedures to get something done or accomplished; Anyone can follow a system.</p><p>2. <strong>A ritual</strong> is a series of actions or type of behavior regularly and invariably followed by someone. It’s different from a system. A system might only be followed once, but by many people. A ritual is something someone or some group does again and again, in the hope of arriving at the same or improved outcome.</p><p>3. <strong>A habit</strong> is a regular tendency or practice, especially one that is hard to give up. If you want to be productive, you have to be habitual with your rituals, as part of your system.</p><p>How does it all fit together? Name a system. Next, list your process steps, sequence, and any rules around them. Last, do the steps again and again until it becomes a habit.</p><h3>Lack of These Kills Productivity</h3><p><strong>Clarity, Progress, or Commitment</strong></p><p><strong>1. Clarity</strong> is the quality of being certain or definite. You need clarity in order to know what you need to do. <strong>Lack of clarity</strong> creates confusion and waste. Each step of a system should be actionable and repeatable. In order to ensure certainty around your steps, write them down; maybe draw a picture or diagram. If your outcomes are not repeatable, you have an experiment but not a system.</p><p><strong>2. Progress</strong> is forward or onward movement toward a destination or goal. Your goal is productivity. If you <strong>lack progress</strong>, you lose momentum. If you lose momentum, you will lose commitment to the system.</p><p><strong>3. Lack of commitment</strong> to the system results in you no longer using the system. You move on to something new to get the productivity results you seek.</p><p>In the event your system lacks clarity, progress, or commitment, performance will go down or you’ll stop using it all together. I stopped using the planner and GTD becuase I just didn’t see the progress they were promising. I no longer followed the rituals. I know longer had habits. Like a domino falling, once I failed to see progress, I lost commitment in the system.</p><h3>Summary</h3><p>Though I have only provided a conceptual model, try applying it to your personal system. Like in any productivity strategy, once your defined system becomes habitual, you can start to focus on improvements. Maybe you want to do more in less time. Maybe you want to do the same with higher quality. You be the judge. It’s your system. Remember, you’ll still need clarity, progress, and commitment or your productivity will be short lived.</p><p>Listen to Dave Prior and me in an episode of LeadingAgile Sound Notes, as we talk about the <a href="https://www.leadingagile.com/podcast/productivity-triangle-derek-huether/">Productivity Triangle</a>.</p><p>If you want an editable copy of the triangle, <a href="http://www.derekhuether.com/wp-content/uploads/2016/12/productivity-triangle.docx">download it here</a>:</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa2e4898ad66" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Things You Need to Increase Productivity]]></title>
            <link>https://medium.com/@derekhuether/3-things-you-need-to-increase-productivity-57a4deec3e0c?source=rss-213c67fe5e93------2</link>
            <guid isPermaLink="false">https://medium.com/p/57a4deec3e0c</guid>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[pomodoro-technique]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Derek Huether]]></dc:creator>
            <pubDate>Wed, 28 Sep 2016 09:54:54 GMT</pubDate>
            <atom:updated>2016-10-03T12:27:21.742Z</atom:updated>
            <content:encoded><![CDATA[<h3>What I Believe</h3><p>If you want to increase productivity, I believe you need <strong>3 key things</strong>. In a previous post, <a href="http://www.derekhuether.com/2016/08/31/discipline-over-motivation/">I wrote you needed ritual and motivation</a>. After some reflection, I decided to update that. First, create a system to ensure you are always getting stuff done, regardless if you’re motivated (though it helps). Second, create rituals to follow within the system. Last, repeat those rituals until they become habits.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IzEpvYT5iLMaX_DIeWIFFg.png" /><figcaption>Productivity Pyramid</figcaption></figure><h3>System</h3><p><strong>My system of choice, for my own work, is Kanban. </strong>It’s a method I use to manage everything I do. In short, Kanban is a visualization of value flowing through a system. I use sticky notes on a wall as signals of outcomes I’m working toward. I have columns on the wall; To Do, Work In Process (WIP), and Done. I also have the WIP column split into two rows. One row is for active work in process. The second row is for outcomes or work that is blocked. I believe one of the keys to a successful system is having clarity around its design but also to have low overhead (effort to maintain the system). It doesn’t matter if I use a physical wall or a virtual one, the importance is either are in my field of view. When on the road, I use a virtual Kanban. When at home, I prefer a physical one.</p><p><strong>My supporting system is a Pomodoro.</strong> A Pomodoro is simply a kitchen timer. Like it or not, I respond really well to deadlines. One of my favorite quotes is:</p><blockquote>A goal without a deadline is merely a dream.</blockquote><p>Give me a goal with a deadline and I may not get it all done, but I’ll make progress and get you something. If I have a goal without a deadline, I can think something to death. Like with my Kanban, I prefer to go with physical but I’m happy to use a virtual one as well. The important thing is the timebox. It’s like personal sprints. (yep, like Scrum). Make a commitment; get it done.</p><h3>Ritual</h3><ul><li>Every morning, I review my (virtual) LeanKit board</li><li>I then review my physical Kanban board next</li></ul><p><em>I review my Kanban board in a very specific order: Done, Work in Process, Blocked, To Do. [1] I do this to remind myself what I recently got done. [2] It allows me to verify if I finished something the day before but forgot to pull it to done. [3] It gives me a chance to pull something off the to-do column and put it back in my backlog, allowing space for something of higher value.</em></p><ul><li>I pull a card from To Do to WIP</li><li>When I’m ready, I set the Pomodoro timer for 25 minutes and begin work</li><li>When the timer goes off, I take a 5 minute break</li><li>Reset the timer for another 25 minutes, review what my next highest priority is, and begin</li><li>If I’m coming back from an extended break like lunch or dinner with the family, I still reset to 25 minutes</li><li>I continue this process until I finished work for the day</li></ul><h3>Habit</h3><p>It’s true if you get something done, regardless of the size and complexity, it makes you <a href="https://www.psychologytoday.com/blog/brain-wise/201209/why-were-all-addicted-texts-twitter-and-google">feel good (thanks to dopamine)</a>. If something makes you feel good, it physically reinforces your behaviour to do it again. You need a few quick wins (getting things to Done), to start releasing dopamine and establish the ritual for the longer term. If you don’t get outcomes, you’re not going to keep doing something. If you can create the habit of getting several smaller things done per day, you are on your way. Habits are not for optimum productivity. Rather, they are there to ensure minimum productivity. I recommend breaking work into small enough chunks that you can get <em>something</em> done every hour.</p><h3>Summary</h3><p>By doing these three things, you’ll achieve increased productivity. If you can get inspired and motivated, your increase will be even higher. Alas, inspiration and motivation are a different topic. Until then, capitalize on the system, rituals and habits, until the next time you get inspired.</p><p>If you are looking for a system to work beyond personal productivity, the same rules apply. Visualize your group or organization’s continuous flow of value on a wall or board (physical or virtual Kanban). Define timeboxes, like in Scrum, for teams to focus on work. Take a short break at the end of each timebox. Keep reflecting on the things you’ve accomplished. Get that dopamine flowing!</p><p><em>Originally published at </em><a href="http://www.derekhuether.com/2016/09/28/3-things-need-increase-productivity/"><em>www.derekhuether.com</em></a><em> on September 28, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57a4deec3e0c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is ‘Work In Progress — WIP’]]></title>
            <link>https://medium.com/@derekhuether/what-is-work-in-progress-wip-5a2be611cee7?source=rss-213c67fe5e93------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a2be611cee7</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[process]]></category>
            <category><![CDATA[kanban]]></category>
            <dc:creator><![CDATA[Derek Huether]]></dc:creator>
            <pubDate>Sat, 04 Jun 2016 13:12:33 GMT</pubDate>
            <atom:updated>2016-06-04T13:12:33.139Z</atom:updated>
            <content:encoded><![CDATA[<p>Work in <em>process</em>, also known as WIP<em>,</em> refers to activities that have entered the completion process but are not yet outcomes. <a href="http://www.investopedia.com/video/play/work-progress-wip/">Work in <em>progress</em> (WIP)</a> refers to all materials and partly finished products that are at various stages of the production process. WIP excludes inventory of time or materials at the start of the completion cycle and finished products inventory at the end of the production cycle. That means you don’t count the things you have not started or have not finished.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iFp3VvGKeJZ_9chr.jpg" /></figure><h3>Work in Process vs Progress</h3><p>I see the difference between <em>process</em> and <em>progress</em> as being very small but I want to make a distinction. I see <strong>progress</strong> being anchored to physical goods at different stages of completeness on an assembly line and <strong>process</strong> being completion of any activity as part of a goal or outcome. Your process could be as simple as To-do and Done. If you are multi-tasking and have 5 things started all at the same time, you have a WIP of 5.</p><h3>Personal Agility Tip</h3><p>One of the secrets of managing your work in process is to only start work on things you actually have capacity to work on. When you have capacity, you can pull work into your “queue”. Rather than accepting and starting every task that comes your way, limit the amount of stuff that you’re working on at any given time. Focus less on starting things in your queue and more on finishing them, and I can pretty much guarantee you’ll get more done.</p><p>Personally, I know that I can only deal with three activities at a time before things start to get dropped. Know your personal limits and set them accordingly. If you’re working on something and you get blocked, don’t just pull in more work. Add a visual indicator that shows the item is blocked and continue pulling working to done. Once you unblock work, you can pull it the rest of the way through your system to done.</p><p>Have questions? <a href="http://7dayagile.com/contact/">Ask</a> me how I do it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a2be611cee7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Principles of Personal Agility]]></title>
            <link>https://medium.com/@derekhuether/principles-of-personal-agility-8a0ad2c62a1d?source=rss-213c67fe5e93------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a0ad2c62a1d</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Derek Huether]]></dc:creator>
            <pubDate>Fri, 13 May 2016 01:37:39 GMT</pubDate>
            <atom:updated>2016-05-13T01:43:36.140Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently, I’ve been doing a lot of reflecting on how to increase personal agility. No, I’m not talking about doing somersaults or some crazy yoga poses. I’m speaking of the ability to focus on the delivery of value and be adaptable in what I do every day. When the <a href="http://agilemanifesto.org/principles.html">Agile Manifesto</a> was written back in 2001, there were representatives from Extreme Programming, Scrum, DSDM, Adaptive Software Development, Crystal, Feature-Driven Development, Pragmatic Programming, and others present. They focused on values and principles that would improve how we do software development. But, can we apply the same practices to our personal lives? I’ve been looking to answer that question since 2010, when I started to write about <a href="http://www.derekhuether.com/2010/09/07/my-personal-kanban-2-0/">Personal Kanban</a>. For me, Kanban doesn’t get the love it deserves, as a tool to help manage personal activities and outcomes. When people talk about agility, they usually think Scrum. I realize Scrum is being leveraged outside of software development. I have even been approached to comment on “Agile” Marketing by using Scrum. It got me thinking… Why do people think Scrum will solve all problems? When it comes to organizational agility and specifically personal agility, I don’t think it does.</p><h4>Scrum for One?</h4><p>For the sake of this post, I want to keep focus on people and not big organizations. Having been an Agile coach and consultant, I have learned a lot of strategies that have helped me manage customers and accounts. While working with large complex organizations, I have seen productivity improvements on organizational levels by leveraging Lean and Kanban and on a team level by leveraging Scrum and Kanban. But what about all of the individuals who work for those organizations or on those Scrum teams? What about people who have no idea what Scrum is and don’t care? How can they better their productivity outside the software world?</p><p>In the Lifehack article “<a href="http://www.lifehack.org/articles/featured/scrum-for-one.html">Scrum for One</a>,” Dustin Wax described how many of the elements of Scrum could be adapted for individual productivity. When reading the article, I wasn’t sold on the idea. Scrum is an awesome framework for teams but I see it like jamming a round peg in square hole, if you want to use Scrum for your day-to-day productivity.</p><p>In Scrum, you demonstrate value to your customer or customer representative every 2–4 weeks, as part of a sprint (timebox). Does that make sense for managing your personal work on a continuous basis? No.</p><p>In Scrum, you have a 3 roles: ScrumMaster, Product Owner, and Team. Unless you have a split personality, it’s just you!</p><p>If the metaphor doesn’t align with reality, find a new metaphor versus trying to bend reality to reflect it.</p><p>Most of the things I think about when getting things done include: Aligning activities to outcomes, breaking work into managing chunks, iterating on what I’m doing or creating so it can be delivered or improved over time… With that, these are not elements exclusive to Scrum. So, why limit yourself to Scrum?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dHYB9rBT07-NqLBwHYPfpQ.png" /></figure><h4>Personal Agility Manifesto</h4><p>I believe personal productivity (or agility) could be rethought. Is personal productivity about being really busy or is it about getting things done? To be productive, it means you must produce. If not, you are just active. There is a difference! To help shape my thoughts, I wrote my own principles of a <a href="http://7dayagile.com/personal-agility-manifesto/">personal agility manifesto</a>. It’s a lot like the Agile Manifesto.</p><h4>Principles of Personal Agility</h4><p><strong>I follow these principles:</strong></p><blockquote>My highest priority is to satisfy myself and then others<br>through early and continuous delivery of valuable outcomes.</blockquote><blockquote>Welcome requests, even late in the day.<br>Agility harnesses change for my competitive advantage.</blockquote><blockquote>Deliver outcomes frequently, from a couple of hours to a couple of days, <br>with a preference to the shorter timescale.</blockquote><blockquote>Work together with others daily.</blockquote><blockquote>Outcomes are completed by me being motivated.<br>Get the environment and support I need, and get the job done.</blockquote><blockquote>The most efficient and effective method of conveying information<br>to and from others is face-to-face conversation.</blockquote><blockquote>Outcomes are the primary measure of progress.</blockquote><blockquote>Agile processes promote sustainable outcomes.<br>I need to maintain a constant pace indefinitely.</blockquote><blockquote>Continuous attention to technical excellence and craftsmanship enhances my agility.</blockquote><blockquote>Simplicity–the art of maximizing the amount of outcomes–is essential.</blockquote><blockquote>The best outcomes emerge from me being a self-organized individual.</blockquote><blockquote>At regular intervals, reflect on how I can become more effective,<br>then tune and adjust my behavior accordingly</blockquote><h4>Key differences from the Agile Manifesto?</h4><p>First, (any) outcomes are the primary measure of progress. This isn’t all about software development.</p><p>Second, I’m focused on minutes, hours, and days to get things done. Teams will continue to focus on days, weeks, and months to get work done and shipped.</p><h4>Conclusion</h4><p>I’m looking to dig into something anyone, within or without an Agile team, can use to improve personal productivity. When you hear <strong><em>Agile</em></strong> it’s actually a pretty niche group. But, when you talk personal productivity, the audience size explodes. Like with agile, I don’t think there is a single right way. So, I’m looking to experiment and continue to try and get better. So, if you are an individual, you can be <strong><em>agile for one</em></strong>. If you have any tips or tricks on how you get things done, I would love to hear them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a0ad2c62a1d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>