InfoQ Homepage Project Management Content on InfoQ

Articles

RSS Feed

Newer Older

Culture & Methods

WTF requirements in Agile Product Development

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.

Gene Gendel
on Aug 11, 2016
Culture & Methods

Waterfall Requirements in Agile Product Development

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.

Gene Gendel
on Aug 11, 2016
Culture & Methods

Why ALM Is Becoming Indispensable in Safety-Critical Product 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.

Kristof Horvath
on Jul 15, 2016
Culture & Methods

Q&A with Johanna Rothman and Jutta Eckstein on Cost of Delay

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.

Ben Linders
on Jun 16, 2016
Culture & Methods

User Stories Are Placeholders for Requirements

It can be difficult to change from a Waterfall approach where ‘business analysts write big requirements up front’ to the Agile practice in which requirements are prepared ‘just in time’, and are the responsibility of the entire team. The secret to success in Agile is ruthless management of scope.

Russ Lewis
on Jun 06, 2016
Culture & Methods

Using SEMAT and Essence at Fujitsu UK

Fujitsu UK is using a large number of processes and methods which have developed over the period of many years. Looking for a way of combining agile and traditional methods, they became aware of SEMAT and the Essence Kernel. This article explores how they applied SEMAT and Essence to systems engineering, and used it to look at the whole programme of work across all disciplines.

Ste Nadin
on Jun 04, 2016
Culture & Methods

Is There Really Such a Thing as a “Hybrid Agile” Method?

There are dozens of Agile methods nowadays and more and more often we hear about Hybrid Agile, but what does that actually mean? This article provides a view on why it is important to have clarity around the term Hybrid Agile and what it has to mean to make sense. It provides guidance on circumstances when you could use the different kinds of methods.

Mirco Hering
on May 04, 2016
Culture & Methods

Q&A with Dave Snowden on Leadership and Using Cynefin for Capturing Requirements

Dave Snowden gave a talk titled "Context is Everything" at the Scaling Agile for the Enterprise 2016 congress in Brussels, Belgium. InfoQ interviewed him about applying leadership models, the Cynefin model and how it can be used for capturing requirements, scaling agile, and sustainable change.

Ben Linders
on Apr 23, 2016
Culture & Methods

Q&A with the Authors on "Requirements: The Masterclass LiveLessons-Traditional, Agile, Outsourcing"

Suzanne and James Robertson, authors of numerous publications in the requirements field, launched a video course called "Requirements: The Masterclass LiveLessons-Traditional, Agile, Outsourcing". InfoQ interviewed them on these video lessons to get further insights into some of the topics addressed.

Rui Miguel Ferreira
on Apr 17, 2016
Culture & Methods

Agile Approaches in Test Planning

At Agile Testing Days 2015, Eddy Bruin and Ray Oei explained how to satisfy the needs of stakeholders who ask for test cases, test plans, and other comprehensive test artifacts without writing large test plans. An interview about test plans in agile, how to make stakeholders aware that they can influence quality, and which agile practices they recommend for testing.

Ben Linders
on Feb 21, 2016
Culture & Methods

The Agility Challenge

To be successful, a company needs to become an agile enterprise. 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, know what they are trying to achieve, understand why, be able to decide by themselves how to best do it and genuinely care that it gets done.

Dragan Jojic
on Feb 04, 2016
Culture & Methods

#noprojects - Outcomes: The Value of Change

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. He looks at the context in which value is derived, provides an approach to define and measure outcomes and discusses the impact of constraints.

Evan Leybourn
on Jan 14, 2016