Comments on: Using a stakeholder requests list as part of scope definition http://www.bridging-the-gap.com/using-a-stakeholder-requests-list-as-part-of-scope-definition/ Helping business analysts become leaders and advance their careers. Thu, 09 Sep 2010 12:12:17 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Laura (Brandau) Brandenburg http://www.bridging-the-gap.com/using-a-stakeholder-requests-list-as-part-of-scope-definition/comment-page-1/#comment-3740 Laura (Brandau) Brandenburg Wed, 04 Nov 2009 15:29:00 +0000 http://www.bridging-the-gap.com/?p=1832#comment-3740 Thanks, Linda! The attributes I am referring to are in the bulleted list starting with "Strategic Fit". What I mean is that you should customize how you present your list of requests to fit how decisions will be made about the project. Thanks, Linda! The attributes I am referring to are in the bulleted list starting with “Strategic Fit”. What I mean is that you should customize how you present your list of requests to fit how decisions will be made about the project.

]]> By: Linda Bogie http://www.bridging-the-gap.com/using-a-stakeholder-requests-list-as-part-of-scope-definition/comment-page-1/#comment-3739 Linda Bogie Wed, 04 Nov 2009 14:57:11 +0000 http://www.bridging-the-gap.com/?p=1832#comment-3739 Laura, your structured stakeholder requests list is a fantastic suggestion for defining scope and fleshing out requirements. Using the list as a stakeholder feedback tool to help validate and finalize high level requirements, and ultimately to control scope creep, is brilliant. I am not sure that I understand exactly what "attribute" you are referring to in the following paragraph. Can you please explain. "As you flesh out your requests, feel free to add or remove from this list. I rarely use all of the above attributes and I often find myself using an attribute I’ve never used before to meet the needs of a specific situation." Thanks lots for another very insightful article! Laura, your structured stakeholder requests list is a fantastic suggestion for defining scope and fleshing out requirements. Using the list as a stakeholder feedback tool to help validate and finalize high level requirements, and ultimately to control scope creep, is brilliant.

I am not sure that I understand exactly what “attribute” you are referring to in the following paragraph. Can you please explain.

“As you flesh out your requests, feel free to add or remove from this list. I rarely use all of the above attributes and I often find myself using an attribute I’ve never used before to meet the needs of a specific situation.”

Thanks lots for another very insightful article!

]]>