Individual Sprints – a WorkFlowy Productivity Hack

Have you ever heard the terms “agile development“, “scrum” and “sprints“? I had… but never really looked into any if it – because I’m not a software developer. And then I came across a post by Shivani Bhargava. She demystifies the sprint process and shows us how to set it up in WorkFlowy – even if you don’t have a software developer bone in your body. Here is what “Individual Sprints” can do for you:

  • Find the motivation to get the ball rolling on projects
  • Track how much you get done week by week
  • Help you understand your personal capacity of how much you can get done in a week – especially with an unstructured lifestyle (freelancers, contractors, writers, etc.)

I asked Shivani to do a quick screencast for us, outlining her Individual Sprint hack in WorkFlowy. (If this catches your attention, her Medium post is a must-read – where she gives it to us with all the trimmings):

 

 

Shivani Bhargava – San Francisco, CA – is CEO and Founder of TheRightMargin – “a smart, goal-driven writing app that helps you finish what you write.” She also helps early-stage companies get to MVP, go to market or accelerate getting to product-market fit. You can find her on Twitter

 

If you’d like to let the WorkFlowy community in on anything cool you’re doing with WorkFlowy – big or small – you can drop me a line at: frankman777@gmail.com 🙂

6 thoughts on “Individual Sprints – a WorkFlowy Productivity Hack

  1. Thanks for sharing this extremely helpful – specifically to handle your time. I am curious about Shivani’s comment, “Let’s say you think you have the capacity to do 25 points worth of tasks in a week.” I would love to get the communities’ thoughts on how you would determine that capacity in a quick manner.

  2. Hey Ann, in the screencast Shivani made reference to the “Fibonacci Sequence” as a way of allotting points to any given activity. Here’s a great explanation/ discussion as to why:

    https://pm.stackexchange.com/questions/4251/why-would-teams-use-the-fibonacci-sequence-for-story-points

    A quote from the thread:

    “Some teams also use powers of two, or have a scale like 1, 2, 5, 8, 20. The idea is that the larger the story is, the more uncertainty there is around it and the less accurate the estimate will be. Using the Fibonacci sequence helps teams to recognize this uncertainty, deliberately creating a lack of precision instead of wasting time trying to produce estimates that might also carry a false degree of confidence.”

    Built into the points system is the understanding that determining one’s capacity to get a group of tasks done is by no means an exact science. More often than not, it’s discovered through trial and error/ experience.

    I think there’s a similar dynamic with the Pomodoro Technique… where you work in blocks of time and are constantly evaluating how realistic your expectations are… and in so doing, we learn one day, week and month at a time how much work we can realistically take on. It all depends on your work rhythm… so in my case, it takes me 2-3 times longer to get things done than the average person – due to perhaps excessive tinkering and re-shuffling… I realize this and have learned to be comfortable with this and adjust my expectations of how much I think I can get done in a certain period.

  3. Thanks Frank. So let me ask how would you dertetmine the number of points you have available in a week? In Shivani’s example she said her capacity is 25 points. Estimating my capacity is where I struggle.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s