<div>
Thanks very much, developmentguru. &nbsp;I really appreciate the time and thought. &nbsp;Why not submit it, as-is, to one of the industry magazines? &nbsp;I am certain this situation is relatively common and would think such an article would prove valuable to many readers.
</div>


Thanks very much, developmentguru.  I really appreciate the time and thought.  Why not submit it, as-is, to one of the industry magazines?  I am certain this situation is relatively common and would think such an article would prove valuable to many readers.

<div>
<div class="content wysiwyg-content">
My company recently acquired a rather complex software product created by a single developer for a limited market. (It happens to be an MRP system, but not sure if that is relevant.) We are trying to get a handle on the functionality, code and database (none of which are well-documented) so that bug fixes and further development can be taken over by a larger team -- and get it ready for larger-scale distribution. The original developer is still available, but only on a limited basis. <br />
<br />
Do you know of an article or book that addresses best practices or suggestions for a task such as this? &nbsp;Thanks.
</div>
</div>


My company recently acquired a rather complex software product created by a single developer for a limited market. (It happens to be an MRP system, but not sure if that is relevant.) We are trying to get a handle on the functionality, code and database (none of which are well-documented) so that bug fixes and further development can be taken over by a larger team -- and get it ready for larger-scale distribution. The original developer is still available, but only on a limited basis. 

Do you know of an article or book that addresses best practices or suggestions for a task such as this?  Thanks.

Need article on moving development of acquired software from single developer to team.

Project management is the discipline of carefully projecting or planning, organizing, motivating and controlling resources to achieve specific goals and meet specific success criteria. A project is a temporary endeavor designed to produce a unique product, service or result with a defined beginning and end (usually time-constrained, and often constrained by funding or deliverables) undertaken to meet unique goals and objectives, typically to bring about beneficial change or added value.

Project Management

Quality assurance (QA) is a way of preventing mistakes or defects in products and systems, and avoiding problems when delivering solutions or services to customers. QA is applied to software to verify that features and functionality meet business objectives, and that code is relatively bug free prior to shipping or releasing new software products and versions. Quality assurance comprises administrative and procedural activities implemented in a quality system so that requirements and goals for a product, service or activity will be fulfilled. Two principles included in quality assurance are: "Fit for purpose" (the product should be suitable for the intended purpose); and "right first time" (mistakes should be eliminated).

Quality Assurance

Programming includes both the specifics of the language you’re using, like Visual Basic, .NET, Java and others, but also the best practices in user experience and interfaces and the management of projects, version control and development. Other programming topics are related to web and cloud development and system and hardware programming.