Comments on: Prioritising requirements – how to do it and why it is critical to project success http://businessanalystmentor.com/2009/04/05/prioitising-requirements-why-you-should-do-it-and-how/ destination site for business analysts Tue, 21 Feb 2012 13:29:34 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Five techniques to successfully manage scope | businessanalystmentor.com http://businessanalystmentor.com/2009/04/05/prioitising-requirements-why-you-should-do-it-and-how/comment-page-1/#comment-511 Five techniques to successfully manage scope | businessanalystmentor.com Sat, 10 Oct 2009 15:31:38 +0000 http://businessanalystmentor.wordpress.com/?p=81#comment-511 [...] being resistant then more formal requirements prioritisation techniques should be pursued. ( see article) There is a strong argument that these should be undertaken anyway to support discussions later in [...] [...] being resistant then more formal requirements prioritisation techniques should be pursued. ( see article) There is a strong argument that these should be undertaken anyway to support discussions later in [...]

]]> By: Rose Broadbear http://businessanalystmentor.com/2009/04/05/prioitising-requirements-why-you-should-do-it-and-how/comment-page-1/#comment-425 Rose Broadbear Fri, 05 Jun 2009 21:28:38 +0000 http://businessanalystmentor.wordpress.com/?p=81#comment-425 I think the authorneed to use spell check more often on the documentation (article). I was very distracted by the grammatical errors in this article. The content was very informative. I think the authorneed to use spell check more often on the documentation (article). I was very distracted by the grammatical errors in this article. The content was very informative.

]]> By: Prioritising Requirements | businessanalystmentor.com http://businessanalystmentor.com/2009/04/05/prioitising-requirements-why-you-should-do-it-and-how/comment-page-1/#comment-424 Prioritising Requirements | businessanalystmentor.com Fri, 05 Jun 2009 10:22:33 +0000 http://businessanalystmentor.wordpress.com/?p=81#comment-424 [...] have written a post on this subject here and will report back on this meeting if you are unable to [...] [...] have written a post on this subject here and will report back on this meeting if you are unable to [...]

]]> By: Alex P http://businessanalystmentor.com/2009/04/05/prioitising-requirements-why-you-should-do-it-and-how/comment-page-1/#comment-412 Alex P Thu, 28 May 2009 05:41:28 +0000 http://businessanalystmentor.wordpress.com/?p=81#comment-412 Tom thanks for your comment. I've looked at the documents but won't claim I've fully understood as there is clearly a lot to absorb! I'd be interested to hear how receptive your clients have been as the highly formalised approach would initimidate or turn off many business representatives. Alex Tom

thanks for your comment. I’ve looked at the documents but won’t claim I’ve fully understood as there is clearly a lot to absorb!
I’d be interested to hear how receptive your clients have been as the highly formalised approach would initimidate or turn off many business representatives.

Alex

]]> By: TOM GILB http://businessanalystmentor.com/2009/04/05/prioitising-requirements-why-you-should-do-it-and-how/comment-page-1/#comment-411 TOM GILB Wed, 27 May 2009 13:46:47 +0000 http://businessanalystmentor.wordpress.com/?p=81#comment-411 well we agree on need for prioritization of requirements. But, I think there are smarter and more dynamic ways to prioritize Here is some detail Choice and P… http://www.gilb.com/tiki-download_file.php?fileId=48 Mng Priorities http://www.gilb.com/tiki-download_file.php?fileId=60 well we agree on need for prioritization of requirements.
But, I think there are smarter and more dynamic ways to prioritize

Here is some detail

Choice and P…
http://www.gilb.com/tiki-download_file.php?fileId=48

Mng Priorities

http://www.gilb.com/tiki-download_file.php?fileId=60

]]> By: DougGtheBA http://businessanalystmentor.com/2009/04/05/prioitising-requirements-why-you-should-do-it-and-how/comment-page-1/#comment-326 DougGtheBA Wed, 15 Apr 2009 19:53:04 +0000 http://businessanalystmentor.wordpress.com/?p=81#comment-326 That would be exactly the point I was trying to make but...um....forgot to state. Thanks for covering for me. That would be exactly the point I was trying to make but…um….forgot to state. Thanks for covering for me.

]]> By: Alex P http://businessanalystmentor.com/2009/04/05/prioitising-requirements-why-you-should-do-it-and-how/comment-page-1/#comment-323 Alex P Tue, 14 Apr 2009 06:45:38 +0000 http://businessanalystmentor.wordpress.com/?p=81#comment-323 Hi Doug I absolutely agree with your comment. I haven't explicitly mentioned IT architect/designer as stakeholder but their view must always be considered. There is often a degree of technical risk associated with a project and that could be as it is unproven technology, untried in the company or particularly complex. All of these provide reasons for tackling this first. HOWEVER, this is only one of the reasons and, typically, this exercise should start a debate so that consensus is reached by all the parties. Ideally, you would deliver requirements that deliver most value to the business AND tackle architectural risk earlier. Alex Hi Doug

I absolutely agree with your comment. I haven’t explicitly mentioned IT architect/designer as stakeholder but their view must always be considered. There is often a degree of technical risk associated with a project and that could be as it is unproven technology, untried in the company or particularly complex. All of these provide reasons for tackling this first. HOWEVER, this is only one of the reasons and, typically, this exercise should start a debate so that consensus is reached by all the parties.
Ideally, you would deliver requirements that deliver most value to the business AND tackle architectural risk earlier.

Alex

]]> By: DougGtheBA http://businessanalystmentor.com/2009/04/05/prioitising-requirements-why-you-should-do-it-and-how/comment-page-1/#comment-322 DougGtheBA Sat, 11 Apr 2009 02:32:40 +0000 http://businessanalystmentor.wordpress.com/?p=81#comment-322 Alex: Though it may have been implied, I thought it worthwhile to post an explicit reply....the one thing that I didn't pick up on in your article is the architect/designer as stakeholder. I learned and have used a technique in which both the tech reps above perform a priortization and so do the business stakeholders. Both sides apply numerical weighting and the combination of biz/tech values that are highest indicates the hipri reqs. Why is this valuable? Because the tech people have an understanding of what reqs will have the most architectural impact if implemented. Hence building one req that is medium for a user yet high for a techie may bring more intrinsic value by describing a larger portion of the app architecture.....so the user gets more functionality earlier and the IT can define tech aspects, and the probs they might encounter with it earlier as well. Alex:
Though it may have been implied, I thought it worthwhile to post an explicit reply….the one thing that I didn’t pick up on in your article is the architect/designer as stakeholder. I learned and have used a technique in which both the tech reps above perform a priortization and so do the business stakeholders. Both sides apply numerical weighting and the combination of biz/tech values that are highest indicates the hipri reqs. Why is this valuable? Because the tech people have an understanding of what reqs will have the most architectural impact if implemented. Hence building one req that is medium for a user yet high for a techie may bring more intrinsic value by describing a larger portion of the app architecture…..so the user gets more functionality earlier and the IT can define tech aspects, and the probs they might encounter with it earlier as well.

]]>