Building a Systems Development Team - Time & Money

Many software projects are over budget, late, and hard to implement.

Steve Jost Profile Picture
Share
Contributors Chris Hodge David Brown

These issues generally boil down to the same root causes, going into a software project with incorrect assumptions, lack of communication within the project, and poor communication of outcomes to the rest of the business. One of the major evils in any project is scope creep.

Construction firms will understand the idea of scope creep, but mitigating it in the context of software development will be very different to what they're used to. In building, the underlying technology generally does not change throughout the life of the project. However, in software, the tools you use when you start a project may be outdated by the time you finish a project.

Lastly, because of the relative newness of the software development field, many supervisory positions don't have the intuitive knowledge to effectively oversee a software project.

This is Part 6 of an 18-Part Series


Topics Covered in the Series Include:

  • Management
  • Balance
  • Clarification
  • Workflow
  • Industry

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


More from Steve Jost
Building a Systems Development Team - Balance
Striking a balance between immediacy and scalability is a constant decision with Systems Development and will be ever-changing in most organizations. The needs of your organization may necessitate erring on one side of that balance or the other.
Building a Systems Development Team - Support
The need for support, training, and maintenance of developed systems should not be underestimated.
Building a Systems Development Team - Risk
Minimizing the business risk of a developer leaving. The better you are able to make your company a great place to work (culture & communication), the easier it will be to retain your top talented team members.