Click here to close now.


Related Topics: Microservices Expo, Java IoT, Agile Computing

Microservices Expo: Book Review

Book Review: The Agile Culture

Leading through Trust and Ownership

I wish this book would have been around a few years ago. At the time I was trying to convince a manager for several months that the top-down command and control model no longer works. The evidence was not difficult to come up with, you just had to take a look at the last 4 to 6 projects they ran, and the results spoke for themselves.

The really bad part was that it was a completely predictable environment. Orders came from the top to management and down to the worker bees. The projects were always over budget, missed delivery dates, and delivered buggy partially completed products. If you were lucky you got something close to what the business asked for, but sometimes it just didn't work at all, or was so far away from meeting their needs it wasn't usable. Process makes for a predictable outcome, and the top-down command and control style they used, created the same result every time.

That was the bad part, the sad part was everyone in IT knew what was going to happen, but they had no choice but to play along. The business being convinced IT was just a business expense, and not a strategic partner, they just thought this is how it is working with IT. Expensive and you get very little for your money.

This is a very archaic way of thinking and is usually found in businesses over 70 years old. They still don't understand, that in today's world, many companies of any decent size are just an IT company that specializes in a certain type of business. IT is the life line to their customers. People pick up a phone to order a product, but not by making a phone call to their favorite salesman, they use the mobile application your company provides. Don't have one? I guess the order wasn't going to your company then.

As I said above, in these companies you will find the mindset that the business is IT's customer. Instead of a partnership with the goal of meeting the actual customer's needs, the command and control mindset is built into their relationship creating a lot of dysfunction. This is a higher level example of an entire department having no trust from the business unit and no ownership of their projects. This has devastated the morale in IT and without big changes, it won't get better.

In these archaic thinking companies you find very little trust and ownership in all their departments. I see a lot of them today suffering terribly, but insisting on staying in denial. They just won't give up on the mantra- This is how we have always done it, and doing it this way is what got to where we are today. They just don't have a realistic view of where they really are today, and if you don't know where you are today, you sure as heck can't decide where you want to be tomorrow.

This book provides a way out of the anguish that companies like I described above are in. Below are the chapters the book contains-

Chapter 1. Unleashing Talent
Chapter 2. Trust and Ownership
Chapter 3. Building Trust and Ownership
Chapter 4. Trust Tools
Chapter 5. Ownership Tools
Chapter 6. Business Alignment Tools
Chapter 7. Dealing Honestly with Ambiguity
Chapter 8. Tools to Deal with Walls
Chapter 9. Metrics
Chapter 10. Case Study
Appendix A. Quick Reference Guide
Appendix B. Trust-Ownership Assessment
Appendix C. Collaboration Process
Appendix D. Collaborating with Non-Collaborators Worksheet
Appendix E. What to Do about Metrics

I love that this book pushes for transparency by accepting and dealing with the fact that we work in an environment of low certainty and high ambiguity. One of the best things about this book is that when there is an Elephant in the room, they don't just point at it and say "there is an Elephant in the room", they walk you over to it and let it trunk slap you a few times.

My daughter had a habit of striking up a conversation in the middle of her teacher's lectures. She was constantly bringing home notes from the teacher throughout second-grade asking for our help making her understand she cannot speak while the teacher is speaking.

Third grade rolled around and we were at the point of having our first parent teacher conference. I had received no notes asking to help my daughter not to hold mini fashion classes while the teacher was lecturing. Amazingly the meeting went great. My daughter was being a model student. This repeated during the second teacher conference of the year.

Then the third one came. I went in and sat down smiled and said hello to her teacher. Right before my eyes I saw her smile fade away into a twisted sick looking grin, her eyes bulged, and I swear I thought I saw her hair fly out from her skull as she screamed "You have got to do some thing about your daughter!!! I need help!!!". My first thought was,you certainly do need 'help'.

She proceeded to rant on and on about how my daughter won't stop talking in class, and just ignores the teacher when she asks her to stop, along with a dozen other things. I asked her why she told me she was doing great and was well behaved in the first two meetings. She said she is a believer in tolerance. I didn't get it. She explained that she believes every child given enough time will choose to do the right thing and the teacher of today tolerates misbehavior until the child changes.

I won't tell you what I wanted to say, but I did say "well apparently that's not going to good for you. Can I ask why the teacher of today thinks their only role is to regurgitate the curriculum and not teach children the difference between right and wrong behavior? " I thanked her for letting my daughter get all her little girl chatter, and back talking out during class, because of that, she had been great at home.

This teacher attempted this year after year, and year after year it failed. That is a perfect example of complete trust in someone who just didn't have the capacity to understand how to take ownership of their actions. I see this all time. Leaders trusting the same people over and over again and those people failing to deliver over and over again. So what happened. The same thing that happens at companies, complete 100% command and control kicked in. My daughter couldn't sneeze the rest of the year without being written up.

It all boils down to, change, hope, and insanity. You hope the next time will be different, but you refuse to change anything in your environment. It is called insanity. As Einstein put it- insanity is doing the same thing over and over again and expecting different results.

