Improving product quality is often a very difficult task for even the best software development organizations. Rajini says the additional benefits of automation include benchmarking, code scanning analysis, end-to-end test cases, and compatibility validation.
DevOps is represented by a set of principles and practices that help improve communication and collaboration between development and operations. Bob Aiello and Leslie Sachs have put together a great introduction showing how quality assurance needs to commence at the very start of a DevOps project.
The cloud and the rapid migration to mobile devices and the Internet of Things have made traditional software licensing schemes obsolete. Omkar describes new software monetization based on business, pricing models, and usage.
It isn't unusual for a project team to believe that adopting a mix of waterfall and Scrum can deliver the best of both worlds. According to Steve, nothing could be further from the truth. In fact, Steve retraces a real project that quickly disintegrated into an absolute disaster.
Software vendors are making extraordinary efforts to protect the installation and use of apps, but have they gone too far? Preventing software piracy can have an adverse effect on genuine users. Software licensing technology, according to Steve, needs to strike the best balance of protecting the asset while trusting the customer.
By using an approach similar to that used by surfers to catch waves, you can effectively help your team transition to agility. Scott presents a four-stage process that alternates training with coaching and doing with learning.
Alan Crouch addresses the question most commonly raised by those who are new to security testing: "How does security testing fit in my QA process?" Alan explains that security testing shouldn't be limited to the QA process, but instead should be applied throughout the entire software development lifecycle. Read this FAQ column for suggestions on how to improve your chances for success in catching security issues.
By emphasizing better communication and collaboration between software development and IT, this article explores ways to establish trust by focusing on customer value. For example, Manoj Khanna suggests continuous integration and validation as techniques that helps build that trust.
Matt Heusser presents ten key factors to establish a team cadence—the time between running tests and getting a product into production. The shorter the cadence, the less time spent in test/fix/retest land, and the more time spent working on new features.
Thomas Wessel presents how T-shaped and pi-shaped teams based on each member's span of knowledge, ability to collaborate, and depth of expertise play an important part in how effectively your team performs.