Collective responsibility for complete product development: Revision history

Jump to navigation Jump to search

Diff selection: Mark the radio buttons of the revisions to compare and hit enter or the button at the bottom.
Legend: (cur) = difference with latest revision, (prev) = difference with preceding revision, m = minor edit.

21 May 2024

29 January 2024

24 January 2024

  • curprev 01:4801:48, 24 January 2024‎ Ppugliese talk contribs‎ 1,757 bytes +1,757‎ Created page with "__NOTOC__ ==Description== Whilst a single team may focus on a subset of the value stream, all teams are collectively responsible for the cohesion and success of the overall product. This applies to both the collective elements that form the product as well as the end-to-end lifecycle from idea to customer outcome. ==Rationale== As we scale, there is a risk that teams generate elements of the system that are inconsistent with the local optimisation of design decisions. T..."
Retrieved from ‘https://go-else.org:443/index.php?title=Collective_responsibility_for_complete_product_development’