Models can help you explore existing code and discuss new designs; clarify users’ needs and define tests; and be used to generate some of the code. This article shows how working with models will help you in an agile project.
This article takes a closer look at each of the 12 Agile principles and explore a suggestive set of qualitative and quantitative measures that can potentially provide the necessary insights into teams' adherence to them.
In an Agile world, when should performance testing be conducted? Every sprint or only at the end of the product development, as it used to be conducted in the Waterfall model? How do we test for performance within sprint after sprint? How efficient is it to conduct performance testing at the end of the product development?
This article discusses how to take advantage of the talents of your team's architects to develop visionary software responsibly. Software architects are often talented problem solvers. How can your Agile team leverage its architects' capabilities, while still delivering value responsibly? Test-driven architecture makes the role of architect relevant in the Agile age.
To successfully create the significant breakthroughs in your development effectiveness that are possible with agile, it has to be aligned with why you want to do it in the first place and what you need to achieve from it. The authors of A Practical Approach to Large-Scale Agile Development explain how to tune agile to your business objectives.
The DoD is facing challenges to rapidly deploy operational capabilities in complex environments where bridging legacy and new technologies are key to success. The challenges arise as a result of diminishing budgets and the need for new capabilities to operate in war environments, including the global war on terrorism. To balance this imperative need with rapid response, we found that our developed Agile life-cycle paradigm was a viable solution to meet challenges brought about by changes in the environment. This article demonstrates how a DoD program used an Agile approach, throughout every phase of the program’s life cycle, to rapidly field capabilities.
No one person can know everything and needs to rely on the talents of others to be successful in a role, on a project, or in the marketplace. With the increasing pace of change, trusting each other - and unleashing talent - is critical.
If we often associate Agile mainly with project management, the principles of the Agile Manifesto can also be applied to other software development activities. In this article, Nadya Knysh explains how to use these principles in mobile software development and more specifically in the testing of mobile apps.
This article discusses the differences between quality assurance and software testing. If the developer uses techniques like TDD to prove that his program can work, you shouldn’t ask him to prove the opposite. This article advocates having a separate software testing function, even if you are using an Agile software development approach like Scrum.
This report study details how a shift from traditional agile metrics (Story Points, Velocity) to actionable flow metrics (Work In Progress, Cycle Time, Throughput) reduced Cycle Times, increased quality, and increased overall predictability at Siemens Health Services.