2017 Agile Dev + Better Software - Tricentis Interview

Comment

2017 Agile Dev + Better Software - Tricentis Interview

I met a colleague, Noel Wurst, at the Agile Development conference. He's now working for Tricentis and he asked me to do an interview for their website content. Of course, I agreed.

I thought I'd share my replies to his questions. And I want to thank Noel for asking me. It was an honor to contribute...

Here are the interview questions that Noel asked and my replies:

1. Continuous feedback: I hear a lot of people talking about needing to shorten feedback loops, automate reporting, and development, test, and release cycles that deliver continuous feedback. And I agree. CF is highly valuable. But sometimes I wonder if, once people put those things in place, can they immediately act or respond to that feedback? How important is being able to do that, and not just collect or note that feedback, but adjust on the fly to make new decisions, pivots, and responses continuously as well?

I think this is a really important point, Noel. And it’s not simply related to continuous feedback, but also to the continuous improvement cycle. For example, feedback on adjustments that are raised in team, project, or organizational retrospectives. To your point, our lean-age should be towards doing something about our discoveries, in taking action.

Comment

Agile Software Capitalization...Boring!

Comment

Agile Software Capitalization...Boring!

One of the topics that I've typically avoided at agile conferences and in discussions with colleagues is software capitalization. Particularly in agile contexts.

The first reason is that it's usually used as an excuse to undermine agile principles and as a means of continuing old practices. 

The second is that I find it somewhat...boring. Yes, it's often necessary for many enterprise or larger-scale contexts. But I'd rather the teams focus on innovation, customer value, and deliver than on capitalization.

And the third reason, which is somewhat embarrassing, is that I never had a succinct recommendation for folks on how to handle it in agile contexts. I always felt that I said "it depends" too often.

Excuses

But all of those reactions were excuses. And I do realize that it's a serious topic for many folks. So, imagine my delight when I came across a real-world blog post from Stephanie Davis of Valpak in Tampa Florida that explained how they've been handling it. 

And not only that, the post contains some reference post that nicely provides additional capitalization examples and advice.

Wrapping Up

I've shared this post to be my "Go To" reference for capitalization. Thank you, Stephanie, for sharing!

Stay agile my friends,

Bob.

Comment

There IS an I in an Agile Team

1 Comment

There IS an I in an Agile Team

I’m beginning to think that we’re too focused on the team when we talk about agile. Everything is focused towards that end.

Team this and team that.

But what about the individual on the team? I contend that they count too.

  1. Make sure your voice is heard; in many team’s individuals can get lost. Often the loudest of voices seem to become the default voice of the team.
  2. Make sure you take time for yourself; self-learning, downtime / reenergize, reflection are keys to your personal growth and learning. Always increase your value proposition – you.
  3. If you’re introverted, give yourself permission to be alone; this includes working from home and “separating” from the team on occasion to work by yourself.
  4. Gain personal feedback; don’t get caught up in team-only feedback loops. While important, you need personal feedback as well. Make sure you’re getting it from your team and leaders.

1 Comment

2018 - Coaching Circles

Comment

2018 - Coaching Circles

I've been running experiments for the past year around doing virtual coaching. I call the sessions Coaching Circles and they take the loose format of a Lean Coffee hosted via Zoom.

They run for 90 minutes and, so far, attendees have seemed to gain great value from them.

Oh, and did I mention that they're free?

I've increased the frequency to (roughly) 2x a month for the early part of 2018 and have them scheduled for January - May. If you'd like to participate, you can get more info and register here - https://www.eventbrite.com/e/coaching-circles-wbob-galen-tickets-41323509730

Just one of the ways I'm trying to "give back" to our wonderful agile community.

Stay agile my friends, 

Bob.

Comment

My New Role – TechWell Program Chair

1 Comment

My New Role – TechWell Program Chair

I’ve been speaking at TechWell events since around 2000. First, I started out with track talks. Then I started sharing full-day and ½ day workshops. I’ve also been invited to deliver several keynotes at the Star and Agile Dev / Better Software conferences.

All-in-all, it’s been a professional relationship that I’ve really enjoyed.

Recently, the long-time program chair, Lee Copeland, stepped aside. I truly want to thank Lee for the years he invested in helping me grow this side of my consulting practice. I owe him a great deal.

Program Chair & Talent Scout

Given my history and experienced, TechWell approached me to help fill the Program Chair role for the:

  • Agile Development
  • Better Software
  • DevOps

Conference series going forward.

The conference has a West / East format. The West version is held in Las Vegas, typically in early June. The East version is held in Orlando, typically in early November.

The programs are usually developed 8 months in advance of the conference, so you need to reach out to me early if you’re interested in participating.

The program chair is responsible for pulling together approximately:

  • ~4 Keynote presentations
  • ~4 full-day workshops
  • ~20 ½ day workshops
  • ~60 60-minute track talks

across the four major themes (Agile Development, Traditional Software Development, DevOps) of the conference.

