Agile Complexification Inverter

I was working with a failing team some time ago.  I use "failing" to describe the outcome of the team - not the people on the team.  Are you OK with that description? An issue arrose in the stand up - a team member that was to verify the quality of a procedure did so and reported that there were a few records that didn't match expectation in the data set.  Upon inquire the number of records not matching was over 2000.  Most people acknowledged immediately the exaggeration - I could tell by the laughter.  After about 10 minutes of discussing the details of the problem - it appeared the team had a handle on the specific situation. I stopped the discussion and inquired if they could name the impediment.  One team member did a great job of describing the impediment as a _communication gap_ .  Wonderful - I could work with that - the problem had a name and it didn't include anyones Proper Name. "If the problem has a first name; we are going to hav...

In the 1900s the automobile industry was the most important and innovation industry in the USA.  But one could question if this was good for our society in the long run.  And one could question if they actually innovated.   See Russ Ackoff's 1994 speech "You see, the automobile is destroying urban life around the world..." 11 minutes mark. In the early 1900s there were few automobiles, very little infrastructure created to support the industry.  For example the road system was still designed for horse drawn wagons and the wagon wheel (remember a steal rim and wooden compression spoke wheel).  The future  US Highways , or the 1950s Interstate Highway System at the cost of $425 billion were decades and many innovations away. There was no gas service station, there were however horse stables, farriers, and blacksmiths in each town along the roads.  There was no real "road map", there was no road naming system, like was created in 1926 - the United Sta...

Pondering some messages... both the implied, the implicit, the unintended, and the overt. What are the messages when a manager calls a meeting and schedules it for an hour... then repeatedly states that they have nothing really to talk about, and after the group does the appropriate amount of beating the horse, the manager states "I will give you back 20 minutes."? One overt message is the meeting is over you are dismissed and you have 20 minutes returned to you to get real work accomplished. Another implied message is that your time is not your own and now the manager is returning their time, time they require of you to attend their meeting, is now returned to you so do with it as they have done - spend it well.  [ Because anyone delusional enough to think that time belongs to someone, is just off enough to believe that one can spend time. ] The unintended message - the part that rubs me raw; like when manager's refer to people as resources (typically implying...

Now that everyone knows about Bill Murray's movie Groundhog Day - I love February 2nd.  It's my favorite , most enjoyable, beloved, cherished, esteemed day of the year.  And I don't need to tell you again how many LIKES I give this redundant day... so on to the story. Bill & Groundhog Well this happened about ten years ago, and about 6 years ago, or maybe it was 4 years past, and seems like we did this about 24 months ago...  or it could be today! The Agile Transition Initiative at the company has come upon an inflection point (do ya' know what that is...  have you read Tipping Point ?).  I'm not exactly sure of it's very precise date... but  Feb. 2nd  would be the perfect timing.   The inflection has to do with which direction your Agile Transition Initiative takes from this point into the future.   Will it continue on it's stated mission to "transform" the organization?  Or will it stall out and revert slowly to the stat...

I'm working with a large networking (telecommunication) company on a mission critical new initiative to replace existing B2B account services functions that are siloed and separate with a new sexy UI where all the services are aggregated in one portal.  The development has been underway for over one year.  It is touted as an "agile" program.  Yet an interesting impediment has never been resolved.  That is the internal WiFi/Lan systems appear to be overloaded with the strain of development, over utilized with the number of people that are squeezed into the floor plan (I call the sardine can).  This system fails quite frequently, it is a well know impediment to sprints being completed, stories integrated into the build, builds tested, access to the QA server, etc.  Yet this impediment remains after months and continued growth of the program. I wonder if the problem is that management feels that they can't do anything about infrastructure at one of the large...

What metrics do you collect to  analyze  your scrum team? It's the Trends of Metrics that matter. We live in a world of data and information.  Some people have a mindset that numbers will diagnose all problems – “just show me the data.”  Therefore many directors and senior managers wish to see some list of metrics that should indicate the productivity and efficiency of the Scrum team.  I personally believe this is something that can be felt, that human intuition is much better in this decision realm than the data that can be collected.  However, one would have to actually spend time and carefully observe the team in action to get this powerful connection to the energy in a high-performing team space.  Few leaders are willing to take this time, they delegate this information synthesis task to managers via the typical report/dashboard request.  Therefore we are asked to collect data, to condense this data into information, all while ignorin...

A typical impediment sticky annotating the blocked task. Just making an impediment list is not good enough.  Yes, it is a start.  But only the start.  Raising impediments at the daily stand-up meeting shows that a team is mature enough to recognize that all problems are better solved in the light of day.  Problems are easier to solve when more than one person is working on the issue.  One of the first steps to getting multiple people working on an impediment is to make it known to the team. Yet this is the start, not the end of the process.  Yes many newbie teams believe that the Scrum Master's job is to resolve these impediments.  That is a wonderful misconception and will work for a while as the newbie team learns the power of an agile mindset.  But only the maturing teams learn that it is their job to remove these impediments. So what are 7 aspects on a great impediment card living on the top of your impediment list? Title - th...

When it come to being a messenger - we all should receive a Kevlar vest. So you have bad news - you feel that the upper management will not like to hear about it.  Here are two options. The Harvard Business Review recommends a simple 4 step process : Describe. Provide a general overview of the problem, and explain the impact. Be sure to position this in terms of what matters to your manager.  Identify a solution. Recommend a specific solution or approach, along with alternatives.  Analyze your solution. Share the pros and cons and explain the implications. Be prepared to discuss the risks or barriers that may be of concern to your boss.  Accept responsibility. Let your manager know that you are willing to take the responsibility for the outcome of your proposed approach.  Or you could use the Two Step : Lift carpet. Find somewhere to put the problem out of sight - out of mind.  Sweep. Keep sweeping the problem out of the bosses sight ...