The use of all-conclusive, hard-defined, non-negotiable BRDs is not appropriate in agile development. It will lead to an array of dysfunctions, including Local Optimization, deterioration of relationships between Product Owners and Feature Teams as well as loss of trust by end-customers. A refined, well-prioritized Product Backlog is the right place to store requirements in agile development.
Integrated Application Lifecycle Management platforms are advancing product development in life and safety critical environments. The story of how Medtronic Neuromodulation were able to modernize their processes using ALM helps us understand current and future trends in the development of complex software-heavy products.
The book Diving For Hidden Treasures - Uncovering the Cost of Delay in Your Project Portfolio by Johanna Rothman and Jutta Eckstein explores how projects become delayed and provides tools and methods to analyze and limit the costs of delay in projects.
It can be difficult to change from a Waterfall approach to the Agile practice in which requirements are prepared ‘just in time. The secret to success in Agile is ruthless management of scope.
This article explores how Fujitsu UK applied SEMAT and Essence to systems engineering, to combining agile and traditional methods and look at the whole programme of work across all disciplines.
There are dozens of Agile methods nowadays and more and more often we hear about Hybrid Agile, but what does that mean? The author presents some thoughts on what Hybrid Agile actually means. 2
InfoQ interviewed Dave Snowden about applying leadership models, the Cynefin model and how it can be used for capturing requirements, scaling agile, and sustainable change.
InfoQ interviewed Suzanne and James Robertson on the "Requirements: The Masterclass LiveLessons - Traditional, Agile, Outsourcing" to get further insights into some of the topics addressed.
An interview with Eddy Bruin and Ray Oei about test plans in agile, how to make stakeholders aware that they can influence quality, and which agile practices they recommend for testing.
In this article Dragan Jojic explores “the agility challenge”: A company where employees are able to sense and respond to external inputs without managers having to tell them what to do. 1
In this third article in the #noprojects series Evan Leybourn explains the importance of focusing on outcomes rather than activities in order to maximize value for the organization.
Boyan Mihaylov covers his experience when working with both traditional waterfall software architectures and agile ones. 11