There is more to calculating ROI than a simple equation. It can be affected by risk, time, and other factors—including whether your team is agile. Releasing software immediately after coding and testing accelerates feedback cycles, minimizes the cost of delay, and increases return on investment. Allan Kelly tells you how.
One of the common misperceptions with agile software development is that agilists don't "do architecture." This completely ignores the 11th principle of the Agile Manifesto which states that the best architectures evolve over time. In this article Scott Ambler overviews an agile practice called "architecture envisioning" which enables you to gain the value from modeling without the cost of needless documentation.
Powerful new development technologies such as model-based code generation will overwhelm test teams that continue to create tests by hand. It's time for testers to put their own productivity into a higher gear. Harry Robinson tells you all about it in this column.
The Internet of Things (IoT) enables amazing software-powered devices designed to make our business and personal lives easier. Lev Lesokhin discusses four fundamental practices you'll need when developing sophisticated software for the IoT.
With incoming priorities being requested by just about everybody, how in the world can you and your team prioritize? Brandon shows you some innovative techniques that you can use to turn chaos into order. One surprising approach is simply handling priorities on a first-in, first-out basis.
Do your stakeholders use different terms to talk about the same concept or use the same term but in a different way? A domain model can clarify key concepts and the relationships between them, helping your team resolve ambiguous terms and leading to more productive discussions about project requirements.
Mike DePaoli sits down with us to discuss how project leaders, not unlike farmers, benefit from turning to science to give themselves the best chances at a bountiful harvest. We discuss how agile's preference for holistic approaches provides an organic opportunity for success across the enterprise.
Dr. Dobbs senior contributing editor Scott Ambler sits down with Noel Wurst at Techwell.com to discuss how agile team governance does not have to have a negative stigma. Scott helps people see through naive assumptions, while eliminating out of control governance to get teams back on track.
We recently had the opportunity to speak with Alexander Andelkovic, who works as a test lead for Spotify in Stockholm, Sweden. Alexander is a driving force for implementing agile model-based testing techniques and is an ambassador for session-based test management.
Heather Shanholtzer interviewed Seilevel's Joy Beatty about the benefits of using visual modeling instead of traditional requirements documents and why writing good requirements might not be your best point of focus.
Even seemingly simple software systems can be a dense forest of intersecting logical pathways which may leave you wondering if your testing was robust enough. Traditional test cases are flawed since they only execute the pathways the tester considered at the time the test case was written...
Model-based testing can be a powerful alternative to just writing test cases. However, modeling tools are specialized and not suitable for everyone. On the other hand, keyword-driven test automation has gained wide acceptance as a powerful way to create maintainable automated tests, and...
For decades, software development tools and methods have evolved with an emphasis on modeling. Standards like UML and SysML are now used to develop some of the most complex systems in the world. However, test design remains a largely manual, intuitive process.
In the test lab and in production everything hinges on looking at the right performance metrics. A common problem for engineering teams is that they don’t know what metrics they should be analyzing. It’s easy to get lost in an ocean of data from disparate monitoring tools and...