1. Do we really need capability patterns by discipline? Most of the capability patterns defined have one or two tasks inside, sometimes duplicating what is already said inside each task, adding no value Since we don't have much content on collaboration I propose that we use capability patterns for defining collaboration patterns on the 3 process that we have defined: intent, solution and management… these patterns could show the project evolution over time and be used to better define what happens in each phase … (we can not see that on the current project phases because all the phases look equal)… examples follow, just for illustration purposes…if you agree and we would have much less patterns to introduce content than what we have now…

3. Inception

4. Elaboration

5. Construction

6. Transition