What business people need to know about software development

Claiming ignorance of information technology in this day and age is just like claiming ignorance of accounting.  Every manager must have a basic knowledge of IT just like they must be able to read a balance sheet.  Determining what, exactly, every manager must know is difficult, though.  Like most things, it depends on the context.  I'll start with what business stakeholders need to know about software development, in large part because this is my specialty.

Basic Terminology:
User Interface - This is the term for the way in which the software user interacts with the application
Database - This is software that stores the data in most scenarios
Server - This is a computer, usually with a large amount of memory, that hosts the software or database
Hardware - This refers to the physical components of a computer
RAM - Think of this like short-term memory in humans: it stores information that might be needed in a few minutes, but does not hold information in the long-term
Refactoring - The process of rewriting working code to make it more readable
Data - Another name for "information", though "data" is plural

Development Process:
Writing software does not follow a predictable method or process.  If it did, we could write software that could write software for us and save everyone a lot of time and money.  (Most good programmers will do that when and where it is appropriate.)  Because software writing is a highly creative and unpredictable process, nailing down solid estimates can be tough.  If you try to force your developers to stick to their original time and cost estimates, you will likely create a contentious atmosphere which will get in everyone's way when trying to get work done.  Instead be flexible to estimate changes.  If it looks like a task or component is taking too long to complete, decide if it is worth completing after all.  If so, keep in mind that the next estimate very well might be too large and you'll be even in the long run.  If not, it is better to stop a time-consuming task early to avoid throwing good money after bad.

Early detection of problems is important
If you notice something strange in your application, especially if your data looks wrong or missing, find out what the cause is soon.  Chances are that there's something wrong with your user interface and your data is fine, but if there's something in the application that's corrupting the data the sooner you can find the problem the easier it can be corrected.  Lost data can be recovered from backups, but most companies only keep backups for a certain period of time.

Early detection is also important for problems like software slowness.  If your software is slow, it is not likely going to speed up on its own, and will likely get worse over time.  Fixing the problem early before complaints start coming in will save both you and your developer time and frustration.


Know what will change in your business requirements...and what won't
Many developers would disagree with me on this one, but I think it's important to communicate which of your business requirements will never change and which ones will certainly change over time.  For example, if you have an e-commerce site that sells shirts, you might expect to add colors to your offerings, but you will not likely add sizes.  The reason for this is that most developers will program non-changing requirements differently than ones that will change often.  The non-changing requirements can be coded in such a way to make it easier and faster to write the first time, but harder to change going forward.  The opposite is true for the changing requirements.  This concept isn't critical, but it is something to keep in mind.


When problems arise, adding more bodies is probably not the solution
If a software project falls behind schedule, resist the urge to request additional resources to get it done.  Why?  Since, as I mentioned before, software writing is a relatively complex process, it will take time to get new resources up-to-speed on the specific requirements of your project.  This not only means that these new resources will not be as effective as your current ones, but your current resources will be less effective than they were as they help bring the new resources into the project.  Your best bet is probably to adjust your expected finish dates.  If that is not possible, then adjusting the number of features to be added should be the next option.

It was working before....

Refactoring is an important part of the software development process.  Adding features adds code, and unless you change existing code so everything makes sense to the developer you will eventually end up with a tangled, unmaintainable mess, to put it mildly.  Therefore, most good developers will spend some time rewriting code to prevent this from happening.  Every time this happens, the developer runs the risk of breaking something that was working before.  There are ways of mitigating that risk, such as writing and running unit tests, but the risk cannot be completely eliminated.  If you are testing changes made to your software, try to test areas that might be affected.  Also, if you get complaints right after changes were applied about functionality that was working before, take them as seriously as any other.

Know the general limitations of your approach
I am not suggesting that you become a programming expert by any means, but you should be aware of the limitations of the software delivery method you choose.  For instance, applications for a hand-held device might be difficult to move over to other brands of devices.  Desktop applications are hard to update with bug fixes or changes.  Web programming is limited by the fact that most of the processing must be done by the server.  (Going into more detail would require another blog post on its own.)  Being aware of the limitations will help you ask for features that are appropriate for your medium, and will make the conversations you have with your developers about changing features much more productive.