And the talent scout part of my role will focus on looking for new and interesting topics, speakers, and formats to introduce to the conferences.

1 Comment

Advice for my Corporate Colleagues – Find your Blind Spots!

Comment

Advice for my Corporate Colleagues – Find your Blind Spots!

Years ago, I worked for a company called Micrognosis. I shared a little about the company in this post. As I recall, I worked there from the late 1980’s to 1996 or for about 10 years. Over my entire 35+ year career, it was my longest tenured job. And I did a lot of growing there, both in my role and in my self-learning.

When I left Micrognosis, I moved to North Carolina for a software leadership role at Bell & Howell Mail Processing. So not only did I change jobs, but I relocated my family as well. To say the change was a bit scary for me and my family is a bit of an understatement. But we moved and never really looked back.

I realized after about three months at Bell & Howell that I’d stayed in my Micrognosis job for a bit too long. That I’d developed some “blind spots” that I didn’t even know I had.

Let me explain.

Comment

Agile Planning – Getting Punched Every Day

1 Comment

Agile Planning – Getting Punched Every Day

There’s a famous Mike Tyson quote:

Everyone has a Plan
until they get Punched in the Mouth

It reminds me of the ultimate futility of estimating and planning. Or investing too much in both of those endeavors. Particularly in the area of software product development.

Another related quote is from Eisenhower. It surrounds the value of plans (artifact) vs. planning (activity):

I have always found that in preparing for battle that
Plans are Useless,
but Planning is Invaluable

That is:

  • The activity of exploring requirements via user stories and acceptance criteria;
  • The activity of minimizing (MVP) the results so as to learn;
  • The activity of making estimates as a vehicle to explore size, scope, risk, and design approaches;
  • The activity of discussing construction and deployment strategy;
  • The activity of delivering work to stakeholders and gaining their feedback.

Are all more valuable than fixed or static plans, which are intolerant of the punches that are inherent in software development - learning and discovery.

Wrapping Up

The next time you find yourself getting “stuck in” your plans or thinking that planning is more important than doing and adjusting, then please remember these two quotes. Also remembering, that Tyson and Eisenhower weren’t practicing agile software development. But they were indeed…agile.

Stay agile my friends,

Bob.

1 Comment

You might be an agile leader if...

2 Comments

You might be an agile leader if...

I delivered a keynote at the Agile Development + Better Software + DevOps conference put on by TechWell on Wednesday, November 8, 2017 in Orlando. 

The feedback I received was wonderful and it seems the talk resonated with quite a few of the attendees. 

At some point, I'll get a link to the video of the keynote and I'll share it here. Until then though, here's a link to the slide from the talk.

2 Comments

Advice for leading an Agile Transformation

1 Comment

Advice for leading an Agile Transformation

Nathanial Willis posted this in LinkedIn recently:

I asked Steve Denning for advice on how to successfully lead an agile transformation and here's what he said:

  1. Get a bullet-proof vest and hockey mask because you're going to get beaten and be shot at! (As he laughed)
  2. Stop communicating over email - do it face-to-face; preferably in a bar. (No seriously)
  3. Discover your executive leader’s problem. Find a story of how another company solved that problem and share it.
  4. Focus on the 20% that want to change. Forget about the folks that don't.

1 Comment

Just a little…Forgiveness

Comment

Just a little…Forgiveness

I was attending the STPCon conference in Washington, DC last week (week of September 25). As always, there were quite a lot of old friends there. Folks I usually only meet on the conference circuit.

The conference committee tried a Lightning Talk format for the first time. They invited 7-8 speakers on stage to give 5-minute, focused talks. Dot Graham gave one that is still sticking with me.

She focused on creating (fostering, inviting, inspiring, allowing) a mistake culture. One where everyone focused on two aspects of their mistakes:

  • Learning from them, and
  • Forgiving themselves for them.

I’ve heard the learning part many times before. But this is the first time that I’ve heard “forgiveness” mentioned as part of creating a learning culture and it struck me.

In a team environment mistakes always happen. Sometimes they’re small things. And other time, they’re large ones which have an impact on the entire team.

I have a saying that I often share in my coaching and teaching. I amplify that agile teams (all teams really) succeed and fail as a team. That is, we don’t throw anyone under the bus, but we deal with everything from the solidarity of a WHOLE TEAM perspective.

I now want to add other attributes to that description:

  • We reflect as a team;
  • We learn as a team;
  • We make mistakes as a team;
  • And we forgive ourselves as a team.

I love the Norm Kerth sentiments regarding the Prime Directive for retrospectives where he sets the stage for the “intentions” of all attendees.

Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.

I think this sentiment helps us in our view towards mistakes and our forgiving each other (including ourselves) for making those mistakes.

I know that I for one can be really hard on myself when confronting the things I’ve done wrong.

As Dot reminded me, I want to encourage all of you in your agile journeys to be kind and forgiving of one another. Remember, they are ONLY mistakes and we all make them!

Stay agile my friends,

Bob.

Comment