agile

My Agile Life: Fix A Few Things

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).

Many Agile methods use some kind of retrospective to review and improve. I adore them but find they can drag for two reasons: sometimes people hate them and sometimes people go overboard.  It can become a venting session or it can become a case of people shutting down.

Personal retrospectives can be a drag as well for the same reasons, though I find it tends towards the “overboard.”

I find that the “overboard” and the “underboard” are part of the same problem – that retrospectives can be overwhelming.  If you want to discuss what went wrong on a sprint or on a project, you can probably easily find tend or even hundreds of things.  This can lead to people endlessly listing off problems – and people trying to ignore then because there’s so many (and their egos feel threatened).

A retrospective needs you to both focus and not be afraid.

What I’ve learned both as an Agilist and in my own life (where I can’t escape any of this) is that you need to limit what you try to improve. When you focus on one or two or a few things to get right, you can get them done – focus on every problem and you’ll never start, or you just won’t try and review your work.

Besides, as you focus on a limited amount of improvements you can also reinforce the issue that many of the problems that came up were already taken care of.  All those hundreds of problems got taken care of by reasonably mature people or a reasonably mature person and it’s probably not worth going over.  Focus on what needs to be improved.

On top of that, the focus on a limited number of issues can take your ego out of it.  You ignore the vast amount of things you can complain about to focus on things you can and want to fix.  It tones down the fear you may feel of going over the many things that did go wrong, dealt with or not.

I’ve found the “power of Few” to be very helpful in that I can focus on getting better in specific ways – ways that have real value.  Plus it doesn’t’ trigger any insecurities

As an addendum, you should always seek to improve outside of reviews and goals. Good opportunities to get better abound all the time, and seizing on them is a big part of an Agile Mindset. It also helps you get used to facing and fixing problems on the fly – so they don’t gum up your retrospectives (and your self-esteem).

(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: Plotting, Pantsing, And Agile

by

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

So this week I finished the plot outline of my book. I’ve been expanding it iteratively, from one-sentence summaries to full character profiles, based on the Snowflake method. The method itself works great with Agile – and brings up a very important point about writing.

Writing, it is said, is often divided into “pantsers” (seat-of-my-pants writers) and “plotters (organized writers like yours truly). As a plotter, I’d like to note that you do end up “pantsing” anyway, just on a finer-grained level. At some point in writing you can only plan so much before you have to write – it’s a matter of degree.

This truth can frustrate some plotters, because you can only define so much before there’s nothing left to do. Your ideas may be totally wrong, your plan may be horrible, your plot awful – but you won’t know until you start writing.

This is the same thing one faces in software, where Agile methods continue to hold more and more sway – you can only design so much before you have to write code to see if it works. It’s the same with writing.

So now that I have a plot, how will I confront my inevitable discovery of all my horrible mistakes?

First, I won’t be afraid. As I like to note, Eat Your Failure.

Secondly, I plan to do reviews:

  1. I will write a chapter at a time and share it with people for feedback.
  2. I will review my full plot outline every chapter completed to make notes and see what changed or what I want to modify or what I want to add.

I know my plot outline (all 8 pages in a spreadsheet) is only so good. But it’s good enough to get moving with an idea of where I’m going, and good enough to improve when I find mistakes or get new ideas. It also is stable enough that it probably won’t fall apart and deep enough it’s not shallow.

Two notes:

  1. I have trouble seeing how “pantsing” can work for complex stories, but perhaps I have something to learn there, no? Maybe I should “pants” a short story sometime.
  2. Based on my own experiences and what I’ve seen in the market you can in theory plot a novel pretty finely, and its very easy if you’re using tropes or taking a “light” approach. Not sure how good it’d be, but it seems doable.So what have you found?

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

– Steve

My Agile Life: Eat Failure, Not Your Peace Of Mind

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).

Doing Agile in my personal life taught me how to fail. You’d think at my age I’d have plenty of practice failing, but there’s always something to learn.

Ever obsess over a problem or mistake? Of course you have. We make mistakes then play with them in our heads over and over even while we fix them, berating ourselves as we do so. Even when the mistake is fixed, the self-flagellation may continue afterwards.

This is terrible for our peace of mind. Every minute spent in worry is a minute not spent doing something else. Worry can eat up so much time that we get less done – which only makes us worry more.

In business, we’re familiar with the equivalent of this worry; blame game and paralysis through analysis. A department or group becomes so locked up by blame-flinging and over-analyzing nothing gets done. Such a department is as trapped just like person locked in an endless cycle of self-loathing. In fact, I’d say it’s pretty much the same thing

In doing Agile for my personal life as well as work, I came up with the term “Eat Your Failure.” Agile methods use failure to fuel improvement. Failure’s not just part of the process – failure powers it. Failure is actually not bad (well, not entirely).

This has helped change my attitude towards failure in a very short time, and am finding it fear of it starts to diminish. I’m far more aware of when fear of failure or annoyance with it drains my time. I’m less upset with it because I take an “eat your failure approach.” By treating failure differently, I have much more peace of mind and get more done.

(Trust me, on the novel I’m working on, that’s such a change of pace I get lots of fear of failure.)

In large organizations, this “eat your failure” mindset is as important if not moreso. If I get obsessed with failure and don’t think in Agile methods, I can slam a beer or go to therapy. In an organization, bad attitudes towards failure can become part of culture and outlast the people there (and their supplies of beer and therapy). Worry can become institutionalized.

Taking a positive or at least progressive view of Failure doesn’t just bring efficiency. It brings peace of mind.

Of course in our lives or in our jobs, we have to make sure that’s part of our culture, be it just us or an entire company. It’s up to us to make that change and encourage the change in others.

But honestly, how many people or businesses would be much happier if they just said “Let’s live with failure and improve” over obsession and guilt and denial?

Yeah, we know the answer.

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

– Steve