Agile Life

Steve’s Update 6/5/2017

by

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

It’s my weekly Scrum style standup for the audience – and you’ll notice it’s now Monday.  This is because yes, the week starts Sunday but those updates kind of invited me to move more week stuff into my weekend.  So now updates are Monday..

And now on to what’s up!

What’s Up For The June Sprint?

  • First, Way With Worlds Minibook #1 will drop eom.
  • Speaking at Hydra Comic Con.
  • Finishing the full plot outline and writing the first chapter of “A Bridge To The Quiet Planet” hopefully.
  • Donating some books to libraries.
  • A few social events.

So what have I done the last week?

  • Way With Worlds Minibook #5:  Got behind on this, trying to get back to it.  I think I’m kinda of tired writing these, so maybe book #6 just needs to be done in one go.
  • Social: Finished up Fanime.
  • Her Eternal Moonlight: The sale completed!
  • “A Bridge To The Quiet Planet:” I think I’m back on track.  I’ve got an expanded plot outline done more or less on time.

What am I going to do this week:

  • Way With Worlds Minibook #5:  Try to, well . . . write for it.
  • “A Bridge To The Quiet Planet:” I’m going to finish up the full plot outline – scene for scene – this weekend.  This is the big one.  If I can get this to work I’m ready to write.  Not 100% sure I’ll do it, but let’s give it a shot!
  • Writing: More blog posts – now alternating my agile findings and my writing experiences.

Challenges and blockers:

  • My allergies are back, so we’ll see how bad that hits me.
  • I realized I’ve not done any new generators – I might shift some priorities to do a fun one.

– Steve

My Agile Life: Breaking It Down So It Works Together

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

One of the challenges of doing any work is that things we want to get done can conflict with each other, are hard to schedule, can only be done at certain times, etc. That makes anything, from delivering software to my own attempts to organize my life a bit more challenging.

What I found is that when you figure out the things you want to do – the stories and tasks – don’t just design them or break them down in a vacuum. Design them so they’re as easy to do as possible, hard to block or disrupt, and of a size where you can have a good chance to complete them in a reasonable time. This way you can maximize value, deliver quicker, and be disrupted less – and even when you are disrupted, you can switch priorities easier.

Here’s a few examples:

  • You’ve got to buy gifts for Christmas. You could have a simple Story “buy gifts” and “order for everyone on the list” but there’s a lot that could go wrong – lack of gifts, delays, a need for research, and that’s one big block-of-work. If you make a task for each person you can do them in order in one go – but if there’s any delays or unavailable items, you can take care of some of the orders a different way. This lets you timeshift or adapt (and is good policy).
  • You’ve got a massive art project to do. You prefer to do it in one 8 hour go, and you really can’t subdivide it without losing your mojo. You make sure your other tasks are broken down so you can easily fit them around the needed 8 hour block, and get the important stuff done early. (By the way, in my experience the Big Block does not always work, so be careful)
  • You plan to deliver a book chapter for a technical manual to an editor. It’s going to be a hefty chapter and require some research. You decide to make each section its own story.  This allows you to adapt (by doing them out of order), get them to the editor quicker (thus avoiding lots of WIP), and gives you a good sense of organization.

A rule I found helps is this: break down stories so that they don’t just deliver value, but require as few tasks as possible, and those tasks are as small as you can reasonably make them.

This will mean more stories, but stick with me here.

Stories deliver value. If you can break down stories into the smallest chunk of actual value, then you can deliver (and evaluate) that value faster. In turn because you are working on smaller pieces, you can shift them around, scheduled them, deal with interruptions by working on something else, etc. This also lets you focus better – and change focus if needed.

So if you’ve got lots of small stories, it’s probably a good sign. Sure there may be some big ones, but if a lot are small then you can move them around while you deal with the big ones.
– Steve

My Agile Life: Agile Is A Dialogue

by

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

This is my continuing column on my “Agile Life” experiment where I use the Agile techniques in Scrum for a more productive, less-stressful life.   My latest insight to shareis how Agile and agile techniques like Scrum are about diaogue.

These dialogues may be with yourself, with one person, or with many people. But there’s always a dialogue to be had. Not surprising, it’s part of the Agile Manifesto.

Three of the four parts of the agile manifesto are about communication – among the team, with customers, and with the reality of change. You talk to each other, to your customer, and respond to reality.

I’ve had plenty of dialogues in my Agile Life practices;   I’m the Product Owner, the Scrum Master, and a Team Member – sometimes it helps to have a little sit-down with myself.  Here’s a few:

  • In my planning I’d look at my Backlog and my Projects and have to ask what delivers value.
  • I’d ask how to break down stories into deliverable value.
  • In breaking down my Stories into tasks I’d have to ask what the tasks were and how they’d complete a story.
  • In my daily reviews, I’d ask what’s next and think over what I had to do – and maybe coordinate with people on things like when I’d run an errand or who could help me with something.
  • My Cumulative Flow would help me realize how much work was in the air – and how much I was delivering, in case I was overworking myself.
  • As I took care of things, I’d get ideas for the next Sprint or ways to improve, and make sure I had revised my plans and improved my methods.

Scrum, the Agile method I’m most experienced in, actually sets up tons of “dialogue moments in the form of ceremonies:

  • A planning session.
  • Daily standups.
  • Retrospectives.

So when you’re trying to be more Agile, to use Scrum or whatever, remember the need for dialogue – even with yourself. Asking good questions means getting good answers and doing good works. Even if it’s just you sitting there asking what’s the best way to cook for a party.
– Steve