Agile Life

My Agile Life: Multitasking. Sort Of.

by

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

More on my use of “Agile” and Scrum in my life!

Agile methods tend to discourage multitasking as well as having a lot on your plate.  The goal is to avoid distractions (with less multitasking) and avoid having a lot on your mind (by limiting work in progress).  Of course, as we always get interrupted, we tend to multitask a bit.  Sometime things almost have to be done together or require such long delays (like a chat) that multitasking is almost needed.

Let me note that I do think you should avoid multitasking.  I do believe in limiting work in progress.  But there are times multitasking is fine or even good.

What I’ve found that in my own life, what helps is to identify what you can do while doing other things.  Preemptive multitasking as it were.

You know what I mean:

  • You’d like to watch some tv, but friends want to chat online – you can do both.
  • You’d like to come up with a shopping list which you can do while watching tv as it’s not a rush.
  • You want to do some online research, so you do it while chatting or on the phone – heck, the other person may have ideas.
  • And so on . . .

You’ll note a lot of this is recreational/social.  This is where I often multitask when doing things that are “gruntwork-like.” Not something requiring intense effort, nor intense focus, but things that have a lot of “bite sized” tasks so I can watch TV or chat to take the edge off.  Sometimes it even helps to have others around.

This has helped me timeshift a lot lately, as well as get more done.  Yes, it’s multitasking, but only when appropriate.

As  a note I will be the first to say that you should avoid multitasking when it reduces your ability to focus, get things done, or do them your best.  I usually do it when the multitasking is something more fun, or social, and so on.  Be careful when you do this until you learn what works for you.

However, if you make multitasking conscious, you can do it right.  You can also choose when not to do it because you’re more aware.

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

– Steve

My Agile Life: The Project Doesn’t Matter

by

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

More on my use of “Agile” and Scrum in my life!

So this is going to sound weird, but one thing I realized in Agile practice, and my own use of the Agile technique of Scrum (with a touch of Kanban), is that the Project isn’t the most important thing.

Yes, I know, heresy. Projects are books, right? Projects are art, true? Projects are games, correct? I talk Projects all the time.

No. A book, a piece of art, a game is a product. Products deliver value to the customer and that’s what matters.

Projects are ways to get things done, to produce products, a useful conceptual tool, but that’s it.  The idea of a Project helps you complete a Product that has value.

Yeah, let that sink in. All your planning, all your schemes, everything are secondary to the result. Think it’s hard for you? I’m a guy with a ton of certifications on the subject of Project Management. In short, I actually have certifications on the second most important thing.

Except this is liberating. I don’t have to take Projects seriously or any other organizational tool.  All that matters is if this concept, this idea, this tool, this idea helps deliver value.  That’s it.

This is where Agile as a mindset shines. It’s outright saying that your goal is a result.  That’s it.  Everything else is just a tool on the way to the result.  You only have to care so much.

This is where Agile techniques shine, they’re tools to help you find blockages and get to the results – but like any tool you don’t have to be attached to them. Scrum this year becomes Kanban. This level of Project Breakdown is replaced by another.

I still use the term Project.  It’s useful.  I just don’t have to get invested in it.  It’s all about results.

By the way if you’re focused on Projects and not results – why?  Are the results even worth seeking?

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

– Steve

My Agile Life: Meetings

by

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

More on my use of “Agile” and Scrum in my life!  This is another one inspired by my personal agile, but a bit more focused on business.

Meetings are why we can’t reduce meetings.

I find my personal practice of Agile – with a one-man team – informing me about my work in the business world. Since I do all roles, since all information flows to and through me, I actually have a decent feel of what productivity is like because of personal Agile. Thanks to this experience, I can better see when things are messed up in the business world.

Lately, this reasonably decent personal workflow has made me see just how crazy meetings can make us. Trying to schedule them in my own life is tough enough; and then when you look at the job world . . .

We’re drowning in meetings. Sure we complain, but we keep doing them over and over again. We know they waste time. We know people don’t want to be there. We know the people on either side of us are checking Facebook.

We KEEP DOING MEETINGS.

Meetings are terribly inefficient, at least in the way they’re run. If you invite 20 people to a meeting that’s an hour long and each person gets 10 minutes of benefit out of it, then you spend 1200 minutes so people get 200 minutes of benefit. Sure, they may multitask and do other things, but they won’t do it well as if they were focused.

But we KEEP DOING MEETINGS.

I could list any number of reasons why pointless meetings are held, but I want to share a realization of why we don’t stop this insanity.

There are clear solutions to reducing, avoiding, or improving meetings. I’m sure three or four spring to mind as you read this, such as information radiators and quick check-ins. Despite having these clear solutions, we do not use them, and we’re back to 20 people in a room hating it.

Frustrating, isn’t it? I’m sure you’ve tried.

Having worked to transform teams, improve process, and so on, I’m painfully aware that any attempts to change how people work takes time and effort. It also takes meetings, because you have to coordinate, plan, normalize, and so on. Getting rid of meetings . . . may take meetings.

That’s the bogeyman under the bed of meeting-reduction. If we want to get rid of meetings, we have to make an up-front effort to do so, and that effort may require meetings. People don’t want to do these meetings, and might not even have time for them.

We can’t reduce meetings because of all the meetings we have.

Really, it’s enough to drive one to drink. I recommend Licor 43.

What’s the way forward here? In the past, I resorted to either incremental changes or just barreling ahead. My personal Agile work helps as it provides me a lot of gut-level explanations and insights (like this) to share with people, which helps the situation. I’m hoping this personal insight helps people get around meeting-phobia.

But at some point, you’re gonna have to have that meeting. To stop meetings.

Yeah, I know.

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

– Steve