One of the things I would have like to see is a little more dealing with the team member that refuses to update their skill set in order to be more effective, and have no interest in taking ownership. The book touches on helping members decide to leave, and asking them to leave, but that is not an option for these individuals. They themselves, along with their managers, and the majority of the company believe they've paid their dues. Most have over 25 years of service and are headed towards the day they can start using their pension.

This can be a very big problem in companies that have a great retention rate. Many of the company's heroes from the mainframe days are still occupying seats with their same skill sets. Some have moved on, retired, or have been given a new roles in the company.

In one of the environments I am referring to the company has scattered the remaining mainframe era individuals throughout the IT teams. The issue is, those that don't update their skills are hurting their team. They are counted as a full resource, but only provide a fraction of what the other team members provide.

The worst part of this situation is that these legacy team members are not lazy people, and could be used in other areas of the company. Why aren't they? The command and control environment doesn't ask what they would like to do, it doesn't care. Upper management decides where resources are needed and moves people there. This is really blatant in government. If they are in IT, they must stay in IT, although you can tell they are sick of IT.

In some even worse cases the legacy employees have been made managers. The company has been 100% command and control since their inception 100 or so years ago, and they see no reason to change that. Management is therefore trained with in-house made training, which is all geared towards maintaining a command and control environment. This book would be labeled heresy in this environment. If caught with it, you may be burned t the stake. It is an endless cycle of promoting people to the point of incompetency, which adds a little more dysfunction to the environment with every round of promotions.

Because the world says everybody must go Agile and Lean, they attempted to implement Agile and Lean practices. How did that go you ask?
Bill Gates said, "The first rule of any technology used in a business is that automation applied to an efficient operation will magnify the efficiency. The second is that automation applied to an inefficient operation will magnify the inefficiency."
The same can be said about Agile and Lean practices:
The first rule of any software process used in development is that Agile and Lean practices applied to an efficient development team will magnify the efficiency. The second is that Agile and Lean practices applied to an inefficient development team will magnify the inefficiency.
I won't ding the book for not covering the team issue I brought up above, because the book didn't try to cover it. It was just something I would liked to have seen. There are many more difficult situations I could bring up that I would like to see covered, but this book is based on the author's real life experiences. If they have not had to deal with such situations, it is not something they would cover.

That is something I really like about this book. It is all based on experiences. I have said before that there are way too many books, and way too much information available on agile these days. I'll be the first to admit, that every time I see an agile book coming out the first thing I think is how could they possibly still be milking agile. I also must admit, that many of the new books coming out on agile are now reflective of experience, and not based entirely on theory. That was what you used to find in the agile library, all theory and no experience. Now with books like this one, we find great advice based on real world experience.

Trusting people is hard. I always proof of concept a new development team. What choice do I have, especially today when the technology changes with every new project. Every time it has paid off in dividends. Someone always joins the team in the wrong role. I have had several four person teams where one or two of the team members had to be assigned menial tasks, or if possible replaced. This not only works to circumvent disastrous code and a lot of wasted time, it also helps you identify the members you can trust with technical decisions. You may not have time to get fully briefed on an issue before a decision needs to be made. Having a second or third technical expert identified for the team really helps.

There is a big difference between leading and managing. If you want to succeed as a leader, this book is a great read. It is packed with advise on building trust and helping teams take ownership. It also has a ton of advise on aligning with the business and showing you what metrics are the most important in a project. They show you why "hitting a date" is from the land of the lost, and delivering a quality product that pleases the customer is when the project is done.

The book also has 5 appendices packed with tools to help you assess your current situation and then move towards an environment of trust and ownership.

I thoroughly enjoyed reading this book. The authors all have great writing styles and reading it goes really fast. I have about 15 tabs stuck in it, and I will be keeping it close. This is the kind of wisdom I like reminding myself of periodically.

If you buy only buy one agile, management, or leadership book this year, make it this one!!!! If you plan on buying more than one agile, management, or leadership book this year, make this your first one!!!!

The Agile Culture: Leading through Trust and Ownership

The Agile Culture: Leading through Trust and Ownership

More Stories By Tad Anderson

Tad Anderson has been doing Software Architecture for 18 years and Enterprise Architecture for the past few.

