Advice

My Agile Life: Overwork

by

(This column is posted at www.StevenSavage.com, Steve’s LinkedIn, and Steve’s Tumblr)

(My continuing “Agile Life” column, where I use Scrum for a more balanced and productive life continues).

Uhg.  So as you know from my blogging about agile techniques, I’ve been getting overloaded.  I’m trying to fix this with some success.  So here’s what I’ve been trying.

  • Velocity.  Velocity, the measure of work done in a timeframe, is a big part of Scrum.  One reason to measure it is to see what you can do – but another is to make sure you’re not overloaded.  I can tell my usual workload doesn’t quite work out, so I’m trying to reduce it a bit here and there.  EXAMPLE: Restructuring how much I put into a given project a month.
  • Effectiveness.  Do things better.  I’ve found you can also save time just by doing stuff better.  EXAMPLE: I made graphic templates for upcoming graphic work.
  • Letting go of the schedule.  Work done on time doesn’t matter if it’s poorly done.  You have to re-evaluate and re-assess your schedules and in some cases dispose of them entirely.  EXAMPLE: I had some library donations to make that kept getting interrupted, so I had to accept “it gets done when it gets done.”
  • Iterativeness.  The flipside of efficiency is to not try to be perfect.  Some things are iterative, things you do over and over or regularly.  These can be improved, or mistakes compensated for.  EXAMPLE: Cleaning.  If I miss a hard water stain in the shower it won’t kill me as I’ll fix that next week.
  • Capture.  Be sure to capture any big blocks of time you want to use for something.  EXAMPLE: I have some convention speaking coming up so I literally put it in my schedule as a big block of time to note “I will be doing nothing else then.”
  • Sizing.  I’m sticking with the Fibonacci numbers for sizing my work – in hours – as it seems to produce better estimates.

I’ve also looked at things that mess up my planning and scheduling and productivity.  The Antipatterns.  They are

  • Loading Up.  When you find your maximum velocity of work, it doesn’t mean it’s what you should do.  It’s what you’re capable of when you push yourself.  What is you sustainable rate?
  • Lumping.  When possible break things down so you can calculate your workload – and because it lets you adapt better.
  • Missing lumps.  Some things are just purely about a time commitment, like “setting aside X hours to relax.”  Some things are better lumped together just so you’re not micromanaging.
  • Not looking at value.  When you do something ask what makes it useful – believe me there’s some surprises in there.
  • Bad Deadlines.  Again, deadlines should serve quality, not the other way around.
  • No goals.  When you don’t have goals, you can’t plan.  We often substitute panic, deadlines, etc. for goals – those aren’t goals.  Goals are positive.
  • Done over quality.  Doing something fast poorly can be worthless.
  • Rigidity.  Agile methods are about embracing change, and if you have to keep things rigid, you’re not Agile.  You need to find ways to be adaptable.

Hope these help you out.  Something to look out for in your own life – and anyone you manage.

(By the way I do plenty of books for coaching people to improve in various areas, which may also help you out!)

– Steve

A Writer’s View: Complexity And Convolution

by

(This column is posted at www.StevenSavage.com and Steve’s Tumblr – and hey, think this should go on the Sanctum too?)

Working on “A Bridge To The Quiet Planet” is interesting as in some ways it’s very complex, a tale of a world of science and sorcery that survived a world-shaking war, and the lives of those centuries after the trauma.  In other way’s its simple – it’s a heist/chase story that goes Cohen Brothers, just with a sarcastic sorceress and a disreputable used bookseller.

Complexity in stories is a challenging area of discussion, because it often seems what people say is complex is anything but to me..  As my friend Serdar notes in his blog:

Now, Steve did specifically say complex stories. That could mean one of a number of things, not all of them what you might think. Complexity in a story is too often assumed to be convolution, as in a plot that is very knotty and full of double-reverses and whatnot. I tend to stay away from such things if only because I am not nearly smart enough to pull them off, but also because I have a different idea of what kind of complexity is relevant in a story. For me a story is complex if the pieces in it have a lot of thematic richness, or if the characters are multidimensional and humane. It’s not if I need a map in the endpaper and a list of dramatis personae.

This pretty much hits the division on the head for me.  A story can be convoluted but not complex – a Wile E. Coyote mess of tricks and craziness can exist atop a simple set of characters and tales.  A story can be complex with deep richness and many facets, while being straightforward.

What I realized in my writing is that complexity and convolution are not the same thing, and separating them in your mind is valuable for a writer for several reasons.

First, to separate them is to ask what you’re wanting to write.  Do you want to challenge the audience with double-backs and twists or do you want them to experience richness?  Or both?  To separate complexity and convolution is to help you set goals.

Secondly, to separate them is to ask when is one or the other appropriate within a story.  One part may need complexity, one part may need convolution.  It is possible what seems to be appropriate may, at later examination, not be – a complicated murder plot may be more interesting from the viewpoint of a character who has it figured out, so you can explore their character.

So I’m writing a story that’s complex (in characters) but the overall plot isn’t overly convoluted (it’s straightforward) once you know what’s going on.  This is actually important because if I added convolution to the story, the book might be longer but also more confusing due to the setting’s many unusual elements.

Complexity isn’t convolution.  They may exist together, but can be happily apart – and keeping that in mind will enrich your writing either way.  Plus, it’s OK to write one, both, or none – just know what you want.

(Oh and if you need some other creative boosts, check out my book on Creative Paths!)

– Steve

A Writer’s View: A May Roundup

by

(This column is posted at www.StevenSavage.com and Steve’s Tumblr)

I figure with all the writing I do and have planned, it’d be fun, educational, and good experience to reguarly share my findings on writing.  So . . . I am.  Probably about once a week or so I’ll spew forth the latest seltzer water of wisdom I happen to have handy.

Right now most of these insights come from my first public fiction project, “A Bridge To The Quiet Planet.”  I’ve written fiction a lot before, have edited, have consulted, but figured it was time to return to fiction in style – with a novel.  Short summary: science fiction/fantasy fusion combination of road-trip and religious pilgrimage goes dreadfully wrong.

So the insights to share for May – any one of these might become a later column.

  • Agile works really well for writing – the mindset and the methods.
  • Writing is about loops, finding cycles and patterns in your story.  Because of this plotting one idea may lead to changes, expansions, or new ideas.
  • Never assume anything in your story is “true” until it’s written – discovery is part of the process.
  • Look for Congruence – when things “feel” right.  You want this on all levels of your work, and before you move on from one thing (say from a character idea to a character outline) make sure things “feel” right.
  • Your inner voice is probably right.  The voice that comes after that voice and points out all its flaws is probably less reliable.
  • When plotting, your story may become “timey-wimey” – ideas later on may influence earlier sections.  That’s fine.
  • Characters are the true measure of your world and writing – knowing them means you know your world and story.
  • Characters are a great way to discover your world – designing them makes you ask specific questions you may have missed.
  • Think of your audience – keep them in mind in your writing, what you say, what you deliver.
  • Enthusiasm beats self-loathing for a writer every time. Better to succeed by creating better than tearing down.
  • Beware “Big Rock” ideas that you’re so committed too they drag the story and other ideas down.
  • Don’t “commit” too early to ideas, concepts, or scenes.
  • A small change may quickly scale up and affect your story.
  • Give yourself a place to record ideas without commuting to them.
  • Start over as early as possible so you don’t have to later.  My restarting the plotting cost me 4-6 weeks, but I can’t imagine what’d have cost me if I’d rammed through with my lame initial plot.

Hope these give you something to think about!
– Steve