I'm sure you can tell me what you do. You can probably describe, in excruciating detail, how to do it. Let me ask you a simple question. Why do you do what you do?

We continue to look forward to sending to and hearing from our SBDi Tips Members. We use these tips as a means to share our knowledge and experience with you. Our ears (eyes for emails) are always open waiting to hear what is of concern to you in the area of Requirements Engineering, Project or Program Management, and Process Improvement. Please continue to send in your inquiries and we hope you continue to find these tips helpful and useful.

Now, let's complete our Anti-Pattern discussion.

Risk refers to anything that could compromise a requirement not being satisfied. Risks can occur throughout the product's and project's life.

Every day you can view it with the opportunity to review the state of different projects and deliverables within your Programıs boundaries. Each individual piece requires coordination.

What needs to be coordinated?
Coordination needs to be discussed at three levels. First is the coordination of running the project on a day-to-day basis; second is the product development coordination; third is coordination at the business level. In this tip we will focus on the day-to-day coordination.