29
Fri, Nov
0 New Articles

Debunking Those Change-Control Myths

Change Management
Typography
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

Every IT shop has some sort of change-management system. And it's often more a burden than a help. Why? Because of a number of change management myths that we hold near and dear.

 

The single most unheeded dictum, which seems to come from every successful entrepreneur-turned-billionaire, is to not be afraid of making mistakes. In fact, many people proudly declare that mistakes are the only way you make progress, and they attribute much of their success to their ability to make mistakes. Interestingly enough, this never seems to have worked out for me, but they're the rich ones, so they must know.

 

But ours is a world of caution, and it's one company in 10,000 that truly does not consider mistakes a cardinal sin. Careers are shipwrecked on mistakes. In many companies, management never remembers your victories, only the goofs.

 

Because of this deeply ingrained mindset, change control has evolved from the coder's helper to the coder's nightmare, and more than one company has set up change-control systems that double or triple the time it takes to get something "to market" without really providing any additional safety.

 

Here are just a few of the change-management myths we have embraced that have helped it grow from a tool to a prison.

 

Every User's Thoughts Should be Noted

Great writers fill notebooks with passing thoughts and bits of inspiration that come to them at odd moments, and someday some of those thoughts may become great pieces of literature. Or at least quick reads that net their authors a hefty royalty.

 

But users are not writers. Most passing thoughts and bits of inspiration that come to users (both real users and IT people) should be ignored. Yep, just forgotten about.

 

If the thought comes multiple times, maybe it's worth following up on, but most of the things we think about are just not worth further scrutiny. They may be cute and all, but they provide very little real business impact.

 

Unfortunately, there's a real belief in many companies that by allowing users to create their own requests and adding them to the queue, you are empowering those users and providing an enhanced level of service. Whatever.

 

The downside to this freedom, however, is that you end up with a huge queue. Sure, you can put a management review in there, but how many managers really want to tell their people that the idea they had was stupid? In this kind of environment, no matter how hard IT is working, it appears they're making no progress because the influx of half-thought-out ideas more than offsets those that are put into place.

 

In addition, if something sits in a queue for some period of time, maybe two or three years, is it really relevant for the business anymore? Try to find someone who says their business is not continually evolving. So if that's true, how relevant to today's needs is a requirement from three years ago?

 

Plus, even though you're theoretically providing a service to your users, if one of them puts in a suggestion and doesn't see any results for two years, they really aren't going to consider that "service." Sometimes, it's better to say no right away than say, "Oh, yeah, we'll get to it" month after month.

 

Finally, because you let things that aren't fully researched get into a queue, you get down the road and nobody really remembers what that was all about. The person who put it in may be gone or may not remember. So what do you do then? Close it? Or spend three or four people's time trying to figure out what that item was? Either way, it's a lot of overhead.

 

The More People Who Look at a Change, the Safer It Will Be

This is a big one. If we want to avoid code problems in production, don't just leave it up to the coder; have someone else look at it, probably a whole bunch of people. Have the users test it (I agree with that), have a user manager approve it, have someone independent in IT look at it, have IT management look at it, create a special final test group to look at it…. There's no limit to what you can do here to "protect" yourself.

 

First, let's look at management. Managers should know what's going on, but the idea of them looking at something detailed and spotting a problem is, for most companies, wildly optimistic. Managers are busy managing, whatever that means. And I believe managers can be either detailed or overview-oriented. I don't think most people do both very well. So what you get from management (both user and IT) is a quick look and a pass. But it does effectively add anywhere from a couple of hours to a week to the development cycle.

 

Second, I don't believe in special test groups. The only person who can really understand the change and test it properly is the coder. I strongly believe in empowering the coder to have the responsibility of ensuring that the change being made is a good one. Yes, for some projects that's going to be a big job, but the "coder" could always be a team: one person to do the SQL scripts, one to do the RPG changes, and one to do the final testing (because some people are better testers than others). I just don't like the idea of dropping an enhancement on another group of people and saying, "Here, test this." Besides, people who just test things day after day tend to snap more often than normal people, which is a problem because they always seem to be big into firearms or medieval weaponry.

 

Every time you pass something off to a different group, you waste time. And you force people to look at things that aren't what they were looking at a few minutes ago. I think there's real value in keeping people focused.

 

This doesn't mean that you shouldn't communicate about what you're doing. Team meetings in which everyone understands what each other is working on and the impact it will have on things are still necessary. But they should be short, more like Scrum meetings, not the endless meetings we all know that go on with one or two people endlessly dissecting the same thing over and over again. Oh, yeah, we know who you are. We talk continually today about training to teach people new skills. How about training to teach people how to stick to the point, say what they have to say, and shut up about it already?

 

Proper Change Management Will Prevent Production Problems

Yes, and fairy dust will cause pigs to fly and people like myself to become powerful warriors.

 

We live in a physical, probabilistic world, and despite the fact that what our society wants most of all is to eliminate all bad surprises, things are going to happen that we didn't count on. Accept it and move on.

 

Putting in a dozen firebreaks doesn't prevent problems; it just lengthens the time it takes us to get solutions out into production. Besides, traditional problems are the least of our worries. Poor design and crappy code cause most of the user unhappiness and, down the road, maintenance issues, but very little is done about that because it might mean stepping on someone's toes. (And don't decide to add a design review and a code review to your change process. It won't do any good.)

 

