Monday, April 24, 2017
One of the greatest articles written about software development is entitled “The Big Ball of Mud.” It describes how most software come into being during the 1970’s and 19080’s. It then goes on to illustrate how short term thinking, entropy, and poor software development created the legacy systems which many developers and consultants struggle with today. These systems are rickety. Often they are ignored until they are so brittle that they cannot scale or no longer serve the customer needs. This is the world I live.
It is a world of stand-up meetings with off-shore teams. Meetings with upper management explaining that Visual Studio 2003 is no way to develop contemporary software. It is budget meetings where you have to describe continuous integration to an accountant who cannot monetize more responsive systems. It is the world where I fill out performance appraisal goal sheets in spite of growing evidence that contemporary performance evaluation processes do not work.
As a scrum master, we do it because we want to build systems which work. We do it because software developers should be making software instead of dealing with corporate politics and bureaucracy. We do it because public companies need to make the transition to the current century and global economy. The software is just the first step when we talk about business transformation. It is why I keep going.
Until next time.
Monday, April 17, 2017
|An agile coach can learn from a bunch of rabbits.|
The rabbits are more than a form of escapism. They are a reminder of the natural world. Each day the world is trying to destroy that warren of rabbits. Each day they find a way to gather food, avoid predators, and make more rabbits. These creatures are fluffy and adorable survivors; reflecting on this reality, it dawned on me as an agile coach I can learn plenty of lessons from these specimens living in my back yard.
Charles Darwin said the species most likely to survive are the ones most responsive to change. I have lived in my home for over thirteen years. In that time neighbors have come and gone. Fences have gone up, and many pets have made efforts to hunt down the rabbits. With each change, the rabbits have adapted. They forage around the fences and make themselves hidden when people walk their dogs. A parent accompanies young rabbits, and thy do not bother snacking on grass when I put fertilizer down. My neighbor has gotten into the act and has decided to stop planting rose bushes. Change and responding to change are an essential ingredient to survival.
My rabbits reminded me of engineer and lean management pioneer, W.E. Demming who said, “Survival is a choice.” Each day the rabbits in the yard choose to do what is necessary to survive. The minds of rabbits are not as developed as humans, but every brain cell in the rabbit skull is preoccupied with survival. People for all our mental ability can be distracted. Distractions pull us away from the necessary things we need to survive another day. Our obsession with status in the office distracts us from our jobs. Obsessing over the stock price distracts us from providing customer service. Being the alpha dog on the development team neglects necessary software quality. Humans are distractible creatures, and those distractions pull us away from what is needed.
So each day as a scrum master, coach or business person is a choice. You can choose to survive, or you can pay attention to the distractions surrounding you. From a distance the choice seems simple, people want survival and necessity. At the moment we concentrate of distractions, and they undermine our survival. Choose survival and change over distraction. If a rabbit can do it, so can a human.
Until next time.
Monday, April 10, 2017
|Being a scrum master is hard.|
Dealing with Sleep –Agile teams work anywhere in the world, and if you are a large corporation, any software solution requires an off-shore team. Development teams are located in India, Northern Ireland, and Russia. All of these places are numerous time zones away which means to communicate with them you need to be up early in the morning or stay up late.
I have decided to take the early morning route. My day begins at six and ends at three in the afternoon. I am usually in bed by 8:30 PM and the process starts over the next day. This time shifting allows me to deal with the off-shore teams. It also grants me two hours of “me” time to do administrative work and writing before others get into the office.
Working with Others –Servant leadership requires mental toughness because you work with messy people; individuals who don’t follow instructions or won’t take coaching. Each day, I am forced to work with these messy people. It is the most difficult part of my job because I am accountable for these individuals.
Lately, I have punted in this responsibility leaning on my human resources professionals and upper management to deal with these situations. I go about my day attempting to serve as an example to others and trying to be kind. Sometimes, it is all you can do.
Unwinding –The hardest part about working in technology is that your mind is always attempting to solve problems. You may be out of the office, but your mind is still wrapping around that gnarly data issue holding up the project. You are attending a family function, but mentally you are back at the office.
It is why weekends are so important to me. I do not respond to mail from the office or offshore. I try to enjoy lighter activities. Finally, I avoid my computer for a full day. This little bit of unplugging goes a long way.
So these are some of the strategies I have to deal with the emotional stress of being a scrum master. I would like to learn some of your techniques.
Until next time.
Monday, April 3, 2017
|Talking about forgiveness.|
My professional career has was shaped by my training in journalism and engineering. The world of mass communications is very judgmental. We criticize television anchors for hair color choices and how good their dentition looks on camera. Radio disc jockeys are slaves to ratings and program managers who can crush your career. Ratings mean money and if you provide ratings, people will ignore some of your worse personal faults.
Engineers are also a judgmental bunch and are willing to back up that judgment with the scientific method. The code could run a few nanoseconds faster. The class could better use the Liskov Substitution principle. Finally, you could always tighten up the code to make it less error prone. There is additional machismo where team members compete to assert dominance using their intelligence or programming skill. It is brutal, and these environments discourage vulnerability and innovation.
As a scrum master, you are encouraged to help remove these dysfunctional behaviors. Sometimes a scrum master gets caught up in these bad practices. When you do, you are going to hurt the team. When you hurt the team, you are undermining your credibility in the organization, and with the people, you are supposed to serve. The first thing you should do when you hurt your team or someone on it is making amends and apologize. Asking for forgiveness is hard, but it reinforces the agile values of respect and openness. A team which can forgive each other when they make mistakes is going to be higher performing than one which is not.
Forgiving yourself is a much harder skill. We know ourselves better than anyone else. We are also the least forgiving of our mistakes. We can feel like frauds to ourselves, and this is imposter syndrome. Our emotional intelligence may be below average, and we find ourselves in situations which would puzzle others. Finally, emotional control can be undermined by people who just do not want to improve. You become a tangled bundle of rubber bands, and you feel like you can snap at any minute. You do snap you feel riddled with guilt and self-loathing. Over my career, I have spent a few mornings thoroughly hating the person I see in the mirror. These feelings are not rational or objective. These feelings just are, and you cannot escape them.
I have been leaning on friends and family for the last few weeks to receive relief. I am seeing a doctor in order understand if the stress of the role is contributing to my emotional recriminations. Finally, I have been avoiding alcohol and caffeine. My brain chemistry is bad enough, and I don’t need to make it worse with outside stimulants and depressants. I am making a conscious effort to try and forgive myself for past mistakes.
From the outside, this process is not going to look beautiful, but I need to do it if I am going to improve as a scrum master. Everyone deserves a dose of forgiveness now and then.
Until next time.
Sunday, March 26, 2017
The hardest part of being a leader is the emotional self-control. How do you maintain your emotional even keel when you have people lying? How are you supposed to trust people when they let you down on a regular basis? How do you inspire others when they are more interested in the office pool and watching the clock at the end of the day? Usually, in this blog, I try to provide answers which I have discovered over the years. This week I am out of answers.
I am pretty worn out at the office and I have been struggling with sleeplessness. I also am feeling whipsawed by professional and personal setbacks. I am not much good to myself or anyone else right now. I am kind of messy and in a corporate environment that is a forbidden state.
I will be back next week with more wit and wisdom but for the moment I am going to take a rest.
Until Next time.
Monday, March 20, 2017
|Don Quixote got nothing on me.|
As a scrum master and agile coach, I am a big believer in the idea of servant leadership. The Marine Corps saying, “Ductus Exemplo,” is starting to become slang among business executives. It is a fantastic concept, and I strongly support it. The hardest part of being a servant leader is the everyday realities of being in charge of complicated software projects and managing people who are equally messy. The mask of command and professionalism falls away, and you become vulnerable which for a leader is dangerous.
This danger of vulnerability means your raw nerves are exposed, and your emotions are controlling you rather than you controlling your emotions. Losing emotional control means you will say things you should not and do things impulsively without thinking them through. It is a dangerous place to be and one which can undermine your leadership credibility.
I have to confess that the above situation happens to me more than it should. I become a fountain of rage at times. In particular, when confronted with an individual who refuses to be accountable for their conduct I become a character from a Robert Louis Stevenson novel. I get angrier when I spend time coaching someone, and they ignore my direction. It makes a person feel like Don Quixote jousting with windmills. The reward for your trouble is getting knocked off your horse and the laughter of by-standards. Getting up and dusting yourself off to do it again looks stupid and futile when you have to do it with weekly regularity.
So here I am at my most vulnerable, filled with rage, feeling like a failure and believing the effort is futile. These feelings can be fleeting, or they linger. It is the worst when you are alone in bed trying to sleep, and the vulnerability is thicker than the darkness in the bedroom.
Like any leaders, I have to deal with these emotions and the emotions of my team. It is not easy. The rewards are fleeting. I promised myself that when I became a business leader, I would try to be firm, fair, and inspire others. I fall short from time to time, but I still aspire to that ideal. I have no choice; it is a promise I kept to myself and to the people I serve. People depend on me.
Until Next time.
Monday, March 13, 2017
|Without "Never Events" |
a doctor is nothing more than a glorified butcher
The term “never event” came from a medical paper from the National Quality Forum. These are mistakes which should never happen in any medical setting. Some examples of these never events are, people receiving the wrong type of blood during a transfusion, surgeons amputating the wrong limb, and discharging an infant to the wrong set of parents. If something like this happens, the doctor is subject to profound liability, and a patient could die. It is why they are called “never events.”
I thought about this, and I felt that those of us in the software business should have a series of “never events” for our profession. If we are going to improve in the agile community, we need to have a set of standards and those standards should include things which should never happen.
Here is my list of never events for software development –
- Code which exists in production should never reside on individual’s computer; it should all reside in source control.
- The database administrator should never ignore system backups of data; data should be backed up regularly and before scripts are applied to the system.
- All code which performs business logic should have unit tests; this way you will understand where the system has changed and what the possible changes are.
- Network servers should receive regular patches and security upgrades; this will discourage hackers and avoid technical debt.
- A developer should never work longer than 10 hours; fatigue causes mistakes.
- Before checking in the code, it should be code reviewed by another developer; an extra set of eyes on the code prevents errors and helps to learn.
Until next time.
Monday, March 6, 2017
|Working in technology should|
not feel like being in a sweatshop.
According to the United States Census website, approximately 7.3 Billion people live on the earth. According to the Verge website of that roughly 18.5 million people know how to write and maintain software. If you do the math, only .05% of individuals on the planet know how to keep the modern global economy moving. In short, there is too much work chasing too few people able to do the job.
Since software can be written quickly in a café in Nigeria or a pub in Northern Ireland, the laws of supply and demand get twisted into a pretzel. Domestic developers are pitted against offshore teams to keep wages low but because the skills are still rare wares are relatively high compared to other professionals. Something has to give, so IT professionals become swamped with work.
IT professionals commonly work long hours and fight unrealistic deadlines because of this labor shortage. Software professionals become contingent workers because much of their work is project based. They are hired and fired at will and often treated with contempt because they are often “the geeks” they have to pay. So many people in the profession do receive excellent compensation, but they have zero security or respect. Like rock musicians, they are only getting paid when they are working. Unlike rock musicians, we rarely have adoring fans.
Making matters worse is the H1-B visa. The United States immigration service provides this service. In short, if you are a foreign national and work in the United States you need an H1-B visa. If you lose your job you have 30 days to find a new one; otherwise, you are deported. Over my career, I attended many staff meetings where everyone was afraid to talk because if they offended the Vice President, they would be rolled off the project and deported back to the country of origin and this is why I compare the H1-B visa to indentured servitude.
Finally, many managers who lead IT teams have no understanding of the messy nature of building software and treat it like the manufacturing of machine tools. They use project management and manufacturing techniques to lead IT professions which create numerous situations of labor alienation and crushes productivity. IT professionals like any other employee have to put food on the table. IT professionals put up with the lack of respect, overwork, poor security, and incompetent leadership for one reason – the paycheck.
It should not have to be this way. The Agile reformation started because many smart people felt there was a better way. People could do work more productively and more sustainably. It is why I am and agilest. It is also why I will not put up with ever working in a lousy environment again. I am getting to old for that kind of grief.
Until next time.
Monday, February 27, 2017
|Harassment is unacceptable always|
I have been adamant on this blog that the technology world needs to be more accommodating to women. I have openly criticized the misogyny of others in the technology business. This week Susan J. Fowler described her experiences working as an engineer for Uber. I will let the blog post speak for itself. As a developer, you should not have to put up with unwelcome sexual advances from management. Also, when you make a credible accusation of harassment, it should be treated seriously by human resources.
I think this is part of what Slate magazine calls, "..the open hostility many technology firms have for women." I have noticed this throughout my career and have repeatedly called it out. Women are just as good as men as software developers. Gender is not an obstacle to success in this field.
I suspect that misogynistic men join the software business for three principle reasons; 1) they like building things, 2) they like showing off their intelligence for ego gratification purposes, and 3) people in the technology business like creative destruction especially if you can flout social norms.
Building things is a natural human endeavor. Building things are traditionally masculine in many cultures. Thus, women involved with technology could be regarded with suspicion because they took part in a traditionally male activity. Since the rise of second-wave feminism, men have been pushing back in the indiscrete ways to women who want to participate in manly activities. I firmly believe that this is insecurity on the part of some men who feel threatened by women competing with them for success.
Since the early days of Western civilization, men have enjoyed bragging. They would brag about athletic prowess and business success. Scientists and philosophers would opine about their intelligence to anyone who would listen. Over the last four thousand years, men continue to do these things and being the smartest, best, and most successful engineer is a gateway to more success. Thus, the engineering culture of software includes plenty of people who are willing to tell you how smart they are. A select few can back up that claim. Throwing women into this completive and egotistical environment is a recipe for harassment.
Finally, the notion of creative destruction appeals to many. For the smart but emotionally unintelligent, an algorithm is a tool for vengeance for every playground bully, spurned romance or humiliation suffered. Success is the best revenge and what better revenge than to ruin someone who metaphorically kicked sand in your face financially. For the people who are not technically gifted but are more emotionally intelligent and competitive, the world of technology gives them a place to move fast, take names, and amass lots of money and power. Naturally, these folks gravitate to sales and management.
Combine the need to build things with egotistical preening and the ability to engage in creative destruction; you have a toxic stew of masculinity which is particularly hostile to female engineers. If the technology business wants to become more agile and fruitful, this kind of behavior needs to stop before a sexual harassment suit with punitive damages in the hundreds of millions of dollars shuts down a promising technology company.
Quid Pro Quo sexual harassment or hostile workplaces are antithetical to Agile. It undermines trust on software teams. It halts the exchange of ideas at the firm. Finally, it creates an environment of fear which acts as cancer on any organization. As Agile Coaches or Scrum Masters, we need to be on the front lines and help manage this behavior out of any organization. What happened to Susan Fowler should not happen to anyone at any company. That fact it happened at a technology company makes me doubly determined to make sure it does not occur at any technology company I am associated.
Until next time.
Monday, February 20, 2017
|Listen and Disagree|
One of the more interesting books about leadership is “Team of Rivals,” by Doris Kearns Goodwin. The central thesis of this book was that President Lincoln had a unique leadership style where he relied on the opinions of political rivals in this cabinet to help him better manage the events of the American Civil War. Having a room full of devil’s advocates made Lincoln a better leader. Numerous other articles and books have also surfaced which emphasized that diversity of opinion and perspective is necessary for success and innovation.
Lately, my blog posts and discussion on the Google plus agile community are being challenged by coach from Europe. Some people would recoil from this kind of push back; I do not. This individual has credentials and plenty of experience in the field so while I may disagree with his opinion; I respect his perspective. I am a firm believer in disagreeing with people without being disagreeable.
My approach to Agile and Scrum centers around the Agile Manifesto and Agile Principles. The Scrum Alliance gave me formal training as a Scrum Master. Finally, I have spent nearly four years in the role of a scrum master shipping software with domestic and offshore development teams. I have seen some things and done some stuff. My experience colors my agile knowledge and opinions.
The product owner has the hardest job in the scrum. The Scrum Master is a Coach, Therapist, and often the bad cop which keeps things moving forward. Finally, the development team generate shippable code each day and are the unsung heroes of the process. I live this experience every day and hope each of you who read this blog gain from my knowledge.
Disagreement is healthy, and if you are not willing to consider other opinions and activities, you are not going to grow as Scrum Master. Listen to others who you disagree with; you never know what you might learn.
Until next time.
Monday, February 13, 2017
|Make sure you mean it!|
When things go badly in spaceflight mission control can terminate the mission. When that happens, the astronauts turn the ship around and head back to earth via the shortest route. When things go wrong on a scrum team, we have what is called an abnormal termination. The sprint ends immediately, the team does a retrospective and plans a new one.
There is a contentious debate in the Agile community about who has the right to terminate a sprint. I belong to the ideological camp that a scrum master should have this terrible duty. I feel this way because the scrum master is the protector of process and improvement of the team. When the Product Owner or the development team is in a hopeless situation, it is up to the Scrum Master to recognize it and take draconian measures.
Terminating a sprint is a huge deal. Do not do this lightly. It should be the plan “C” or “D” for any sprint. Terminating a sprint creates all sorts of attention in an organization and is profoundly disruptive. When a Scrum Master kills a sprint, it is the equivalent of Zuse saying, “Release the Kracken!” Do not do it unless you are certain. Otherwise, it is like pulling a fire alarm because you do not want to go to class.
The following are the rare reasons why a scrum master ought to terminate a sprint.
Project funding has changed drastically-In an uncertain global economy, projects get canceled, and new ones are spun up. These events impact your plans. If this happens, the scrum master may want to terminate the sprint. The termination will give the Product Owner, development team, and Scrum Master a chance to take stock and decide what the next steps to pursue.
The Product Owner is fiddling with a sprint while it is in progress-I working with a product owner who was under so much pressure they could not prioritize work. Sprints would begin, and stories would be swapped out with others. Things which were a priority during sprint planning would be dropped days before the end of the sprint and replaced with stories of equal size. The development team was forced to try and do the same amount of work in half the time. Confronted with this bad faith behavior, I hit the self-destruct button and brought it to the attention of my Vice President. Leadership replaced the Product Owner in the aftermath. The development team resumed sprinting.
The team grossly underestimated the work they could do in the sprint-We have all had the “ten-minute change,” conversation. A product owner or someone from the business asks for a change to the system. The developer listens to the request absentmindedly and says the change takes approximately ten minutes to perform. A week later the developer admits the change affected other systems and it would take longer than expected. Soon the rest of the development team is sucked into correcting the situation.
As my mentor, Angela Duggan would say, “developers are afraid of looking incompetent or unskilled.” This fear pushes software developers to underestimate work. The team commits to something and then realizes it is more complicated than first expected. If your development team has with six weeks of work in a three-week sprint, it is acceptable to hit the reset button.
These are three of the rare situations where you might terminate a sprint. If you have other suggestions, I would love to hear them.
Until next time.
Monday, February 6, 2017
|Scrum should not be a cargo cult.|
The primary criticism of my article was that I was encouraging a “cargo cult” kind of scrum. The term comes from a Scientific American article from 1959 which documented primitive tribes in Melanesia coming in contact with missionaries and soldiers. The connection prompted these indigenous people to create cults to encourage cargo to be delivered to them. Primitive air strips, airplanes, and shipping terminals cropped up in the hope that actual cargo planes and people would show up.
The pre-modern culture felt if they mimicked the trappings of technology without understanding the principles behind that technology they would receive the prosperity which comes with modernity. This assumption is wrong. The tribes created many faux landing strips and cargo depots in the South Pacific.
People in the agile community, use the story of the cargo cult to illustrate the difference between going through the motions of agile and being agile. In a perfect world, a business would reconfigure itself to follow the word and spirit of the Agile manifesto. We do not live in a perfect world, so it is up to scrum masters and agile coaches to provide structure for the transition from traditional business to agility.
The events of scrum provide a means to help speed that transition. Business people and developers are forced to inspect, act and adapt to changing situations. That is the heart of an agile business.
When I refer to the meetings and events of the scrum as rituals, I mean the meetings should have purpose and significance. I am not attempting to create a “cargo cult” in an organization.
I am glad someone challenged me on my assertions, and I look forward to more give and take in the future.
Until next time.
Monday, January 30, 2017
|Becoming a scrum master is like becoming a priest|
The role of a Scrum Master is a complicated one. I have written about the topic numerous times. As I have grown more comfortable in the role, it occurred to me that this position resembles the life of a parish priest or Protestant minister. You are always visible and accountable to the people you serve. I firmly believe in the need for a human being to have ritual and routine in their lives. Both Carl Jung and Joesph Campbell, mention that the collective unconsciousness is something which needs nurturing. If we do this, then we are on the way to building effective teams.
The daily stand up-Each day the team gathers around the metaphorical campfire and talks about what they have done, what they will do, and obstacles. Working in an office creates a few anti-social behaviors. It is very easy for people to cocoon into their desks and ignores others. The stand up breaks people out of that unhealthy habit. Each day for 15 minutes they interact with the scrum master and each other. The group stands because it forces people to pay attention to one another. It also keeps side talk to a minimum. Finally, it helps foster a sense of teamwork because everyone is participating and involved in the success of the project.
After a few weeks or months, the scrum master should not facilitate the meeting. Instead, the team should learn to run its stand-up meetings. It is part of the ethos of self-organization. It is essential to the success of agile at any organization.
Backlog Grooming or Refinement –The Product Owner has the most difficult job in agile. They work with the “business” and the development team to create software each sprint. Backlog refinement is where most of this job happens. The Product Owner and the development team go over the backlog. This meeting is designed to clear up any misunderstanding, explain user stories, and set priorities. It is an informal meeting with back and forth conversations. The Product Owner facilitates this session. It can be done regularly each day or scattered around a work week. The keeps communication between the team and the product owners flowing.
Sprint Planning –The Scrum Master, Product Owner, and development team get together to decide what they want to work on in the next sprint. Using the refined backlog the team and the Product Owner decide what to do next. This meeting is a little more formal as the team estimates and tasks out the work. The meeting also ends with a consensus about what the sprint goals are and how to meet them.
Sprint Review or Demo –One of my biggest frustrations I had as a developer was spending a year on building a software product and then showing it to the user community and having them say it is not what they wanted. The sprint demo is designed to eliminate this situation. After a sprint, the development team shows off their work to the Product Owner and the people who are stakeholders in the project. Here they gather notes and feedback where they can improve. The demo also shows the business that things are getting done and that they will have software in a measurable amount of time.
The Retrospective –The retrospective led by the scrum master. It is a combination of rituals. It is about what happened. It is also a look forward at how to improve. Everyone participates in the process, and everyone contributes. It is up to the Scrum Master to take notes and help the team improve on how it is supposed to do its work. The retrospective is the most difficult part of the scrum process, so a scrum master good at facilitating meetings is essential.
So this is my take on the rituals of Scrum and why we do them. They are all important, and if you do not do them, the effectiveness of your scrum teams will suffer.
Until next time.
Monday, January 23, 2017
|Software is messy|
If you are not already following Angela Dugan’s blog, “The TFS Whisperer,” you should. One of the posts struck me for its honesty and courage. She talked about how application lifecycle management and DevOps are “messy.” I add that everything involving software is messy.
The creation of software is a new trade. It began in the days of vacuum tubes after World War Two and had grown into an activity employing a total of 11.5 professionals worldwide. The term bug came from a moth trapped in a box of the first vacuum tubes of the ENIAC computer. Today, bugs represent any of the defects or mistakes we perpetuate in code.
In the seventy-plus years since the beginning of professional programming, the activity has not fundamentally changed. Smart people work in isolation writing software code, and business people take it for granted that is works. The reality is software is one of the few activities which has not been taken over by automation. It is a creative and manual process. It is both an art and science.
Unlike construction which has a set rules for engineering and gravity software development lives in a strange world where the rules do not matter or change with each release. Deadlines are either fluid or hard as stone. People work late nights and early mornings to get the product out on time. Personal relationships suffer as support calls intrude on anniversary dinners and you are asked to release software on Sunday afternoons.
The people who do this work are smart and creative. Too often the demands of the business community force leaders to treat these people like machines which run on caffeine and pizza. The people who write software have children, significant others, and aging parents. They have felt and experience the entire range of human emotions. They are more than points of data in an Excel spreadsheet or a line item in a project plan.
It matters because software is one few activities in business which is immune to automation. It is manufactured by hand by these creative human beings. So software is “messy” because people under great pressure author it every day. Software development is “messy” because people make mistakes. It is “messy” because people have emotions which are hard to control. Finally, software development is “messy” because business people treat software professionals as interchangeable “staff” instead of skilled artisans.
I have spent numerous nights questioning my ability and worth thanks to the messy nature of software development. I am sure that other software professionals have done the same. This business is humbling. Angela and I agree; software development is messy because very human people are involved in every stage of its creation.
Until next time.
Monday, January 16, 2017
|A scrum master is a servant-leader|
The Elevator PitchWhen I am at social functions, networking events or family gatherings people ask me what I do for a living. I say scrum master and I get a puzzled look, and they ask me, “What kind of job is that?”
This is what I say.
“I build software and help developers and businesses develop software on time, on a budget, and with minimal bugs.”The person nods and smiles, once this sinks in and switches to a new topic.
The Scrum Master SyllabusWhen I describe the job of a scrum master, it often looks like a college syllabus.
A good scrum master is:
- An excellent communicator with individuals, small groups, and the organization.
- They understand the agile manifesto and principles of Agile and practice them every day.
- They are a trainer and coach making product owners, developers better and their job.
- They educate business leaders and stakeholders on how agile is making their business better.
- They are good listeners
- They have grace under pressure
- The can educate developers on TDD and SOLID development
- They are servant leaders
- They ship working software regularly.
- They make a god damn difference.
The bottom line.Being a scrum master is a hard job. It is also a calling of sorts closer to being a priest or pastor than a software professional. A good scrum master can reinforce your belief and faith in agile, or they can turn into a tool of oppression. I have never been into oppression, and I want to be someone who makes a difference. That is why I am a scrum master and why I have such high standards for the profession.
I hope this clears up any misunderstandings.
Until next time.
Monday, January 9, 2017
|Development is a lot like theater|
Business professionals use sports metaphors to describe what they do. I was never any good at sports, so I look business through the filter of music and performing arts. I think it is a more constructive way to look at the work. There is no scoreboard hanging over the cubicles in the office. Business leaders are often too busy to chart out plays, and there is no playoff season or championship. Business is an ongoing activity.
To me, the world of work resembles repertoire theater or a jazz orchestra. Each week the company needs to put on eight shows a week with a matinee on Sunday. The quality of the performance needs to be professional grade because people will not pay big money to see an elementary school recital. People get sick, and performers drop out but in show business terms, “The show must go on!” If the show does not go on then, people do not get paid. The cruel arithmetic of performing arts is that quality must be outstanding and that people must want to purchase your product. Otherwise, you starve.
So as a Scrum Master or Agile Coach you need to look at your job as if you were a theater director or the leader of a jazz band. Instead of being autocratic about the work, you will need to be collaborative. You will have to get to know the people you work with and understand them as people. Do they have children, are they single, is this their first job or do they have experience? Do they show up for work on time? Are they prepared? Can they improvise and can they handle the pressure? As coach and scrum master you need to know.
Once you understand the above, you can lay out the goals and mission of the team. Scrum is good about this. Each sprint has a beginning, middle, and end. The release of working software should is like a performance. When the curtain falls, the scrum master and the team decide how to do better job next time.
I am a big believer in the 1% principle. Each sprint, I want to improve the performance of the team by 1%. If I have thirteen iterations in a year, the team has increased its performance by 13%. Over a period of five years, that would be a 65% growth in efficiency. That is the kind of return which creates pay raises and promotions. So create small increments of improvement and meet them. Over time, you will be amazed by the results.
Finally, Agile and Scrum can not overcome a poor work ethic, incompetence, or stupidity. Being average is not sufficient. As a coach or Scrum Master, it is your job to help everyone become a better team member. People unwilling or unable to improve must go. It is best for the individual and the team. It is one of the hardest decisions to make. As someone laid off multiple times, I speak from experience. Each time I have lost a job I have bounced back and been a better developer. Nothing focuses the mind quite like unemployment.
So look at your role as a theater director. Get to know your people. Collaborate with your team and hold them accountable for small improvements over time. Finally, remove people from the team holding them back. Being a scrum master is not easy, but it is the most rewarding job you will ever do.
Until next time.
Monday, January 2, 2017
|After 2016, I think we |
all need a tall glass of wine
Looking back, it is clear that when I paid attention to technology and trends in the industry, my predictions were accurate. Apple computer did have a rough year with tax issues from the European Union and sales which dipped for the first time in years. Microsoft is growing its business with the Azure cloud services and a full embrace of Linux. It also has surprising sales of its Surface Pro 4. They are still going to founder in the phone market, but they are ruling in the desktop and enterprise realm. My prediction that the Scrum Alliance was going to have some growing pains came to fruition.
When I looked at politics in 2016, I was wrong. I predicted that election season would be a draw with the Democrats retaining the Presidency while the Republicans would keep the House of Representatives and lose the Senate. Instead, Democrats made slight gains in the House and Senate while losing the White House by the statistical margin of error in Wisconsin, Michigan, and Pennsylvania. President Trump's mandate is about 100,000 votes in three states which are .08% of the total votes cast. Please read this great article with lots of wonky footnotes on how this happened from Vox. Republicans have complete control of all three branches of government since 1929 in spite of their razor-thin margins of victory.
As a blogger and pundit, I need to take responsibility for when my predictions are correct and when I get them wrong. I also should learn from my mistakes and extrapolate what I need to do to make better predictions. Here is what I expect in the coming year.
Big Fight over Net Neutrality.There are already rumblings in the new Trump administration that net-neutrality is going to open to discussion. Changing the current net-neutrality rules will be a gold mine for cellular phone providers and cable companies; it will be bad for everyone else. The internet rose up in rebellion and forced members of Congress to drop support for a law which would have made pay to play access to the web law of the land. This time around the fight is not going to be in Congress but in the FCC and it is going to be harder because political appointees are going to be much less susceptible to public pressure.
Deregulation a-go-goMany Republicans have a love affair with Ayn Rand. Now that Republicans control all three branches of government prepare for a full wave of deregulation in technology and business. Overtime rules will be cut back. Financial regulations will be revoked, and a worker in this economy is going to have a more difficult time.
Those are the only two big predictions I have for the new year. The interesting thing about working in the technology world is that change is a big constant. If you are not paying attention, then you are bound to be surprised by something. I look forward to being along with you for the ride because 2017 is going to be a challenging year.
Until next time.