The AGILE SOFTWARE PRODUCT LINE AUTOMOTIVE - ASSESSMENT MODEL




Purpose

The purpose of Agile Software Development is to react faster on customer needs and legal constraints to reduce the time to market for innovative feature upon a simultaneous increase of software quality.


Outcomes

Process related Outcome - Base Practices - Work Products

ProcO_03.01 Features are developed in a faster pace and the time to market is reduced upon a simultaneous increase of software quality.
BP_ProcO_03.01 Reduce time to market with a faster feature development. Ensure that the time from initial idea to first release and time-to market is reduced. Further, ensure that the decrease of development time does not result in a decreased software quality.
A_01-03 Software Item
ProcO_03.02 Products and features are released as early as possible and the cost of delay for new product and market specific features is reduced.
BP_ProcO_03.02 Release product and market specific features early. Ensure that features for specific markets and products are released early and get afterwards repatriate in the software product line.
A_01-03 Software Item
ProcO_03.03 Changes in requirements are included into the development process and are taken into account.
BP_ProcO_03.03 React on changes during the development. Ensure that late changes in requirements are addressed in an acceptable time.
A_01-03 Software Item
A_08-28 Change Management Plan
ProcO_03.04 Legal constraints are fulfilled by the development process.
BP_ProcO_03.04 Analyze and consider constrains given by the law. Ensure that legal constraints are fulfilled and required artefacts are created.
A_13-01 Acceptance Record
A_13-08 Baseline
A_13-08 Delivery record
A_17-05 Documentation requirements
ProcO_03.05 The agile software development is synchronized with all affected parties.
BP_ProcO_03.05 Synchronize the agile development with the surrounding processes. Ensure that agile development is synchronized with all affected parties.
A_11-05 Software unit
ProcO_03.06 Outsourced agile software development is funded according to the development task.
BP_ProcO_03.06 Focus on business value. Ensure that agile development is in budget, creates business value and new terms of supplier payments are introduced.
A_02-01 Commitment/ Agreement
ProcO_03.07 The use of agile practices is not stipulated, context-specific agile practices are used.
BP_ProcO_03.07 Utilize agile practices whenever applicable. Ensure agile practices are suited for the context they are practiced.
A_07-05 Project measure
A_07-05 Quality measure
A_07-05 Risk measure
A_08-12 Project Plan
A_13-01 Acceptance Record
A_13-04 Communication record
A_13-04 Review plan
A_13-04 Meeting support record
A_13-04 Documentation Plan
A_13-04 Configuration management record
A_13-04 Progress status record
A_13-04 Proposal review record
A_13-08 Baseline
A_13-08 Delivery record
ProcO_03.08 Knowledge is transferred to other variants in the SPL by retrospectives.
BP_ProcO_03.08 Implement retrospectives and feedback culture. Ensure that knowledge gained in a retrospective of one software variant is transferred to all other software variants.
A_07-05 Project measure
A_07-05 Quality measure
A_07-05 Risk measure
A_13-04 Communication record
A_13-04 Review plan
A_13-04 Meeting support record
A_13-04 Documentation Plan
A_13-04 Configuration management record
A_13-04 Progress status record
A_13-04 Proposal review record


Product related Outcome - Process Attributes - Work Products

ProdO_03.01 The software satisfies customer needs and the customer is directly included into the development.
PA_ProdO_03.01 The development shall focus on customer needs. Ensure that customer feedback is integrated into the development of the product, by means of close customer collaboration.
A_07-01 Customer satisfaction survey
A_07-01 Customer satisfaction data
A_07-01 Field measure
A_07-01 Service level measure
A_13-17 Customer request