The diagram above was tweeted by Philippe Krutchen (@pbpk) in October 2014 and recently retweeted by Ruth Malan (@ruthmalan). It addresses the need to align 3 aspects of development:
However, its intended scope is incomplete and risks aligning 3 tires while leaving the fourth badly out of alignment.
See https://charliealfred.wordpress.com/alignment-in-system-architecture for more discussion.
Software development processes are a lot more like business suits than they are like stretch socks. Implementing a process that worked well in some other organization or industry is like wearing somebody else’s clothes. Goldilocks nailed it on the head. “These clothes are too big! These clothes are too small…”
A dozen or more contextual factors determine how well a process will fit. Some are cultural. Some deal with project size and scope. Others deal with team size or geographic dispersion. Some deal with prior experience in the problem domain, and how static or dynamic the problem is. Others deal with prior experience with solution technologies, and how rapidly they are changing,
If you are looking for a process to copy, a) find one that is working well and b) find one whose contextual factors are very much like yours. Otherwise, examine your context closely, and use first principles to tailor a process to what you need.
The blog article at http://wp.me/PiW0e-5j discusses the contextual factors and presents two examples of how they apply.
Charlie Alfred's Weblog 