What does do some good is accountability. Making the primary coder the one responsible for the enhancement is the best way to ensure quality. Involve a team if necessary, but everyone on the team should know what their responsibility is and know that they need to be accountable for it. Most of the time, people will respond favorably to that.

 

It's Not That I Hate Change Mangaement…Or Do I?

All in all, it doesn't seem like I'm a big fan of change control as most of us know it today. I'm not. But I am a big fan of producing quality code that meets user needs.

 

So far, I've talked about things that I think aren't true. But what do I think is true? Ah, for that, you're going to have to stay tuned. Catch me next month, when I talk about what I think change management should look like. I know; I'm excited too.

 

David Shirey

David Shirey is president of Shirey Consulting Services, providing technical and business consulting services for the IBM i world. Among the services provided are IBM i technical support, including application design and programming services, ERP installation and support, and EDI setup and maintenance. With experience in a wide range of industries (food and beverage to electronics to hard manufacturing to drugs--the legal kind--to medical devices to fulfillment houses) and a wide range of business sizes served (from very large, like Fresh Express, to much smaller, like Labconco), SCS has the knowledge and experience to assist with your technical or business issues. You may contact Dave by email at This email address is being protected from spambots. You need JavaScript enabled to view it. or by phone at (616) 304-2466.


MC Press books written by David Shirey available now on the MC Press Bookstore.

21st Century RPG: /Free, ILE, and MVC 21st Century RPG: /Free, ILE, and MVC
Boost your productivity, modernize your applications, and upgrade your skills with these powerful coding methods.
List Price $69.95

Now On Sale

BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

Support MC Press Online

$

Book Reviews

Resource Center

  • SB Profound WC 5536 Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. You can find Part 1 here. In Part 2 of our free Node.js Webinar Series, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Brian will briefly discuss the different tools available, and demonstrate his preferred setup for Node development on IBM i or any platform. Attend this webinar to learn:

  • SB Profound WP 5539More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.

  • SB HelpSystems ROBOT Generic IBM announced the E1080 servers using the latest Power10 processor in September 2021. The most powerful processor from IBM to date, Power10 is designed to handle the demands of doing business in today’s high-tech atmosphere, including running cloud applications, supporting big data, and managing AI workloads. But what does Power10 mean for your data center? In this recorded webinar, IBMers Dan Sundt and Dylan Boday join IBM Power Champion Tom Huntington for a discussion on why Power10 technology is the right strategic investment if you run IBM i, AIX, or Linux. In this action-packed hour, Tom will share trends from the IBM i and AIX user communities while Dan and Dylan dive into the tech specs for key hardware, including:

  • Magic MarkTRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now!  Request Now.

  • SB HelpSystems ROBOT GenericForms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.

  • SB HelpSystems ROBOT GenericIT security is a top priority for businesses around the world, but most IBM i pros don’t know where to begin—and most cybersecurity experts don’t know IBM i. In this session, Robin Tatam explores the business impact of lax IBM i security, the top vulnerabilities putting IBM i at risk, and the steps you can take to protect your organization. If you’re looking to avoid unexpected downtime or corrupted data, you don’t want to miss this session.

  • SB HelpSystems ROBOT GenericCan you trust all of your users all of the time? A typical end user receives 16 malicious emails each month, but only 17 percent of these phishing campaigns are reported to IT. Once an attack is underway, most organizations won’t discover the breach until six months later. A staggering amount of damage can occur in that time. Despite these risks, 93 percent of organizations are leaving their IBM i systems vulnerable to cybercrime. In this on-demand webinar, IBM i security experts Robin Tatam and Sandi Moore will reveal:

  • FORTRA Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:

  • FORTRAManaging messages on your IBM i can be more than a full-time job if you have to do it manually. Messages need a response and resources must be monitored—often over multiple systems and across platforms. How can you be sure you won’t miss important system events? Automate your message center with the Robot Message Management Solution. Key features include:

  • FORTRAThe thought of printing, distributing, and storing iSeries reports manually may reduce you to tears. Paper and labor costs associated with report generation can spiral out of control. Mountains of paper threaten to swamp your files. Robot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing. Manage your reports with the Robot Report Management Solution. Key features include:

  • FORTRAFor over 30 years, Robot has been a leader in systems management for IBM i. With batch job creation and scheduling at its core, the Robot Job Scheduling Solution reduces the opportunity for human error and helps you maintain service levels, automating even the biggest, most complex runbooks. Manage your job schedule with the Robot Job Scheduling Solution. Key features include:

  • LANSA Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.

  • LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed. Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

  • LANSASupply Chain is becoming increasingly complex and unpredictable. From raw materials for manufacturing to food supply chains, the journey from source to production to delivery to consumers is marred with inefficiencies, manual processes, shortages, recalls, counterfeits, and scandals. In this webinar, we discuss how:

  • The MC Resource Centers bring you the widest selection of white papers, trial software, and on-demand webcasts for you to choose from. >> Review the list of White Papers, Trial Software or On-Demand Webcast at the MC Press Resource Center. >> Add the items to yru Cart and complet he checkout process and submit

  • Profound Logic Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.

  • SB Profound WC 5536Join us for this hour-long webcast that will explore:

  • Fortra IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn: