The most prevalent development methodology in use today is the Agile methodology. There are a multitude of different “flavors” of Agile, and there is no single approach that is perfectly suited for all situations and all teams. When we look at how a company produces software, it is not about whether they are following the letter of the law of any specific methodology, but more importantly, whether a methodology is defined, agreed upon, and followed by everyone on the team. In early-stage companies with small teams and senior resources from the industry, the process can be very light because the developers are mature and self-disciplined enough to follow best practices. And, if they understand the industry, they don’t need everything spelled out for them. This is the most efficient form of development team and process. However, at the other end of the spectrum, if there is a large team with many junior or offshore resources, a heavier process is needed to ensure the right things are being developed correctly.
This is where the experience and discernment of the resources doing the assessment come into play. Two teams with the same process could score very differently from the perspective of risk, given these other factors. Having a tech diligence partner who understands the nuances of how different teams need different processes is critical. A one-size-fits-all approach to the product development process can raise unnecessary concerns that cloud the focus on the things that truly matter.