As we move from one season to another in life, it’s important to step back, take stock, and gather the lessons that will benefit us in the next season and beyond. In this article, consulting software tester Matthew Heusser reflects on some of the lessons he’s learned.
There are many things to consider when picking an SCM standard or framework for your organization. Taking the time to explore compliance, politics, experience, and driving forces before making a selection will increase acceptance and smooth the transition.
Many organizations do not comprehend that just calling something a standard does not necessarily make it so to folks within the organization. There is effort required to create a standard that is valuable to the organization. On the other hand, thee are many de-facto standards that people do not recognize as a standard. This has to do with the drivers of the standards.
The model detailed in this article is a composite model for Software Quality Assurance (QA) to bring visibility into the software development process of low- and medium-maturity organizations. The QA review and measurement processes are integrated to form this composite model. Even though these processes are distinct, they both aim at providing visibility into the software development process. If managed well, both these processes together will provide better visibility and control over the software development process. On this common ground the composite model has been established. In this article, the ten elements of the model are discussed along with the benefits of implementing this composite model.