ISO 26262 and Agile practices

ISO 26262 and Agile practices:
https://www.ibm.com/developerworks/mydeveloperworks/blogs/invisiblethread/entry/five_benefits_of_agile_practices?lang=en

This is a very interesting article tackling a very tangible problem in industry - footprint of standard implementation. The article explains how the process footprint can be decreased by adopting certain Agile practices.

The article shows that there can be possibilities of tailoring agile to heavier processes where (for example) safety requirements are not something to play around with.

In non-Agile processes, the standard compliance usually takes a lot of effort and requires a lot of documentation. This article shows how this can be combined with agile practices on "minimum" documentation.

Recommended reading for all interested in standards implementation - not only in the automotive industry.

@MiroslawStaron

Agile metrics from IBM

Software Econometrics
http://public.dhe.ibm.com/common/ssi/ecm/en/ral14037usen/RAL14037USEN.PDF

This is a nice paper that conceptually describes goals with metrics in the Agile software development. A very good starter reading. I like the concepts and the ideology, but what I lack in the paper is the depth of how to measure things.

Some aspects that come to my mind as and old "metric" guy are:
- How to define "change" in the cost of change metric? What is the difference between rework and change?
- How to define scrap and rework? How to measure those concepts in software development? Is the first feature that one develops to show proof-of-concept a waste - or is it a learning activity?

In short - nice article, but requires digging deeper into the context.

@MiroslawStaron