Keep in mind that you are a team
Finally, keep in mind that most programmers, no matter what their background, experience, or skill level, want to write good software.  Their focus may be different (most software developers I know will often over-emphasize quality code creation at the expense of the software as a whole), but in the end they want the same thing.  They want the software to be successful as much as you do.  From what I've seen, many of the problems between business and IT could be mitigated if everyone remembered that the end goal for everyone else is the same.  Build trust, and good things should follow.

Using outsourcing effectively

There are plenty of stories available online about outsourcing projects that failed to live up to expectations.  Yet I see very few explanations as to why such failures occur, and more importantly, how to prevent a similar failure from happening again.  While I'll be the first to admit I don't have much experience with outsourced projects on the scale that usually make these types of headlines, I'd like to offer some advice on how to outsource effectively, from the perspective of a consultant who carries out outsourced work.

Before I get too far into that, though, I'd like to discuss the difference between outsourcing and off-shoring.  Outsourcing is the process of moving one or more business functions to an outside company, likely a specialist in that particular function.  Off-shoring is the process of moving a particular business function to another location outside of your current company, typically to a country with less expensive labor.  You can have one without the other, or do both at the same time.  I will stick to outsourcing for now and leave off-shoring for another time.

If you’re outsourcing the development of a computer application, you will help both yourself and your vendor if you start by getting as good an idea as possible of what you want out of your application.  Most vendors should expect that you will change your mind about some of the application's functionality during the course of making the software; unfortunately such "scope creep" is an expected part of building software.  However, requirements that are too vague will make it extremely difficult for your vendor to build what you want.  If you know you will have trouble making requirements, hire someone who will help you discover and articulate them.

It is also important to determine where your priorities lie.  Everyone wants their application done quickly, at a low cost, and with high quality.  To make matters even more unclear, "quality" can take on different meanings to different people.  Application speed, ease of use, application up-time, number of bugs, scalability (i.e. the ability for the application to grow with few growing pains), ease to add features, secureness of the application, etc., can all contribute to the perception of "quality".  Unfortunately, many of these are conflicting goals.  Making an application execute very quickly takes longer to develop and is more expensive to build, just like adding a large number features can make your application harder to maintain.  You and your vendor should be on the same page as to where compromises must be made.  Be sure to communicate these goals and make sure your vendor follows them.  Communication up front along these lines can save a lot of headaches and discussion when the bill arrives.

One thing that will help you and your vendor manage your project is to break your large projects into smaller, yet still useful, chunks.  More often than not, once a client starts working with their application, they discover that some of the ideas generated don't work as well in the application as they do in the planning stages.  If you try to develop too much at once, problems are identified late, and the later a problem is found, the more expensive it is to fix.  If you start small, you will see the results of your work sooner, allowing you and your vendor to adapt to each other's styles.  This will allow each of you to communicate more effectively.

You may want to consider billing your projects on a time and materials basis only.  Fixed bid projects are tougher for both parties.  The outsourcing company very often tries to put in as many features as possible in an effort to get the most for their money.  This can cause the company to lose focus on their core needs from the software.  The vendor must protect its interests, and therefore cannot be very open or cooperative to change requests.  If a project is billed on time and materials, a company can focus on which features/changes are most important to them, and the outsourcer can focus on how to most efficiently fill these requests.  In other words, the discussion turns from extracting the most value possible from the other company in a fixed-bid situation to a more cooperative effort to build the best software possible in a time and materials situation.

Also, be sure to stay active in your project.  You may be tempted to give your vendor all the information you think he or she needs and then let him or her finish the project, but that's usually a recipe for failure.  Review any documentation, samples, code, beta versions, etc., as thoroughly as possible.  Your vendor should have tried to understand your needs, but something inevitably gets lost in translation.  Be sure to voice any concerns early before they become problems.  The sooner you find errors or omissions, the cheaper and easier it is to fix them.

