Can a product line approach be compatible with agile development methods?
The short answer is yes, as demonstrated by the successful use of eXtreme Programming (XP) in Salion’s product line effort [Clements 2002d]. However, the larger point is that the applicability of agile methods is more strongly determined by whether a project’s characteristics align with a method’s “home ground.” (See the example practices under the “Process Discipline” practice area.)Boehm and Turner advocate a pragmatic, risk-driven approach to choosing appropriate aspects from both plan-driven and agile methods [Boehm 2004b]. For projects whose characteristics stray from agility’s home ground, it may still be possible to partition off portions where agile methods can flourish.One challenge to agile methods’ applicability is the principle of simple design, de-emphasizing the importance of software architecture. Within XP, this concept is known as “You Aren’t Going to Need It” (YAGNI). As Boehm says, YAGNI works fine when future requirements are largely unpredictable but can be highly
The short answer is yes, as demonstrated by the successful use of eXtreme Programming (XP) in Salion’s product line effort [Clements 2002d]. However, the larger point is that the applicability of agile methods is more strongly determined by whether a project’s characteristics align with a method’s “home ground.” (See the example practices under the “Process Discipline” practice area.) Boehm and Turner advocate a pragmatic, risk-driven approach to choosing appropriate aspects from both plan-driven and agile methods [Boehm 2004b]. For projects whose characteristics stray from agility’s home ground, it may still be possible to partition off portions where agile methods can flourish. One challenge to agile methods’ applicability is the principle of simple design, de-emphasizing the importance of software architecture. Within XP, this concept is known as “You Aren’t Going to Need It” (YAGNI). As Boehm says, YAGNI works fine when future requirements are largely unpredictable but can be highl
The short answer is yes, as demonstrated by the successful use of eXtreme Programming (XP) in Salion’s product line effort [Clements 02]. However, the larger point is that the applicability of agile methods is more strongly determined by whether a project’s characteristics align with a method’s home ground. Boehm and Turner advocate a pragmatic, risk-driven approach to choosing appropriate aspects from both plan-driven and agile methods [Boehm 04]. For projects whose characteristics stray from agility’s home ground, it may still be possible to partition off portions where agile methods can flourish. One challenge to agile methods’ applicability is the principle of simple design, de-emphasizing the importance of software architecture. Within XP, this concept is known as “You Aren’t Going to Need It” (YAGNI). As Boehm says, YAGNI works fine when future requirements are largely unpredictable but can be highly inefficient where there is a reasonable understanding of future needs. Because a
Related Questions
- They both approach development in an iterative and incremental way. Why didn you incorporate more software product line functionality into Code Roller?
- Is a model-driven development (MDD) approach compatible with the software product line strategy?
- Can a product line approach be compatible with agile development methods?
