Hi. What is the key difference between a Business ...

Discussion in 'Other Project Management Courses' started by Joe Antun Mithun V Rayen, Aug 24, 2017.

  1. Joe Antun Mithun V Rayen

    Joined:
    Jul 20, 2017
    Messages:
    1
    Likes Received:
    0
    Hi. What is the key difference between a Business Requirement and Stakeholder Requirement? My understanding is that the BR is something which is required for the stakeholder to meet his objectives so ideally both of this should be the same. Thoughts anyone?
     
    #1
  2. Priyamwada

    Priyamwada Well-Known Member
    Simplilearn Support

    Joined:
    Dec 10, 2015
    Messages:
    757
    Likes Received:
    90
    Hi Joe,

    We have received your query and forwarded it to our Subject Matter Expert.
    Kindly allow us sometime while we revert with an update.

    Happy Learning!!
    Priyamwada Singh - Global Teaching Assistant
     
    #2
  3. Priyamwada

    Priyamwada Well-Known Member
    Simplilearn Support

    Joined:
    Dec 10, 2015
    Messages:
    757
    Likes Received:
    90
    Hi Joe,

    Kindly find the response by our trainer:


    "For the purposes of the BABOK® Guide, the following classification schema describes requirements:

    Business requirements:statements of goals, objectives, and outcomes that describe why a change has been initiated. They can apply to the whole of an enterprise, a business area, or a specific initiative.

    Stakeholder requirements:describe the needs of stakeholders that must be met in order to achieve the business requirements. They may serve as a bridge between business and solution requirements.

    Solution requirements:describe the capabilities and qualities of a solution that meets the stakeholder requirements. They provide the
    appropriate level of detail to allow for the development and implementation of the solution. Solution requirements can be divided into two sub-categories:
    functional requirements:describe the capabilities that a solution must have in terms of the behaviour and information that the solution will manage, and
    non-functional requirementsor quality of service requirements: do not relate directly to the behaviour of functionality of the solution, but rather describe conditions under which a solution must remain effective or qualities that a solution must have.

    Transition requirements:describe the capabilities that the solution must have and the conditions the solution must meet to facilitate transition from the current state to the future state, but which are not needed once the change is complete. They are differentiated from other requirements types because they are of a temporary nature. Transition requirements address topics such as data conversion, training, and business continuity.

    Please let me know, in case of any concerns.

    Regards,
    Vaibhav Pandey."
     
    #3
  4. _26261

    _26261 New Member

    Joined:
    Mar 16, 2018
    Messages:
    1
    Likes Received:
    0
    I may be wrong but in simpler terms I think business requirement deals with business goals and objectives. It is from a strategic level/bigger picture of things and not at the project level. For example, a business requirement may be to grow in sales by 50% by the end of the year. Stakeholder requirements are at the project level, where the stakeholder needs are required. This could be high level stakeholders/decision makers (at the tactical or the "how" stand point) or the lower level stakeholders (at the operational stand point). For example it could be a decision on the type of SDM to apply or it could be a decision of the addition of some functionalities in a software.
     
    #4

Share This Page