Latest Stories
In his General Session at DevOps Summit, Asaf Yigal, Co-Founder & VP of Product at, explored the value of Kibana 4 for log analysis and provided a hands-on tutorial on how to set up Kibana 4 and get the most out of Apache log files. He examined three use cases: IT operations, business intelligence, and security and compliance. Asaf Yigal is co-founder and VP of Product at log analytics software company In the past, he was co-founder of social-trading platform Currensee, which...
The Internet of Everything is re-shaping technology trends–moving away from “request/response” architecture to an “always-on” Streaming Web where data is in constant motion and secure, reliable communication is an absolute necessity. As more and more THINGS go online, the challenges that developers will need to address will only increase exponentially. In his session at @ThingsExpo, Todd Greene, Founder & CEO of PubNub, exploreed the current state of IoT connectivity and review key trends and t...
Two weeks ago (November 3-5), I attended the Cloud Expo Silicon Valley as a speaker, where I presented on the security and privacy due diligence requirements for cloud solutions. Cloud security is a topical issue for every CIO, CISO, and technology buyer. Decision-makers are always looking for insights on how to mitigate the security risks of implementing and using cloud solutions. Based on the presentation topics covered at the conference, as well as the general discussions heard between sessi...
Continuous processes around the development and deployment of applications are both impacted by -- and a benefit to -- the Internet of Things trend. To help better understand the relationship between DevOps and a plethora of new end-devices and data please welcome Gary Gruver, consultant, author and a former IT executive who has led many large-scale IT transformation projects, and John Jeremiah, Technology Evangelist at Hewlett Packard Enterprise (HPE), on Twitter at @j_jeremiah. The discussion...
Too often with compelling new technologies market participants become overly enamored with that attractiveness of the technology and neglect underlying business drivers. This tendency, what some call the “newest shiny object syndrome” is understandable given that virtually all of us are heavily engaged in technology. But it is also mistaken. Without concrete business cases driving its deployment, IoT, like many other technologies before it, will fade into obscurity.
In today's enterprise, digital transformation represents organizational change even more so than technology change, as customer preferences and behavior drive end-to-end transformation across lines of business as well as IT. To capitalize on the ubiquitous disruption driving this transformation, companies must be able to innovate at an increasingly rapid pace. Traditional approaches for driving innovation are now woefully inadequate for keeping up with the breadth of disruption and change facin...
The Internet of Things is clearly many things: data collection and analytics, wearables, Smart Grids and Smart Cities, the Industrial Internet, and more. Cool platforms like Arduino, Raspberry Pi, Intel's Galileo and Edison, and a diverse world of sensors are making the IoT a great toy box for developers in all these areas. In this Power Panel at @ThingsExpo, moderated by Conference Chair Roger Strukhoff, panelists discussed what things are the most important, which will have the most profound...
With all the incredible momentum behind the Internet of Things (IoT) industry, it is easy to forget that not a single CEO wakes up and wonders if “my IoT is broken.” What they wonder is if they are making the right decisions to do all they can to increase revenue, decrease costs, and improve customer experience – effectively the same challenges they have always had in growing their business. The exciting thing about the IoT industry is now these decisions can be better, faster, and smarter. Now ...
PubNub has announced the release of BLOCKS, a set of customizable microservices that give developers a simple way to add code and deploy features for realtime apps.PubNub BLOCKS executes business logic directly on the data streaming through PubNub’s network without splitting it off to an intermediary server controlled by the customer. This revolutionary approach streamlines app development, reduces endpoint-to-endpoint latency, and allows apps to better leverage the enormous scalability of PubNu...
I recently attended and was a speaker at the 4th International Internet of @ThingsExpo at the Santa Clara Convention Center. I also had the opportunity to attend this event last year and I wrote a blog from that show talking about how the “Enterprise Impact of IoT” was a key theme of last year’s show. I was curious to see if the same theme would still resonate 365 days later and what, if any, changes I would see in the content presented.
Apps and devices shouldn't stop working when there's limited or no network connectivity. Learn how to bring data stored in a cloud database to the edge of the network (and back again) whenever an Internet connection is available. In his session at 17th Cloud Expo, Ben Perlmutter, a Sales Engineer with IBM Cloudant, demonstrated techniques for replicating cloud databases with devices in order to build offline-first mobile or Internet of Things (IoT) apps that can provide a better, faster user e...
Culture is the most important ingredient of DevOps. The challenge for most organizations is defining and communicating a vision of beneficial DevOps culture for their organizations, and then facilitating the changes needed to achieve that. Often this comes down to an ability to provide true leadership. As a CIO, are your direct reports IT managers or are they IT leaders? The hard truth is that many IT managers have risen through the ranks based on their technical skills, not their leadership ab...
Microservices are a very exciting architectural approach that many organizations are looking to as a way to accelerate innovation. Microservices promise to allow teams to move away from monolithic "ball of mud" systems, but the reality is that, in the vast majority of organizations, different projects and technologies will continue to be developed at different speeds. How to handle the dependencies between these disparate systems with different iteration cycles? Consider the "canoncial problem"...
Discussions of cloud computing have evolved in recent years from a focus on specific types of cloud, to a world of hybrid cloud, and to a world dominated by the APIs that make today's multi-cloud environments and hybrid clouds possible. In this Power Panel at 17th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the importance of customers being able to use the specific technologies they need, through environments and ecosystems that expose their APIs to make true ...
The buzz continues for cloud, data analytics and the Internet of Things (IoT) and their collective impact across all industries. But a new conversation is emerging - how do companies use industry disruption and technology enablers to lead in markets undergoing change, uncertainty and ambiguity? Organizations of all sizes need to evolve and transform, often under massive pressure, as industry lines blur and merge and traditional business models are assaulted and turned upside down. In this new da...