One of the questions that has been generally asked by Project Managers and Delivery Heads is pertaining to estimation of effort involved in Requirements Gathering.

I have heard about Requirements Work Plan which help in breaking down the requirements activities and help in estimation, but havent had any experience on the same.

Has somebody used a Requirements Work Plan to estimate the Requirements phase or arre there any standards which point what is the time required for each of the activities ( for exaplme time required for each of the interviews, documentation, JAD sessions, follow ups etc).

I would also appreciate if somebody can provide a template if they have on capturing the above.

Regards
Vinay

BABOK identifies the following requirement attributes which a BA should capture in the early stage of requirement elicitation:(refer page 155, section Capturing Req. attributes)
1. Source
2. Value
3. Priority

My questions is how do we capture or measure value of a requirement?

I think there could have been many other attributes including Complexity, Risk, Status, etc...but have never heard of Value....any thoughts!!!

Hi,

I hope this forum can help me.

I’ve written a functional specification for an enhancement to the system across the full business horizontal – new procurement, new storage, maintenance, new products, and five distribution channels.

All the business stakeholders have signed-off the specification +/- 20 people, with the exception of four signatories from IT, who will program the solution.

IT has sent the spec back four times for what I regard as relatively minor changes. I get the impression that the individuals there are being obstructionist. It’s starting to cause serious delays on this project.

Does anyone else have any advice about how I can get an obstructionist IT team to change to work with us rather than against us?

Thanks,
Andrew