agile

Agile Creativity – Principle #6: Facetime

by

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

Agile principle #6 is a simple and sweet one about communications.  It needs no embellishment:

The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

This is obvious.  If you want to get the most done, effectively, talk to a person directly.  I could probably stop here and you and I have easily discussed 70% of the value of this Principle.

Obviously I’m not done – and we’re talking Agile and Agile Creativity, so there’s some subtleties to go into.  So I’d like to discuss this principle in a bit more detail, and focused on creative work.  This probably would be faster if we were face-to-face, so revel in the irony.

Good communication is vital to all work – creativity moreso.

It’s obvious that you get more done productively if you actually go and talk to people, and in-person conversations convey a lot of information effectively.   In-person you can judge gestures, expressions, voice pitch and more.  In-person you sync-up with people better.

When you communicate effectively, you say more, hear more, and can work effectively.  You can adapt better because you’re actually talking to someone directly and saying so much more.  I’ve seen team behavior change and become more productive when face-to-face activities are introduced.

In creative works are challenging to communicate because they involve everything from intuitive interpretation to understanding complex emotions.  This makes face-to-face or similar far more important because there’s just a lot to convey.  So if you have to collaborate creatively, get talking face to face

(As you may guess, I accept we can’t always get face-to-face, which means) . . .

Face-to-face isn’t always possible, so make due

Communicating with people on your team face-to-face sounds great.  It’s also probably impossible at many times due to location, travel, mutual loathing, and what have you.  So what do you do?  You find the closest-way to face-to-face in order to interact.  This could mean:

  • Video conferences (with sharing)
  • Chat programs (of course)
  • Phone conferences.
  • Meeting face-to-face when you can and packing in all the communication you can do.

You do what you can.  This may mean when it comes to creative works, you have to get pretty innovative.  You may do things like sending people videos and following up with online chat, and it may not be face-to-face, but it’ll be as close as you can get.

Is this somehow violating the ideal?  No, because . . .

Face To face is the most efficient and effective method – not the only one.

This Principle is a recommendation and a statement of truth – face to face is the best way to communicate within your team.  It’s not the only one, it’s just the best.  Agile isn’t big on hard rules and structures.

But sometimes the best is not available, so you do what you can.  Don’t fret, don’t beat yourself up over it.  Just do what you can.

A quick thought for solo creatives.

Does this matter to the solo creative?  Actually, hidden within this Principle are two important lessons:

  • You may be solo, but changes are you still are depending on other people for some things.  Delivering supplies.  Providing editorial services.  Etc.  Face-to-face still applies to these “team-like” connections.
  • Are you taking time to really communicate with yourself?  Analyze results, do research, consider where you’re going?  You might not be – learn to pay attention to yourself.

A moment for review

This simple principle is pretty easy to review:

  • Face-to-face is the best way to communicate with your team members.
  • If Face-to-Face isn’t possible, learn the best alternatives.
  • Even when solo, practice good communications techniques and take the time to self-reflect.

Simple one there.  Good, because the next Principle seems simple – but has a lot of depth.  In a way it’s a core to a lot of Agile thought . . .

– Steve

Steve’s Update 3/11/2018

by

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

Hey everyone here’s my latest update – and yeah, going with the personalizing thing.

So what have I done the last week?

  • A Bridge To The Quiet Planet: Editing continues and reaching to my pre-readers.  Which, you know if you want to be one let me know.
  • Writing: As of Tuesday I’ll be halfway through my Agile Principles for Creatives.  Definitely turning this one into a book when done (thinking this may be a general thing with me)
  • Seventh Sanctum: I had to do a bit more backend tweaking (mostly stuff to deal with modern browser requirements), so the Registry took a back seat.  I am wondering if this is WORTH it, so I’ll probably post an Alpha.
  • Other: Thank goodness, the unpacking is now mostly done.

