This paper explores the reasons why custom software projects fail or succeed. It provides a list of attributes and capabilities to look for when evaluating potential software suppliers, to increase your odds for success in your project.

While the custom software projects do involve risks, the paper shows how these can be reduced to an acceptable level, provided the software developer follows a rigorous development process.

This paper examines the processes used to develop custom software systems. It explores the various types of development processes, cites their pros and cons for specific applications.

The paper concludes with an exploration of the concept of Continuous Process Improvements and its role within the Software Maturity Framework developed by Watts Humphreys at Carnegie Mellon University.

This paper provides an overview of the Konverge Collaborative Software Development Process, or KCP. We describe the phases a typical Konverge custom software project goes through on its way from an idea, or a Request for Proposal, to a fully functioning system installed and operating in your organization.

We’re proud of KCP – it’s earned its stripes in the field – please see our client list and references for more. But perhaps it’s most powerful aspect is how it brings you and your team into the process to ensure that the right system is built. After all, no matter how good we are at developing software, if the resulting system doesn’t do what you need it to do, it’s useless.