When it comes to DevOps, the fundamentals of CM may be forgotten (erroneously) by some practitioners. DevOps tools can be strategic assets, but they are not as important as established CM standards and process. It's up to us as practitioners to ensure that the DevOps tool chain implementation supports the corporate CM policy.
With SOA, the services you consume are typically developed by your organization or a close business partner, so you can assume they have standards similar to your own. But when you adopt APIs, you usually have no visibility into how solidly the services were built—or when and how they are evolving. How should you properly vet an external API?
Agile teams are supposed to take responsibility for how they work and how they learn. But what if you need to jump-start that learning? Agile transformation is about making this happen rather than waiting for it to happen. You need to get your team to learn the technical side of agile, and soon. Here are some effective approaches.
Based on the number of cloud computing standards organizations working on the problem, clearly interest is running at an all-time high. Here's a list of some of the bodies actively working on creating cloud standards.
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.
Ben Weatherall gives the rationale for standards from a non-traditional viewpoint, Know what you are trying to solve by first determining the root problems and your culture, and then try to either find a standard that matches or one that can be modified to fit your situation. Just make sure that if you follow a standard, you truly follow it and that if you modify a standard that you document where you vary from it.
Two topics that are likely to launch a development team into an impassioned discussion are development standards and development environments (IDEs, editors, etc). Combining the two topics into that of standardizing on development environments, is even more likely to spark debate. Decisions about development tools affect the day to day workings of each person on the team as well as the productivity of the team, and as such are important to discuss as a team organizes itself.
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, there are many de-facto standards that people do not recognize as a standard. This has to do with the drivers of the standards.