fXceed

http://www.lifehack.org/articles/productivity/scrum-for-one.html

This scheme is exactly what I need for developing my project. Step by step toward each small but important goal.

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.

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.

My schedule is not ideal for many people, but remember—I’m not married, not (currently) taking classes, and don’t have a day job. I maintain a midnight-7am schedule for blogging because that’s when I’m able to focus without being distracted—no matter what. I may be able to work undisturbed during the day every once in a while, but by choosing a time to work that is consistent has led to my building a habit around this time. My body now knows at midnight that it’s time to focus, crack down, and produce. Habits are a great “system” to have in place because they can help force efficiency and effectiveness in everything. Get in the habit of writing at least once a day, and start building good habits around your blogging “business” as soon as possible.

I just can’t help but agree, based on my own experience, observation on myself, I need to build the habit around the specific range of hours which enable me to focus and produce.

The ultimate goal of systematization is not necessarily automation—though when executed deliberately and correctly, automation can be a welcome hand in your business’ operation. By systemizing your blog, you are able to begin working “on” your blog, not “in” your blog—to borrow from a popular business expression. Sure, you need to provide great, original content, but understand that there’s more to blogging than what you type (unless, of course, the blog is for your eyes only!)

Since I hope to make this blog open to the viewers and earn enough money to support my autodidactic plans, I must develop professional skills to manage the blog to be a real business.