Advertising
Advertising

Scrum for One

Scrum for One

Scrum for One

    That’s a funny word, isn’t it? “Scrum.” Scrum is a project management strategy for software development teams. The name comes from rugby (I guess) where it refers to the start of a new play. In the programming world, it’s a technique of coordinating a team’s work without a clear plan, working towards attainable short-term goals, and then repeating the process towards another set of goals – which I suppose is kind of like playing towards a goal in rugby. Except, you know – fewer broken bones. Hopefully.

    Advertising

    I’m not part of a software development team. I’m not even a programmer. But when I came across an article on Scrum recently, it struck me that, while intended for big, collaborative projects, there were a lot of elements of Scrum that could be adapted pretty well to individual productivity. Although Scrum can be implemented at any stage of a project, it really excels as a way of dealing with projects that have stalled out for some reason – projects that have gotten stuck for lack of resources, lack of direction, even lack of teamwork – and that’s something that happens to all of us at one time or another. Maybe, just maybe, the principles that get teams of programmers back on track can apply to the projects every one of us has gotten stuck on.

    Scrum 101

    Although there are whole textbooks devoted to managing teams and their projects using Scrum, the basic principles are very simple:

    Advertising

    • Do what you can with what you have. Projects stall because some resource – whether it’s material, knowledge, or manpower – is missing. Usually, though, there are plenty of things that can be done even without those resources – other parts of the system to build, creative workarounds, standards to devise, and so on. During the planning of each stage, and in daily “check-in” meetings along the way, these shortfalls are taken into account and work designed around them so that a lack of resources doesn’t have to create a lack of progress.
    • Constant feedback. As I just mentioned, Scrum encourages daily contact between its team-members, so that a) nobody stalls and holds up the whole project, and b) the collective knowledge of the whole team can be brought to bear on new problems in creative ways. Meetings are short, as short as 15 minutes, and center around three questions:
      1. What have you accomplished so far?
      2. What will you accomplish today?
      3. What’s preventing you from making progress right now?

      These simple questions are meant to identify any “logjams” and break them up before they hold up the entire project.

    • Work towards clearly-defined short-term goals. Scrum projects are, generally-speaking, point-releases of the software under development – that is, they are significant but relatively simple evolutionary improvements of the state of the project at the beginning of the project. For example, a set of new functions could be implemented, an interface designed, a database structure mapped out, and so on. “Write browser” is too big of a project, it’s realization too far off, to make for a meaningful Scrum project; “correct bug in line 1178” too small. Ideally, as each project is completed, the software under development should be in a usable state – Scrum was developed to deal with the contingencies of the software world, where projects often need to be rushed into market to combat a competing project, or just to bring in an income.
    • Sprint. The basic working unit of Scrum is the Sprint – a focused dash towards the completion of the immediate project goals. At the beginning of the Sprint, the team determines exactly what resources are available to them, what they intend to achieve given those resources, and how long they’ll work on it. Then, they work on those objectives, and those objectives only. The Sprint is sacrosanct – its members work on the project they’ve put together and nothing else until the Sprint is completed. It might be a week, it might be 30 days, or anywhere in between – whatever time they’ve agreed on is dedicated solely to the Sprint. When it’s done, team members might rotate out of or into the team, or be assigned to other projects, but until then – they Sprint.

    Scrumming Solo

    Seems to me that, with a little modification, those are pretty good principles for anyone with some big projects on their plate – especially if you, like me, have a tendency to get side-railed. Of course, most of our projects aren’t collaborative, and they’re rarely as compartmentalized as computer programs, either. The idea of developing a project by evolutionary steps, with each step creating a potentially usable end-product, simply doesn’t apply to the kind of long-term projects most of us have as individuals – things like writing a book, learning a foreign language, or earning a promotion.

    Advertising

    But the idea of Scrum is, I think, very applicable to our personal lives. The whole point is, through a process of constant self-awareness, to identify what’s holding us back, how we can work around it, and where the next few days or weeks should take us. Consider, then, “Scrum for One”:

    • Do what you can with what you have. There are bound to be hang-ups in any project worth doing, and it’s all too easy to look at a project and despair because you don’t have whatever you need to finish it. Well, you may not have what you need to finish, but chances are you have what you need to start, to do at least some of the steps needed to get yourself somewhere close to the finish line. And you can take heart from this peculiarity of Scrum: often, when working under less than ideal circumstances without all the necessities to finish a project, Scrum teams find that either a new solution emerges that’s much more within their grasp or, just as often, that the missing element isn’t really needed in the first place. At the worst, you’ll give yourself the time you need to come up with the missing piece – and meanwhile you’ll be moving inexorably closer to your goal.
    • Constant self-reflection. If you’re a fan of Allen, Covey, or Drucker, you’ve probably already accepted the importance of a weekly review. Scrum for One suggests that more frequent reflection might be helpful – nothing at the scale of a full weekly review, but a few moments of honesty each morning to define the work in front of you and any problems that might be standing in the way. Brainstorm a few minutes to see if you can solve the issue, and if not, put it in your to-do list for later action. A lot of time, just asking “What’s standing in my way?”is enough to trigger a solution – more often than not, the problem lies more in ourselves than in our situation.
    • Work towards clearly-defined, short-term goals. Give yourself a time limit and set a reasonable goal – reasonable, but meaningful – to reach by the end of that period. Projects that stretch out in front of you for months or years are discouraging (which is why so few people write books) while projects that are too small often aren’t very satisfying to complete.
    • Sprint. Sprinting the way Scrum teams do it won’t really work for individuals – you probably have a lot of different roles to play on a day-to-day basis, which means focusing on a single project to the exclusion of everything else is going to be difficult, if its even possible. What you can do, though, is block out a number of hours every day and use them to focus strictly on one project – no distractions, no knocking off early, no nothing until you reach your goal.

    Obviously this isn’t anything like a complete productivity system, but it’s interesting nonetheless. Scrum is a very effective way of managing projects, and is used by software giants like Microsoft as well as tiny start-ups and everything in between. If nothing else, next time you’re stuck, ask yourself the simple question, “What’s standing in my way right now?” and see if that doesn’t lead to “OK, what am I going to do about it?”

    Advertising

    More by this author

    The Importance of Reminders (And How to Make a Reminder That Works) Is Procrastination Bad? The Truth About Procrastination Revealed Back to Basics: Your Calendar Learn Something New Every Day 10 Tips for More Effective PowerPoint Presentations

    Trending in Featured

    1The Importance of Reminders (And How to Make a Reminder That Works) 240 Top Productivity Apps for iPhone (2018 Updated) 3How to Overcome Procrastination and Start Doing What Matters 4Is Procrastination Bad? The Truth About Procrastination Revealed 5The Gentle Art of Saying No

    Read Next

    Advertising
    Advertising

    Last Updated on August 16, 2018

    The Importance of Reminders (And How to Make a Reminder That Works)

    The Importance of Reminders (And How to Make a Reminder That Works)

    No matter how well you set up your todo list and calendar, you aren’t going to get things done unless you have a reliable way of reminding yourself to actually do them.

    Anyone who’s spent an hour writing up the perfect grocery list only to realize at the store that they forgot to bring the list understands the importance of reminders.

    Reminders of some sort or another are what turn a collection of paper goods or web services into what David Allen calls a “trusted system”.

    A lot of people resist getting better organized. No matter what kind of chaotic mess, their lives are on a day-to-day basis because they know themselves well enough to know that there’s after all that work they’ll probably forget to take their lists with them when it matters most.

    Fortunately, there are ways to make sure we remember to check our lists — and to remember to do the things we need to do, whether they’re on a list or not.

    In most cases, we need a lot of pushing at first, for example by making a reminder, but eventually we build up enough momentum that doing what needs doing becomes a habit — not an exception.

    Advertising

    The power of habit

    A habit is any act we engage in automatically without thinking about it.

    For example, when you brush your teeth, you don’t have to think about every single step from start to finish; once you stagger up to the sink, habit takes over (and, really, habit got you to the sink in the first place) and you find yourself putting toothpaste on your toothbrush, putting the toothbrush in your mouth (and never your ear!), spitting, rinsing, and so on without any conscious effort at all.

    This is a good thing because if you’re anything like me, you’re not even capable of conscious thought when you’re brushing your teeth.

    The good news is you already have a whole set of productivity habits you’ve built up over the course of your life. The bad news is, a lot of them aren’t very good habits.

    That quick game Frogger to “loosen you up” before you get working, that always ends up being six hours of Frogger –– that’s a habit. And as you know, habits like that can be hard to break — which is one of the reasons why habits are so important in the first place.

    Once you’ve replaced an unproductive habit with a more productive one, the new habit will be just as hard to break as the old one was. Getting there, though, can be a chore!

    Advertising

    The old saw about anything you do for 21 days becoming a habit has been pretty much discredited, but there is a kernel of truth there — anything you do long enough becomes an ingrained behavior, a habit. Some people pick up habits quickly, others over a longer time span, but eventually, the behaviors become automatic.

    Building productive habits, then, is a matter of repeating a desired behavior over a long enough period of time that you start doing it without thinking.

    But how do you remember to do that? And what about the things that don’t need to be habits — the one-off events, like taking your paycheck stubs to your mortgage banker or making a particular phone call?

    The trick to reminding yourself often enough for something to become a habit, or just that one time that you need to do something, is to interrupt yourself in some way in a way that triggers the desired behavior.

    The wonderful thing about triggers (reminders)

    A trigger is anything that you put “in your way” to remind you to do something. The best triggers are related in some way to the behavior you want to produce.

    For instance, if you want to remember to take something to work that you wouldn’t normally take, you might place it in front of the door so you have to pick it up to get out of your house.

    Advertising

    But anything that catches your attention and reminds you to do something can be a trigger. An alarm clock or kitchen timer is a perfect example — when the bell rings, you know to wake up or take the quiche out of the oven. (Hopefully you remember which trigger goes with which behavior!)

    If you want to instill a habit, the thing to do is to place a trigger in your path to remind you to do whatever it is you’re trying to make into a habit — and keep it there until you realize that you’ve already done the thing it’s supposed to remind you of.

    For instance, a post-it saying “count your calories” placed on the refrigerator door (or maybe on your favorite sugary snack itself)  can help you remember that you’re supposed to be cutting back — until one day you realize that you don’t need to be reminded anymore.

    These triggers all require a lot of forethought, though — you have to remember that you need to remember something in the first place.

    For a lot of tasks, the best reminder is one that’s completely automated — you set it up and then forget about it, trusting the trigger to pop up when you need it.

    How to make a reminder works for you

    Computers and ubiquity of mobile Internet-connected devices make it possible to set up automatic triggers for just about anything.

    Advertising

    Desktop software like Outlook will pop up reminders on your desktop screen, and most online services go an extra step and send reminders via email or SMS text message — just the thing to keep you on track. Sandy, for example, just does automatic reminders.

    Automated reminders can help you build habits — but it can also help you remember things that are too important to be trusted even to habit. Diabetics who need to take their insulin, HIV patients whose medication must be taken at an exact time in a precise order, phone calls that have to be made exactly on time, and other crucial events require triggers even when the habit is already in place.

    My advice is to set reminders for just about everything — have them sent to your mobile phone in some way (either through a built-in calendar or an online service that sends updates) so you never have to think about it — and never have to worry about forgetting.

    Your weekly review is a good time to enter new reminders for the coming weeks or months. I simply don’t want to think about what I’m supposed to be doing; I want to be reminded so I can think just about actually doing it.

    I tend to use my calendar for reminders, mostly, though I do like Sandy quite a bit.

    Featured photo credit: Unsplash via unsplash.com

    Read Next