Most of these suggestions come down to improving communication.  Understanding your project and understanding your priorities help you give clearer directions to your vendor as to what you want from your project.  Breaking down your project into smaller, but still useful, chunks helps you and your vendor communicate requirements in a meaningful way.  Billing your project on a time and materials basis help you and your vendor communicate about what the project needs, rather than about unnecessary information.  Keeping communication clear, open, and frequent will help increase the odds of success in any of your outsourced projects.

Competing Through I.T.

One of the hot topics in business today is the tense relationship between business and I.T.  Of the many articles that I've read, very few try to thoroughly describe how the severity of the problem can differ from company to company, or how the solutions can vary because of those differences.  Nearly 25 years ago, Steven Wheelwright and Robert Hayes published an article in the Harvard Business Review called "Competing Through Manufacturing," which described the different levels in which a manufacturing arm of an organization could be integrated into the organization as a whole, as well as the benefits and consequences of each integration level.  Their terminology could easily be extended to the integration of an I.T. department.   Here are their original four "stages," only slightly adapted for I.T.:

Stage 1: Minimize Information Technology's Negative Potential

An Information Technology department whose role is in Stage 1 would be characterized by a lack of trust between I.T. and the rest of the business.  In Stage 1, a business feels the need to control as many aspects of I.T. as possible to avoid possible negative consequences of mistakes or misunderstandings.  A large portion of the strategic management and implementation regarding technology is left to consultants.  Internal research is discouraged because it leads to uncertainty, which in turn could lead to problems down the road.  The feeling is that anyone could manage I.T., which leads to inappropriate people chosen for leadership positions within the department.  For companies whose major focus is I.T., internal applications aren't given nearly the attention that the customer-facing ones receive.

Stage 2: Achieve Parity with Competitors

An Information Technology department whose role is in Stage 2 would be characterized by the desire to expand I.T. only to keep up with competitors.  Industry best practices are followed regarding programming languages, hardware, purchased software, etc.  Investments in the department usually come in the form of investing in hardware and software, rather than investing in the people or in the process.  Unlike Stage 1 organizations, Stage 2 organizations often look internally for leadership in IT, though leadership still sometimes comes from outside the department.  Improvements are often only made when shortcomings become obvious.

Stage 3: Provide Credible Support to the Business Strategy

Stage 3 Information Technology departments would be expected to actively support and strengthen the company's competitive position.  Stage 3 I.T. departments would make sure that all of their decisions are consistent with the organization's overall strategy and that these decisions are communicated effectively to all I.T. personnel.  These departments would be aware of long-term trends in the marketplace and would be actively considering ways to use these trends to their advantage.  Stage 3 I.T. companies often stay in Stage 3 for short periods of time to implement one or two large changes then revert back to Stage 2.  As opposed to Stage 2 companies, however, Stage 3 companies will often pursue improvements for the sake of improvement, rather than based on some external force. 

Stage 4: Pursue an I.T.-Base Competitive Advantage

A company reaches Stage 4 when the competitive strategy of that company is reliant on I.T.'s ability to implement the strategy.  In other words, I.T. is just as (but not more) important as other departments, and successful projects are largely a collaboration among departments.  What sets Stage 4 I.T. departments apart from other stages is the expectation by other departments that I.T. can contribute ideas and strategies central to the business as a whole.  Wheelwright and Hayes mention briefly that some Stage 4 firms take this idea too far – a firm that promotes one department at the expense of others is doing harm, regardless of which department is being favored.

If I could be able to state with certainty how a company could bring its I.T. department from Stage 1 to Stage 4, I would probably be making seven figures as a business consultant.  Clearly, I can't do that (yet).  But by identifying some terminology, I should be able to communicate some ideas much more easily in future posts.  For example, in a previous post I wrote about improving the job interview process.  However, I hope it's clear that a Stage 1 organization would have different needs than one in Stage 4.  A Stage 1 organization may have driven away its qualified workers, leaving only workers unable to find jobs elsewhere. Its hiring efforts would not only need to focus on finding good programmers, but also on finding programmers who would be willing to endure, and help turn around, a Stage 1 environment.  Since a Stage 4 company's I.T. department is involved in the overall strategy of a business, its management would need to focus its hiring efforts on finding personnel who can understand the business as well as the technology.