Building a Systems Development Team - Mistakes

While there are many benefits to contractors starting their own internal Systems Development teams, there are also many risks.

Steve Jost Profile Picture
Share
Contributors Chris Hodge Profile PictureChris Hodge David Brown Profile PictureDavid Brown
  • First of all, it wasn’t the best fit as previously discussed. 
  • Underestimating the cultural mismatch between developers and other team members that were brought in from outside the construction industry.
  • Not funding the development team properly, including funding of individual roles. Just like the field, many times the cheapest labor is not the most productive per dollar.
  • Not putting the right amount of resources into the management of the team. Managing software engineers and developers is very different than managing a field workforce or project managers. A hands-off “hope” style or a micromanaging style are both typical mistakes.
  • Not sequencing the projects properly, so a return is seen for the investment across the organization.
  • Over-building when a “Minimum Viable Product” or MVP is what you really need. This will impact returns as much as not sequencing properly.
  • Not planning for and managing the roll-out, training, continuous improvement, and support aspects of an internally developed tool.

This is Part 16 of an 18-Part Series


Topics Covered in the Series Include:

  • Workflow
  • Management
  • Balance
  • Risk
  • Outsourcing

All relationships start with a simple conversation. Let’s schedule some time to talk about your specific challenges and opportunities.


Building a Systems Development Team - Mistakes
Construction technology innovation is accelerating and the contractors that learn how to effectively integrate technology into every aspect of their business will dominate tomorrow. ...

Building a Systems Development Team - Mistakes
Construction technology innovation is accelerating and the contractors that learn how to effectively integrate technology into every aspect of their business will dominate tomorrow. ...

Agile Project Management vs. Critical Path Method
The Critical Path Method of project management is very commonly used on construction projects. CPM does not work as well in situations where there are significant “Known-Unknowns” about the plan CPM really breaks down when there are “Unknown-Unknowns”:
Construction Benchmarks, Trends, Forecasts, and Predictions
Two of the most highly leveraged choices that leaders of contractors make are about market strategy and major resource allocations. Robust information systems about the external market are a critical part of this decision-making process.
CMAR vs DBB Project Delivery Comparison
To see how the Construction Management at Risk (CMAR) delivery model compares to Design-Bid-Build (DBB), you have to look at the architectural phases of the project starting with programming.