Architectural cohesion: 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

24 January 2024

  • curprev 01:4001:40, 24 January 2024‎ Ppugliese talk contribs‎ 2,195 bytes +2,195‎ Created page with "__NOTOC__ == Description == When a Value Stream is too large to be managed by a single Product Owner and Team, it should be broken into smaller parts, each of which should be as cohesive as possible whilst still aligning with business synergies. The Team working in that part needs to be able to: # Do the work with the least possible amount of technological and functional dependencies on other parts (low coupling) # Be able to validate their work in a fast and effective..."
Retrieved from ‘https://go-else.org:443/index.php?title=Architectural_cohesion’