Comments on: Good Requirements are SORTA NUTS http://svprojectmanagement.com/good-requirements-are-sorta-nuts Project management wisdom from practictioners and the UCSC Extension in Silicon Valley Tue, 16 Mar 2010 03:47:39 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: JoshNankivel http://svprojectmanagement.com/good-requirements-are-sorta-nuts/comment-page-1#comment-232 JoshNankivel Mon, 30 Apr 2007 20:06:36 +0000 http://svprojectmanagement.com/?p=285#comment-232 I know exactly what you are talking about. I think there are 2 main causes for a project manager not understanding the expectations or true needs of stakeholders: 1. As you stated, it can be uncomfortable to push back on the customer and make them drop their pre-conceived notions of what the solution should be. If you don't however, expect that about half the time the solution won't really solve the root problem. Compare the time and effort up-front to define the root problem with the potential re-work required on the back-end if the pre-conceived solution fails. In my experience, you avoid this risk almost completely by laying it all out on the table right away. 2. The second reason seems to be that project managers don't realize the need to analyze their assumptions, and the stakeholder/sponsor assumptions, objectively. They just say "I was told to go implement this, so here we go!" Requirements gathering is not a good time to make assumptions lightly. Josh Nankivel <a href="http://www.PMStudent.com" rel="nofollow">http://www.PMStudent.com</a> I know exactly what you are talking about. I think there are 2 main causes for a project manager not understanding the expectations or true needs of stakeholders:

1. As you stated, it can be uncomfortable to push back on the customer and make them drop their pre-conceived notions of what the solution should be. If you don’t however, expect that about half the time the solution won’t really solve the root problem. Compare the time and effort up-front to define the root problem with the potential re-work required on the back-end if the pre-conceived solution fails. In my experience, you avoid this risk almost completely by laying it all out on the table right away.

2. The second reason seems to be that project managers don’t realize the need to analyze their assumptions, and the stakeholder/sponsor assumptions, objectively. They just say “I was told to go implement this, so here we go!” Requirements gathering is not a good time to make assumptions lightly.

Josh Nankivel
http://www.PMStudent.com

]]> By: paulandrew http://svprojectmanagement.com/good-requirements-are-sorta-nuts/comment-page-1#comment-229 paulandrew Mon, 30 Apr 2007 15:44:49 +0000 http://svprojectmanagement.com/?p=285#comment-229 Great topic. I try to notice times when I'm reluctant to have those "expectation" conversations and think <b>"I'll just hope for the best."</b> When I can spot it, that's a flag that something is going off track. The thing I wonder about is what makes it tough to have those "let's set expectations" conversations? <b>Everyone knows setting expectations clearly is important--how many do it consistently? </b> Great topic. I try to notice times when I’m reluctant to have those “expectation” conversations and think “I’ll just hope for the best.” When I can spot it, that’s a flag that something is going off track.

The thing I wonder about is what makes it tough to have those “let’s set expectations” conversations?

Everyone knows setting expectations clearly is important–how many do it consistently?

]]>