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.

Steve Jost Profile Picture
Share
Contributors Chris Hodge David Brown

The needs of your organization may necessitate erring on one side of that balance or the other.

  • If your organization is new to software and systems development, you may value more immediacy and short-term projects. The faster you can turn good wins around in the eyes of your customers, the more you can start to scale those solutions for longer periods of time.
  • If your Systems Development team already has people at your company acting as champions, you will gain the ability to start looking forward one or two years with your projects. Additionally, you will have gained enough trust to be finding places where your skills will lead the company, rather than receiving tasks from others.

When scalability and long-term projects become more regular, remain cautious to scope creep and business condition changes. Just as in software, a lot can change in the business landscape in two years.

This is Part 8 of an 18-Part Series


Topics Covered in the Series Include:

  • Clarification
  • Developers
  • Best Fit
  • Outsourcing
  • Time & Money

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 - 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.
Building a Systems Development Team - Developers
A Software Developer is just one of the many roles that make up the systems development team.