Articles
DevOps Articles for the Development team
Scroll down for more...
DevOps is to Agile what the right kitchen tools are to cooking. The tools cannot make up for a bad recipe, but they can help make a good recipe easier make and to make with the same quality over and over. The individual pieces of the DevOps infrastructure are not new, perhaps, but bringing them together to focus upon Agile development makes them new and extends the benefits of Agile. DevOps tools and practices build a lasting and effective bridge from the requirements to realization. Agile clearly helps drive efficiency into the development process by bringing the business closer to IT and helping to assure that what is built is what is most valuable to the business, and what is not wanted is discovered early. It is in the building of these systems that DevOps can enable another level of efficiency. The DevOps tools help the development and QA team to assure that what is built 'works' and anything that does not 'work' is discovered early. Rework is the enemy of most IT development cycles. With Agile, the business can reflect quickly when IT is heading in the 'wrong' direction. Similarly, DevOps tools allow the development team to quickly see when code integration, code coverage, and code quality begin to deteriorate.
0 Comments
"We will not promote any code with known defects". Try getting all your development teams to buy into that culture, let alone your IT and business management. At first, it seems crazy. Why do we even have defect classifications like 'show stopper', or 'low'? The assumption is that 'some' defects are fine! At Agile Down-to-Earth we do not agree. Defects in any form reduce the quality of the IT deliverable, and the result can be reduction of the business faith in IT. More importantly, acceptance of some defects is a 'cancer' that encourages slack development practices. Understood, it is often the business who chooses to allow lower priority defects to remain unresolved in the interest of cost and timing control, but defects that persist all the way to UAT are questionable at best and wasteful at worst. The culture shift is to prevent all defects before they reach late-stage testing. Early detection and remediation of defects is a culture, but also a practice that can be embedded in your SDLC. We propose here 14 levels of defect prevention that can be institutionalized to greatly reduce or remove late-stage defects. |
AuthorPaul Berryman is a passionate application development leader who has earned the title of champion of Agile and DevOps methods and tools for enterprise development teams ArchivesCategories |