Saturday, October 3, 2009

Stakeholders where art thou ?

This weeks blog is short by crucial , starting the assignment but my understanding of the requirements is abit fuzzy. The stakeholder's MO, there business operations, the supporting meta data, and the actual requirements are .. well … best described as little vague. Does this really impact the assignment? No, Not really. What I have found however is that I will have a list of disclaimers (assumptions and interpretations) in the report. Ideally I would have clarified all of these with business, however this isn't necessarily something I can obtain in this scenario. Additionally a series of mock-up (designed in paint or excel) with no dummy data would have been presented to the users to gauge what they want.

Guessing what business wants and developing a fully functional prototype is a recipe for failure. The problem with this approach is that:

  • The BA invests time in a product that the end user may not want.
  • The stakeholder can loose confidence in the BA as they can perceived the guess as left of centre.
  • The stakeholders can become focused on the figures produced rather than designing a solution that can support the decisions making processes.

No comments:

Post a Comment