Friday, March 9, 2018

TDD for Infrastructure as Code. Collaboration with security and governance.

One of the benefits of using a Test Driven Development (TDD) approach to Incremental Infrastructure as Code is that the same tests that were used to build out the system can later be used to monitor the system for security or state.

This can be a great way to help collaboration between development and security or governance folks.

Consider reaching out to an experienced technical coach on TDD or BDD to learn more.

A link to a potential illustration of how this might work is in the references below. 


Friday, March 2, 2018

Getting started with Test Automation for Incremental Infrastructure as Code

Today, I was reminded about a simple approach that has worked well for me in the past.  

When you do something manually for the 3rd time...Automated it.

Perhaps it can work for you.

Thursday, March 1, 2018

"Give them the environment and support"

The Agile Manifesto includes the principle:
"Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done."

Specifically, consider "Give them the environment and support they need"

Do you believe the meaning of this statement would be the same for people identifying themselves as...

(sorted in alphabetical order)

  • Agile Coach
  • C.E.O.
  • Developer
  • HR Manager
  • Lean Consultant
  • Operations Manager
  • Product Owner
  • QA Manager
  • Scrum Master
  • Team Lead
  • Vice President
  • (insert any other title or group that makes sense in your context. A small subset chosen for my sanity) 

It might help you to find out if others have the same understanding as you do.


Friday, February 23, 2018

"The only way you can (insert topic) is to (insert method)"

"The only way you can (insert topic) is to (insert method)"

We have all seen these types of posts.

I know from experience....

There is rarely only one way to achieve a goal.

Consider using ....

- for many people, 
- for many organizations,
- effective approaches include 
- I have used 
- I have seen (x) used 
- (x) might work
- (x) might be appropriate to the situation
- generally
- often
- experience shows

(none of these are definite and fixed)

Add your own to your own personal list.


Note: I was careful not to say "There is only one way to achieve a goal".

Friday, February 9, 2018

The many who help

There are many, many people involved day-to-day in changes to improve their work environments, teams or companies. This can be challenging work and cause many sleepless nights.

Although I greatly appreciate bloggers, authors and conference speakers, it would be awesome if more time was spent thanking the quiet people.

To all of you....

You are appreciated. Thanks for what you do.

Saturday, February 3, 2018

A Discovery Approach to learning about leadership

Hoodoos - Mike Caspar, 2017

Ask someone you consider to be a leader how they might answer this. What you discover might surprise you.   (will bring you to a popular social media site).

Thursday, January 18, 2018

Could you stop development?

In your environment... 

If you wanted to stop development of a product or feature... Could you?

A few potential questions to consider about your context...

Does the system you have in place, provide a mechanism to stop non-valuable work for the benefit of the company without fear or recrimination? 

Do teams know what to do to stop non-valuable product development?

Is it considered Failure or Success to stop development of a product that will not deliver value?


Thursday, January 4, 2018

Sponsors and Users and Sustainable Pace

In reference to the Principles behind the Agile Manifesto, (

Consider this principle:

Agile processes promote sustainable development.
The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

During workshops and sessions in software development groups there is almost always discussion about sustainability for development team members. 

However, there is rarely discussion about the sponsors and users being able to continue at a sustainable pace.

Written a different way, the principle could read....
  • The sponsors should be able to maintain a constant pace indefinitely.
  • The developers should be able to maintain a constant pace indefinitely.
  • The users should be able to maintain a constant pace indefinitely.

Ask yourself... In your discussions about the Agile Manifesto, is any time spent getting feedback to determining if what you are doing allows Sponsors and Users to be able to maintain and constant pace indefinitely?

Ask yourself... What does this mean in my context?

Have fun.