Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Problems with requirements reviews and client signoff!!
Previous Previous
 
Next Next
New Post 7/30/2010 10:50 AM
User is offline simo75
1 posts
No Ranking


Problems with requirements reviews and client signoff!! 

 

Hi all,

first time poster!

Recently started as a newbie BA on a pretty big software development project and after some weeks putting together the FRD's we are now in the position of first drafts out for review and signoff. However we are having problems and delays getting requriements signed off. We have split the development scope up into manageable work packages, where each funtional area has an FRD. So we will probably end up with 1-15 FRDs overall.

key issues
- As the Customer has been let down previously on promises made on delivery estimates on other projects so key stakeholders are somewhat pendantic and difficult to pin down, busy diaries (sorry no time for this!) and to get eventual sign off. PLUS the BA's and techncial team plus the senior mgmt is on the back foot given historical issues so it is also partly political!

-Difficulties in getting internal reviews working, scheduled and getting feedback in a timely way.

-general overall mish mash of approaches and difficulties to the signoff process.

Having sat down and had a good think on this have come up with following approach as a basic outline.

1. once an FRD has been documented this is issued by the BA/Lead BA/PM for internal quality review (not to the customer) to be returned with comments on the document within x days. Depending on the FRD area might be better for meeting or both? How best to schedule?

2. Once comments returned these are updated to the FRD, and internal review held to discuss. Further updates made.

3. Document is then issues to customer for review with return date? However might be better for facilitated review?? This might depend on the complexity and size of FRD.

4. Further changes made to document by the BA follwing the customer review.

5. Then agree to signoff follwing resolution of changes, issues raised.

These are my initial thoughts on the approach, the team seem to be lacking a formal requirements management approach!!!

other things

approaches to scheduling?, agreement with customer on the signoff approach? length of time for reviews?

I'd really welcome comments from all and from those who have been there and done it all!! plus any tips techniques.

cheers

 

 

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Problems with requirements reviews and client signoff!!

Community Blog - Latest Posts

As Business Analysts in Agile teams, we often hear about Definition of Ready (DOR) and Definition of Done (DOD). But beyond the buzzwords, these two concepts are powerful tools to drive clarity, consistency, and quality in our work. Definition of Ready ensures a user story is truly ready for development. It answers: Is this story clear, feasible...
In today's fast-paced digital world, successful projects aren't just built on great code—they're built on clarity. And that clarity often comes from one key player: the Business Analyst. At the heart of every great product or system is a need—a business goal, a customer pain point, or a regulatory requirement. But busines...
I have always loved cooking. I learned from my Grandma June and her kitchen was her sanctuary, a small, warm sunlit space filled with jars of spices, stacks of cookbooks, and the comforting smell of something always on the stove or baking in the oven. Grandma June was as great a cook as she was a teacher to me. She never followed a recipe “to...

 






 

Copyright 2006-2025 by Modern Analyst Media LLC