Posts

4 Top Qualities of a Software Development Firm

When selecting a software development firm to work on your custom software project you want to select the best option available, right? They all seem the same from the surface, but they aren’t. It’s not difficult to discern those that will provide a much greater chance of software project success.
Here are some qualities and experience to look for. If you don’t find most if not all of these, then you might want to consider looking elsewhere for a top software development firm.
  1. Listen and understand without selling
    Any project, no matter the type, starts of with the potential vendor listening and understanding…not talking and selling. Does your prospective software development vendor listen and ask questions in the first meetings? Do they truly understand the situation you’re in?
  2. Can say No
    Can the software firm you’re talking with say “No” to a project because it’s not a best fit? Are they so desperate to get the project that they’re willing to do anything to get it, including massive discounts, ruining other client projects to focus on your project, willing to take on the project even though it’s completely out of their capabilities and focus? If it’s not a project they can and should do, they should be able to say, “No, this project isn’t for us. Thank you for talking with us! Maybe you should talk to this other company.”
  3. True focus of the project
    Do they ask you questions like, “What really drives your company?”, “What is the main goal of your company or department at the end of the month or year?”, “What do you really care about?” If they ask those types of questions there’s a good chance they have the right focus. You can tell them what features you want, and they’ll suggest how the project should go. But they should also be thinking about how the project will help you accomplish what matters, what you care about in the company. If the project isn’t helping with that focus, then is the project really worth doing?
  4. Disciplined approach to specifications
    What do the specifications look like for the project your software vendor is about to tackle with you? Or, what do the specs look like for past projects they’ve worked on?
If they say, “We don’t need specs.”, run for the hills. If their specs don’t have a low level of detail for what needs to be created, run for the hills. If they can’t show you a sample of a spec, run for the hills (they really should have at least one spec or part of a spec they can show you with appropriate redacted info for the other client’s confidentiality.
Keep in mind there are different types and styles of requirements specification…even Agile projects have spec docs…they’re simply in a different format (e.g., epics, stories, etc.).
More top qualities of top custom software development firms to come in the future.