What am I going to do this week:

  • A Bridge To The Quiet Planet: Continue editing.  I’m going to try to get the almost-final run done soon – when I’m in the zone I can get a lot done.
  • Editing: I want to get the edit of version 2.0 of Epic Resume Go done this week.
  • Writing: Continue with the blogging – and I’ve identified several future projects.
  • Seventh Sanctum: Get out the Alpha of the Registry.
  • Art: I’m helping with a book cover and want to finalize that this week.

General

  • Debating how to handle these statuses. I view them as compliments to my newsletter, so not sure if I should break them up etc.

– Steve

Work And Effort: Not Always By The Numbers

by

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

Latley I was feeling overloaded but couldn’t figure out how much. Turns out it was mostly in my own head.

Now I’ve been through a move, changes at work, and more. So the last two months my own workload estimates have been a tad off, all things considered. Now that I’m back at it, I decided it was time to get a handle on my work and my life. This included:

  • Making sure I tracked other time-consuming activities, like me workouts.
  • Getting back to my projects.
  • Recovering from the move.

So, I looked at my plans for March . . . and felt overloaded. Why was that, because in my head it made sense. Not much changed. Hell, I wasn’t moving at least.

Something didn’t feel right. You know that feeling of Really Not Right, and I couldn’t place it. Nothing came to mind, so I began to play with my schedule, looking at time taken, past work. Suddenly, something became very clear – an error you may have made in your own personal plans.

What I found was that I had overestimated the amount of work ahead of me, and that made me feel overloaded.

Normally, I’m for a little overestimation, just to be safe. But past a certain point, overestimation becomes not a buffer, but a source of confusion. Your gut, your mind, and your estimates can’t figure out how long things take or where time is going. That’s where I was.

  • I wanted to track more of my regular activities, making sure I accounted for them and didn’t get overloaded. I made sure to pad them a bit – which may matter little on one or two tasks. But when you’re talking things like cooking or working out that you do a lot, then padding adds up pretty fast.
  • I wanted to get back to my projects. Which of course I now was cautious about, so I overestimated a few of those. Which wouldn’t be as bad except I always juggle 2-4 projects.
  • Finally, I wanted to “catch up” on anything that got behind from my move, and of course, overloaded myself on top of some over-estimation.

Yes, in my effort to be Thinking Ahead and Develop A Good Backlog, I ended up overestimating so much out of caution I confused myself. So, uh don’t do that.

I also found I had to modify one of my estimating techniques. Check this out, it may help you.

Fibonacci Revised

As I mentioend in my Personal Agile, I estimate the time things take in hours using Fibonacci numbers – 1,2,3,5,8,13. This is common in abstract estimating as people are bad at determining small differences in large things – it’s easy to know if something is 2 or 3 hours, harder to know if it’s 4 or 5 hours, and real hard to tell if something is 25 or 26 hours. So Fibonacci estimating uses numbers with increasingly large gaps to force you to A) use certain numbers to avoid fiddling in the middle, with the side effect of B) By the time you’re tackling something so large maybe you should break it the hell down.

Now on the high level (beyond 3 hours) this helped me. But, I had lost control of detail on the lower end.

I didn’t differentiate between a 30 minute task an an hour. Or a 90 minute task and 2 hours. As I break stuff down pretty finely, I had overestimated work in many cases – and as noted as I also track many repetitive tasks, this balooned my estimated workload.

So now my “Modified Fibbonachi sequence” is .5, 1, 1.5, 2,3,5,8, 13. I give myself a bit of leeway on the low end.

I’ve wondered if in time I’ll learn enough I won’t need any kind of sequence as a crutch. I suppose I’ll find out – and share it with you.

Takeaways

So some takeaway lessons:

  • If your sense of what you can do and the time you’ll think it’ll take don’t “feel” right that’s a good warning.
  • Be careful on overestimation and adding too much buffer time to things you’re trying to get done. That causes confusion – and may squeeze out work you can do.
  • In estimating how long it takes to do things, tools like Fibonacci numbers may help on the high end, but give yourself leeway on smaller estimates.

– Steve