Dependencies between MOVEs

Is the assumption of MOVEs being completely independent one which can be negotiated?

We know that one of the toughest job of POs (or Flow Managers) is to slice and dice a project into separate, independent, reasonably sized chunks of work.

1 Like

Take the customer perspective: any MOVE needs to be usable and useful for a customer. If a MOVE is partially useful, because it needs another dependent MOVE, then I would consider putting them together into a bigger MOVE. Dependencies typically don’t need to be managed; it is far more important to mange customers’ expectations.

Note that MOVEs are not about architectural decomposition. They are about customer utility. A MOVE should exercise a whole slice of the architectural stack, so as to be usable.

1 Like