Home > Articles > Software Development & Management > Management: Lifecycle, Project, Team

Like this article? We recommend

Thirteen Organizational Structure Mistakes

Whatever the size of your software development organization, there are certain mistakes you need to avoid. Good organizational structure is a matter of management theory, science, and experience, not luck. Following are our "unlucky 13" mistakes:

  1. Combining software development and operations into a single organization.

    The job of operations is to keep applications up and running. The easiest way to do this is to never change anything. Combining development and operations into a single organization has the natural tendency to stifle innovation. Software development organizations should be separated from operations to allow new and modified applications to be developed as required to support the business needs of the company.

  2. Organizing software technology specialists by project.

    A modern day software development project requires a wide range of software specialists during different times in the software lifecycle. If you have a small organization with only one specialist and two projects, the specialist clearly needs to work on both projects, perhaps at different times. As your organization grows and develops more specialists, you still want to have specialists work across projects wherever and whenever they're most needed. But what happens if you assign technology specialists by project and each project ends up having a small number of specialists that must act as generalists, while doing the work of another specialist assigned to a different project? The result is that your organization as a whole cannot take advantage of all its specialists where they're most needed, and fails to take advantage of the synergies of being one integrated development organization.

  3. Organizing software technology specialists by application domain (financial, manufacturing, and so on).

    This results in the same problem as mistake 2 above. Given a fixed headcount, each application domain receives a smaller group of specialists who therefore are driven to become generalists. There is no room for software technology specialists who span across application domains, such as a GUI design specialist.

  4. Organizing software developers by delivery platform (Windows, UNIX, mainframe, and so on).

    Developers tend to develop a bias in favor of their assigned platform. As a result, there tends to be little or no innovation in new platforms (such as network computers) or cross-platform approaches (such as web-top computing or client/server systems).

  5. Separating software development and software maintenance groups.

    When you separate software development and software maintenance, you end up requiring the same types of software specialists for each group. This means you either have to double headcount in your organization for specialists or force one group to reduce specialization. In addition, it becomes harder to create incentives for software developers to do things right the first time, as they know another group will ultimately be responsible for fixing any mistakes. Such an organization also tends to develop two classes of software developers, leading to morale problems.

  6. Representing projects in the formal organizational structure instead of defining project teams that cut across organizational boundaries.

    This strategy leads to reorganization whenever a major project ends. As a result, software developers spend an inordinate amount of time looking for their next job or find unnecessary reasons to prolong their existing projects.

  7. Organizing software developers into long-term and short-term development groups.

    Again, this type of organization requires two of every software specialist and builds unnecessary competition between the two groups. In addition, this organization often encourages point solutions that may be quicker to implement but cost more in the long term, because of higher maintenance costs and difficulties in integrating with enterprise-wide applications.

  8. Designing organizations that need "super-developers" to succeed.

    In today's complex software development environments, no single developer can be a specialist in all fields. The organization should allow developers to become true specialists in a single field and reward them accordingly. The workload should also be managed to allow software developers to lead balanced lives. No one can work 18 hours a day forever and be expected to maintain his or her work quality and personal satisfaction.

  9. Designing organizations that tolerate underachievers.

    This is the corollary of mistake 8. A healthy organization employs everyone's complete range of talents to the fullest. Software developers who are allowed to underachieve will become bored with their work, which will only lead to poorer quality and further poor performance.

  10. Designing organizations that reward empire building.

    Organizational structures should eliminate all incentives for empire building. This means providing equal career paths for both senior-level software engineers and software development managers. Along the same lines, career paths should be provided both for software generalists and software specialists, as both are needed in a healthy organization.

  11. Setting organizational goals that compete against each other for customer satisfaction.

    Customer satisfaction should be the ultimate goal of all software development organizations. One organization should not have goals whose achievement negatively affects the customer satisfaction of another organization. For instance, if two development groups are working on applications for the same customer that must ultimately be integrated together, one organization should not be rewarded for meeting its timelines if this was only done at the expense of creating a more difficult integration task for the second group.

  12. Organizing around individuals instead of personality types.

    Every experienced software development manager recognizes the importance of matching a developer's job to his or her personality; however, even in the most stable of organizations, individuals come and go. You shouldn't design organizations around individual personalities. Instead, organize them around more general personality types. This allows the organization to recognize the value of individual diversity without having to reorganize every time someone comes and goes.

  13. Mandating organizational changes from the top down.

    All software development organizations eventually must change to adopt to new business models, technologies, or clients. However, mandating a structural change has little or no effect if it's not accompanied by cultural and process changes. The best way to assure successful change is to manage it via a participative process in which all developers are given a chance to affect the final outcome.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020