Whether you’re leading a team that is putting together applications for sale to customers or developing applications for your enterprise, you and your team always face the question, “How can we develop applications quickly and efficiently without compromising quality?”

In answer to that question, TechRepublic columnist Tim Landgrave has come up with a method of development he’s dubbed “Q2,” short for “developing quality software quickly,” which he details in this five-part series. Here’s a summary of each column:

  • The first Landgrave’s View to cover Q2, “Developing software quickly: How to use the Q2 system,” focuses on the basic rules that define a Q2 development project and covers ways to engineer your development process.
  • In the second installment, “Defining quality in a Q2 development project,” Landgrave covers methods that your developers can use to produce prototyping and proof of concept code to help users, testers, and senior managers understand how features may be implemented.
  • “Developing the blueprint for a Q2 development project” describes the importance of clearly defining not only the problem your application is trying to solve and how you’re going to address it, but also the expected business benefits of solving the problem.
  • The fourth article, “Developing code using Q2,” looks at dividing code into two phases: code development and code completion. Such a system is designed to allow the quality-assurance group to begin interface testing and documentation work while allowing the groups responsible for maintaining the reference platform to see what, if any, changes need to be delivered for this application in the production environment.
  • The last article in the series, “Delivering the goods using the Q2 system,” focuses on finishing the testing process, eliminating high-priority bugs, and completing testing and quality assurance (QA) on the deployment process.

Do you have a method like Q2 that you use to manage projects? Tell us about it. Send an e-mail or start a discussion.