manageware.co.il

In most requirement management projects I came across, the Requirements-Review-Process was often “an issue”. A process that requires improvement.

Here is the basic dilemma, as I see it:

On one hand, you want as many stakeholders as possible involved in the review process.

By doing this, you will get people from different backgrounds that will bring different skills and knowledge to this process.

In addition, stakeholders will feel more involved and committed to the project.

On the other hand, having many reviewers involved in the review process is expensive and can cause a great over head on this process.

The more reviewers are involved, it will cause:

1. More people in the organization will consume their time in the review process (and time is money, isn’t it?)

2. The review process will become much more complex: there are much more inputs and comments to handle and review meetings might become much less effective (“where there are 10 different people, there are 10 different opinions”)

Quite a challenge, isn’t it?

In addition, finding this right balance is not enough to get a good review process.

There is much more to it…

In the coming DOORS user forum, we will discuss the Requirement-Review-Process, and hopefully we’ll get to share knowledge from different organisations on their “best practices” on this topic.

I will update this post after the forum with our findings

Share on Facebook