Chapter 3: Scoping the business problem
Chapter 3
Scoping
the business problem
Question 1. What is naming conventions and definitions for a project and how it is important?
Answer Every project has unique names that are particular to it and these names are recorded to make the communication smoother and easier between the stakeholders and team members. In every project at the scoping time names are collected and recorded and it is ensued that everyone involved in the project should be agreed on these naming conventions. It is very important that every project should have effective names as it helps to lead a smoother communication and reduce the misunderstandings that often happen in communication.
Question 2. What are project constraints and how it is important for a project?
Answer Every project has unique names that are particular to it and these names are recorded to make the communication smoother and easier between the stakeholders and team members. In every project at the scoping time names are collected and recorded and it is ensued that everyone involved in the project should be agreed on these naming conventions. It is very important that every project should have effective names as it helps to lead a smoother communication and reduce the misunderstandings that often happen in communication.
Question 2. What are project constraints and how it is important for a project?
Answer Project constraints is something that restricts the
actions of the project team and or put terms and conditions on the work. It
includes several areas in the project, but it mainly includes time, scope, cost
of the project. Project constraints is very important to be known during the
scope management time of the project because it highly impact each and every
activity of the project majorly the requirements gathering process of the project.
For example, if you have a budget of 1 million, it is meaningless to gather the
requirements for 5 million product or service. Therefore, it is highly
important to point out the constraints of the project while managing the scope
of the project because at the later stage it is quite difficult to put the
constraints to the project and follow of the project team.
Question 3. How finding a stakeholder for a project at scoping time is important for project success.
Answer It is highly important to find the stakeholders at
the scoping stage of the project, at the scoping stage there should be a
brainstorming session to determine the stakeholder for the project and a
spreadsheet is a better way to collect all the information about the stakeholders
and it cross references to the stakeholder map and provide the detailed information
about the project. After identifying all the key stakeholder for the project,
it is quite valuable to hold meeting with them in order to consult with them
and tell them why we are considering them as a stakeholder for their project
and the major concern is stakeholder must be a part of the requirement
gathering process of the project.
Question 4. What a negative stakeholder means? how important it is to identify them for a project?
Answer Negative stakeholders are the people who do not co
operate to succeed the project or having less interest in project success.
Although they have negligible interest in the project activities and project success,
but it is quite important to identify them as they might threaten your project’s
product and service. For example, for
developing a website project hacker are the negative stakeholders and it is important
to consider them wisely otherwise they will mistreat your project product and
service.
Question 5. How cultural interest influence product or service launching in other countries?
Answer Products indented for public domain is highly
influenced by the cultural interest. This is often seen when a product is sold
or launched in other countries. You need to be considered the representatives
of the groups as stakeholder of your product or service if your product and service
affected the political, religious, gender, cultural or other human interests of
any group of the community.
Constraints (which appear in the early part of the requirements specification
ReplyDeletetemplate) are global requirements. These restrictions help determine which
subset of requirements can be included in the eventual product. Constraints
affect decisions about the scope of the product by limiting the amount of
time or money that may be spent on the project. Sometimes the constraint
is a pre-ordained design decision that limits the way the problem is solved.
In this chapter, we once again encounter the formality guide but this time they are about the deliverables of each size of the project (rabbit, horse and elephant). We have known the importance of the blastoff deliverables in any projects which relate to its size or aspirations for informality. The level of formality business analysts implement to the blastoff deliverables differs, and they should have had significant attention.
ReplyDeleteOne concern when scoping the business problem that a business analyst should focus is the cultural interest in different countries. A project might be successful in the context of this country but in another country it may fail due to many factors which cultural interest can be one of the reasons.
In every project, naming conventions play a significant role as a name is everything how people identify a project. The possible names for a project are collected and recorded, and when people agree on a particular name, the project is then given a name. It's all about naming conventions. Aside from this, project constraints are another consideration as they have great impacts on requirements gathering process of the project. The major constraints of a project are known as triple constraints which consists of constraints like time, cost and scope. It's much better to identify the possible constraints of a particular project in the first phases, otherwise they can lead to the project failure.
ReplyDelete