Results (
Vietnamese) 1:
[Copy]Copied!
Define and Scope Business Areas The BA must be sure that the project scope is clear and complete before the start of detailed requirements gathering. The BA may be given the scope pre-defined by the project sponsor or may be responsible for defining and documenting the scope as part of the requirements gathering task. Defining and documenting the project scope requires the BA to understand why the project has been initiated, and the objectives of the project. An important contribution of the BA to the project is the analyzing of the business problem without "jumping" to a solution. In addition, a complete project scope will name and define all the stakeholders that will be involved with the project, including people, systems, internal departments, and external organizations. Other important components of the project scope documentation include the project viewpoint, project assumptions, and business risks. These components give the BA the information necessary to prioritize and focus the requirements gathering. Finally the project scope should include a high-level description of the business processes. It may also include a list of items that specifically will not be included in the scope. This gives the entire project team a complete understanding of the work that the BA will be doing during the detailed requirements gathering phase. One additional task required of the BA, is the creation of an organized system for maintaining project information. A glossary should be started along with a filing system for maintaining all of the information that will be gathered during the project. Essential Skills Required: Facilitation skills to bring multiple groups together to scope project and get consensus Ability to document the project scope using business terminology Project scope documentation techniques
Being translated, please wait..
