Skip to main content

Constraints are Killers for IT Projects

After working on information technology projects for many years, I'm here to declare what may be obvious -- it's not the technology that's the problem, it's the constraints.

Software and hardware technology keeps improving, and offers many innovations that can dramatically change how government and business work.  But the constraints remain intractable.

Project management literature is rich in discussions on working with constraints, such as the tradeoffs between schedule, cost, and scope.  The implicit assumption is that all the parties working on a project are rational players and motivated to achieve the stated project goal.  I have experienced other constraints that are not usually discussed and which are even more hazardous to the health of a project:

1. Communications constraints.  A great way to make a project fail is to isolate the project team from stakeholders and prevent communication with people who are most knowledgeable about system requirements.

2. Political constraints.  This is a huge category, but encompasses the extra time and grief of dealing with competing groups within an organization who assert power over a project.  The project team cannot tell whose decisions are final or whose priorities really are most important.

3. Hostile players.  Surprising often, some project participants openly or secretly want your project to fail.  Deflecting their sabotage or co-opting them into the success of the project is time consuming and emotionally draining.

4. Pennywise pound-foolishness.  Sometimes artificial constraints compel projects to spend much more than necessary to solve simple problems.   I have witnessed organizations that spend $1000,000 on costly software optimizations rather than spend $1,000 on a memory upgrade to achieve the same performance improvement more quickly and with less risk. This can happen when different groups manage infrastructure and cannot work together, or when government standards prevent software or hardware upgrades.

5. Project management navel gazing. Ironically, project management itself can create problems which project management activities become a distraction from the real project goals.  Obsession with documentation artifacts at the expense of project progress doesn't usually turn out well.  Many failed projects are well documented.

6. Fragmented, competing project teams.  A final, avoidable constraint is to divide a project team and encourage fighting among the members.  The classic approach in government contracts is to carve the project into pieces and hand each piece to a different contractor.  Without a stake in the overall success of a project, these sub-teams are tempted to avoid responsibility and quick to assign blame to competing contractors.

I recently met with some of our consultants to discuss their career goals and how we can seek opportunities for growth.  One of them said he was tired of working on projects that were constrained in terms of time, technology, cost or resources. Ah, the nirvana of the project without constraints.

Constraints play positive effects as well by sharpening priorities and helping the project team work together to achieve a challenging goals.  It's hard for me to imagine a successful project without a schedule constraint, for instance.  

Sadly, there is no such thing as a project without constraints.  If you can reduce the unnecessary constraints and work as a team to manage the unavoidable constraints, you are more likely to succeed.



Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

Updated 8/15/2022 To understand Microsoft Dynamics 365 (formerly Dynamics CRM) and Power Apps, you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises.  These concepts also apply to Power Apps.  The main difference is that with Power Apps you are not starting with a Microsoft app but more of a blank canvas for your custom apps.  This post introduces some key terms and how these concepts are important for planning your implementation. While Dynamics 365 is still available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds in several countries. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uni

Microsoft Dynamics 365 Solutions for Education

Student Portal by James Townsend For over three years, Microsoft has released solution accelerators based on Dynamics 365 for industries including healthcare, automotive, manufacturing, finance, nonprofits and education.  Each year we are seeing new solutions and updates to solutions based on Dynamics 365, Power Apps and the Common Data Model. In August 2021 Microsoft released the Higher Education component in the latest version of the  Dynamics 365 Education Accelerator v3.2.3.10 . Here are some highlights from the Higher Ed solution A student portal  An advisor dashboard  A business partner dashboard for events, hackathons, internships, scholarships, and grants. The Accomplishment extension tracking student work outside courses. The Grants phone app that allows research faculty to keep track of applications and approvals.  Rich reporting on students applying for internships, grants, and scholarships. System views for tables including students, faculty, extracurricular activities, pr

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises