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.

Sunday, December 17, 2017

CapEx, OpEx and the Enterprise Agile Coach

Are you considering becoming or do you identify yourself as an Enterprise Agile Coach?

To me at least, this implies a certain degree of knowledge of enterprise financial reporting.

As incremental or agile approaches to the delivery of value grow in popularity, the ability to understand the difference between CapEx and OpEx becomes increasingly important.

A large organization may need time to prepare or learn more to properly support some of the changes in approach. 

If for no other reason, consider your ability to be taken seriously during discussion with financially oriented people. 

Imagine that the difference might be the building of a 100 Million dollar asset versus the building of a 10 Million dollar asset and 90 Million dollars worth of expense (an oversimplification only to inspire research. My apologies to my accounting contacts).

Of course, there is much more to the enterprise agile coaching than this one topic, but ignoring it is not good for anyone.  I really dislike lose-lose situations.

Consider ......

At a minimum, you should be able to explain the difference between CapEx and OpEx and the potential impact to Balance Sheet and Income Statement.

If you can't do this basic task with understanding, think about your circle of influence or the circle of influence of the person you are trying to help.

Some ideas for you to get started....

- take a basic accounting course 

- ask a finance or accounting person for insight (a great way to build a new relationship)

- Ask yourself.. "How would I feel as an Investor in the company with the different results ?" (public or private)

- Read some books or articles.

- Ask yourself... "How will I prepare my client for inevitable discussions with regulators, shareholders, or auditors?"

- Consider finding an experienced person with enterprise experience to help you navigate and learn about this.

- Bring someone into your local meetup that understands this topic well.

Many transitioning companies will need some time to learn and assimilate new ideas. In some cases, lawyers may need to get involved to help navigate the change. 

A sample trigger phrase to remind you that you are in an environment where this is fundamentally important: "In service date".  

Enjoy what you learn :->

Saturday, October 21, 2017

Consider a simple thank you.

I recently witnessed a situation where someone put a huge amount of effort into a post to clarify a topic that many people are confused about. 

In the complex domain being discussed, they were not advocating their explanation as the complete (or best) solution... They were simply helping others to understand based on the specific context of the questions involved.

That person knows that that only one answer cannot solve a complex situation and believes that small steps matter. They are willing to respond in a way to help others instead of trying to correct an entire system in one post.

Many people understand that there will always be something to add or improve in a complex system or understanding.

When a poster creates an article to help others (or simply move the needle a bit), this does not mean they lack knowledge of other approaches or parts of the complex domain.

Please consider that sometimes simply thanking them will help keep everyone engaged and comfortable sharing and learning..... 

One-upping someone is not always necessary (or helpful)... 

How about just saying ... 

"Thanks for the insight"...  

Just a thought.

Tuesday, October 17, 2017

Blockchain and Privacy

First, let me say I am not an expert on Blockchain. That being said, I have been following the advancements in this domain for some time.

One feature of a Blockchain is that a previously written block cannot be amended or adjusted in any way (Feel free to correct me if I am wrong).

This all makes for a very secure, distributed history of all things in the chain... 

Blockchain is becoming increasingly talked about in markets involving financial transactions...Trades and currency transactions seem to be a current hot-spot for the concept. 

Recently, I read an article (sorry I do not have the reference, but it stuck with me which is why I created this post).  

The article talked about storing contractor data and recruitment data in a Blockchain and using "smart contracts" to link contractors with potential jobs.  Someone posted it in a feed and proclaimed... "The Blockchain is going Meta".  

I have been wondering about security of sensitive private information and the ability for incorrect or bogus information to be removed.

If you consider that information in a Chain can never be deleted, how does one comply with laws such as the EUs "Right to be Forgotten" legislation  by example? 

My mind races with potential abuses to the concept of information being freely available to anyone with access to the chain.

Consider the example of skills being auto-matched to a requirement.. and the history that would forever exist about this.  I can see several pros and cons to this depending on which side of the situation you are in. 

I sincerely put this question out to experts in Blockchain... 

How DOES information get deleted, or can it (or should it)?  

It seems to me that just because you can put something in a Blockchain, maybe you shouldn't always?

I really don't know the answers.. I just have questions... 

I made this post hoping to find someone wondering.. 

What should go into a Blockchain and how we do we protect our privacy?   I think the time to talk about this is now. If you are in this field, are you having these conversations?

Based on my current understanding of Blockchain, if a country legislated a "Right to be forgotten" for any information in a Blockchain, it would be impossible without starting a brand new chain.  Do I have that right?

* references

Blockchain -

Right to be forgotten Legislation   -

Tuesday, August 29, 2017

Stop bashing corporate leaders

  • Pictures of Leaders with angry red faces
  • "Leadership doesn't get it" blog posts
  • "Greedy Board Member" blog posts
  • Posts about "foolish management"

... the list goes on ...

Do you publicly humiliate the management or leadership of an organization you work for (employee or contract) and then later complain you can't get time with leadership or wonder why you can't connect with them?

If so.... From a purely effectiveness level... If you publicly mock the leadership of an organization, you can't really expect to have a trusting, open relationship with the same people you just mocked. 

How would you feel if the leaders started publicly mocking you?

Something to think about next time you decide you want to post a "let's poke fun at the leaders" message.

Saturday, July 29, 2017

A misunderstanding about contracts in an agile context

The Agile Manifesto contains the following words...

Customer collaboration over contract negotiation

I recently experienced a person suggesting that as agilists, we can sign contracts and then just do what feel is right and that every decision after signing should still be a negotiation. 

There are ways to make flexible contracts. I have seen contracts designed to specifically require collaboration. I have seen contracts that get regularly re-negotiation based on changing needs. 

My preference is to work with a minimal contract (or with pure collaboration if that is possible).

There is always the option to not sign a contract you cannot live with.

Signing a contract with the intent of ignoring it is not collaboration. I would argue that it is very disrespectful to the other party involved. 

I have a different word for someone who signs a contract with the explicit intent of ignoring the terms... and it isn't Agilist. 

Reference: Agile Manifesto -