http://www.b2ttraining.com/2008/04/07/dinner-with-a-menu-or-without/ Connecting Business Requirements to Technology Mon, 30 Jan 2012 21:31:56 +0000 hourly 1 http://www.b2ttraining.com/2008/04/07/dinner-with-a-menu-or-without/comment-page-1/#comment-2543 Angie Wed, 07 May 2008 18:39:15 +0000 http://www.b2ttraining.com/page/business-analyst-blog/archives/132/dinner-with-a-menu-or-without#comment-2543 Andrew - I agree that many business stakeholders are interested in documentation One reason is because they need to explain or train the impact of systems changes to the rest of their organizations. I would like to think that no one creates documentation for job security. I think you are referring to the deliverable sign-offs (as job security) which is more of an IT project management effort to protect themselves if the business says they are unhappy with the resulting software system. They can say your sign-off was on the detailed documents, and the software is built per specs. Although that may be true (and binding) - does that lead to a happy, satisfied customer? Is the project deemed successful in that case? I would say no. By the way the BA has failed in communicating clearly with the stakeholders. I think that is why agile development began with a focus on producing less documentation- "only what is necessary". Agile thought leaders say that there has been too much focus on documents and not enough on whether the customer getting the software that they need. I absolutely agree that we should only produce documentation that adds value. Andrew – I agree that many business stakeholders are interested in documentation One reason is because they need to explain or train the impact of systems changes to the rest of their organizations. I would like to think that no one creates documentation for job security. I think you are referring to the deliverable sign-offs (as job security) which is more of an IT project management effort to protect themselves if the business says they are unhappy with the resulting software system. They can say your sign-off was on the detailed documents, and the software is built per specs. Although that may be true (and binding) – does that lead to a happy, satisfied customer? Is the project deemed successful in that case? I would say no. By the way the BA has failed in communicating clearly with the stakeholders. I think that is why agile development began with a focus on producing less documentation- "only what is necessary". Agile thought leaders say that there has been too much focus on documents and not enough on whether the customer getting the software that they need. I absolutely agree that we should only produce documentation that adds value.

]]> http://www.b2ttraining.com/2008/04/07/dinner-with-a-menu-or-without/comment-page-1/#comment-2542 Andrew Wed, 07 May 2008 10:01:24 +0000 http://www.b2ttraining.com/page/business-analyst-blog/archives/132/dinner-with-a-menu-or-without#comment-2542 From my experience, normally the user is the party who keep chasing after documentations. They treat documentation as important as the system and must be ready before the system ready. Documents like system and functional specs, design details, data dictionary, user guide, deployment guide etc are used by them to safe guard their job, where any discrepancy between the system and business needs, those documents are the judges. In fact these documents are important for the development team too as proof of requirements sign off. From my experience, normally the user is the party who keep chasing after documentations. They treat documentation as important as the system and must be ready before the system ready. Documents like system and functional specs, design details, data dictionary, user guide, deployment guide etc are used by them to safe guard their job, where any discrepancy between the system and business needs, those documents are the judges. In fact these documents are important for the development team too as proof of requirements sign off.

]]>