Related Content
Designing an Office to Nurture Innovative Agile Development Teams Agile software development is a collaborative activity in many ways, but it also requires quiet time. While open office spaces foster communication and collaboration, it's still important for a workspace to have areas where people can buckle down and work. What is the best office configuration to nurture innovation? |
||
What Testers Need to Know about Security Every single tester should keep an eye on what security vulnerabilities might be plaguing their testing, but speaking in an interview at STARWEST 2016, Jeff Payne, the CEO and founder of Coveros, explained why you need to put a focus on security very early in the process. |
||
Naive Innovation in Software Testing The idea behind naive innovation is that a person with the right mindset and passion for a certain area is a great candidate for innovation, even without having the same subject matter expertise as a domain expert. Rajini Padmanaban looks at naive innovation in software testing. |
||
The Value of Testing Simply People obsess over the number of tests and test coverage, but tests that cover more code don’t always improve quality. Some tests have low value and thus, implicitly, high cost. Simple tests may not seem impressive at first glance. But the goal of testing is to ensure quality, and simple tests can be very valuable. |
||
Revitalize Your Problem-Solving by Conducting a Solution Analysis When you're solving a problem, it's a good idea to analyze a solution you come up with before implementing it. One way to do that is to ask what’s good about a proposed solution and what’s bad about it, focusing in particular on the impact of the solution. This way you can be sure you've thought everything through. |
||
5 Tips for Making the Most of Your Agile Meetings People think agile entails too many meetings, but usually that complaint has nothing to do with the number of meetings, but rather the way they're run. New agile teams often do everything together because they think that’s what agile expects, but that's not true. Here are five tips to better run your agile meetings. |
||
Engineering Architecture Systems for a Faster Build In the era of continuous integration and continuous deployment, big applications are creating bloated build pipelines. The problem is when code becomes so entangled that every change impacts large portions of the system, meaning there’s a lot to rebuild. If you reshape the code architecture, you can reduce build times. |
||
Finding the Bottlenecks in the Agile and DevOps Delivery Cycle To achieve incremental software development and continuous feedback, you need to eliminate the tasks that create bottlenecks, which hinder the flow of development. A chain is no stronger than its weakest link, and identifying these “weak links” is a critical step toward achieving agility and increasing efficiency. |