Yup, you’ve got the branching correct.

It’s probably worth mentioning that the 1-4 on the map was used to represent MoSCoW priorities.

1 = Must
2 = Should
3 = Could
4 = Would

All our 1′s are on the critical path. 2-3′s could potentially be dropped, as they are not essential to the business folks. So essentially if a branch had for example five sub tasks, ranging from one must, three should’s, and a would, essentially only the must would really have to get done on that branch, if we really needed the points to spend elsewhere.

The one thing which was quite hard to do on this map at such a scale was to highlight dependencies between items. I always find linking nodes troublesome with XMind, as when new items are added to the map the links often mess up and overlap, or become unreadable if we add too many . So I only highlighted those close together, which there weren’t many.

Hope that helps and thanks for the comment.

Cheers,

Darren.

I’m just trying to understand the tech scope diagrams. Is each high level branch (say FBfunc2) an independent task that can be developed and deployed in isolation, and all sub branches under that branch are smaller tasks that are required to be done before FBfunc2 can be considered “done”?

Does that mean, you can select any high level branch independently of anything else since they are essentially ‘stand alone’?