Obviously, every organization is different. Therefore, every organization will use these patterns somewhat differently. For a given organization at a given time, certain patterns may be very important, others may be only somewhat useful, while others may not apply at all. But given this fact, how do you use these patterns to best advantage?
Note that every pattern has a context, which defines the boundaries of usefulness for that pattern. The context generally shows up at the top of the pattern, although some context is buried in the exposition of the problem. It is often difficult to separate the context and the problem. So you should read the context and problems with an eye to how they fit your particular organization. Note that the context of an organization changes over time. In particular, consider the following:
How large is your organization? In addition, how large and complex is the software you are working on? Several of these patterns apply best to large or small organizations.
How mature is your the organization? How long have people worked together? In mature organizations, the roles tend to be well understood. New organizations will be find the patterns of piecemeal growth of the organization more useful.
How mature is the software under development? This is different from the maturity of the organization. Mature software is more appropriate for HubSpokeAndRim, for example.
What is the culture of the organization? Sometimes, the organization's culture makes easier — or harder — to apply certain patterns.