Task: Plan Analysis Activities
Plan Analysis Activities
Disciplines: Business Analysis

Purpose

To determine the overall process that will be used to gather, classify, and document requirements.

Relationships

RolesPrimary Performer: Additional Performers:
InputsMandatory:
    Optional:
    • None
    Outputs

      Main Description

      This task describes the steps associated with the planning and monitoring of analysis activities, including:

      ·         Developing estimates for analysis tasks.

      ·         Planning how the Analyst(s) will communicate with stakeholders.

      ·         Planning how requirements will be gathered, traced, and prioritized.

      ·         Determining the deliverables that the Analyst(s) will produce.

      ·         Determining the processes that will be followed.

       

      The analysis approach should describe the overall process that will be followed to perform business analysis work on a given project. How and when tasks will be performed, the techniques that will be used, and the deliverables that will be produced. In most instances this will already be decided, however depending on the complexity of the project, additional steps or documentation may be necessary. Review the analysis steps and documentation and determine if additional steps are required for the specific project you are working on.

      Part of planning the analysis activities is determining with the team how the project will be ran. This will determine how the requirements will be gathered; Waterfall vs. Agile.

      Steps

      Determine Timing of Analysis Work
      Determine when the analysis efforts should occur, when tasks need to be performed, and if the level of analysis effort will need to vary over time. This includes determining whether enterprise analysis, requirements analysis, solution assessment, and validation activities will be performed primarily in specific project phases or iteratively over the course of the project.
      Determine Formality and Level of Detail for Deliverables
      Determine whether requirements will be%EOL%delivered as formal documentation or through informal communication with stakeholders, and the appropriate level of detail%EOL%that should be contained in those documents. The Requirements Management Plan identifies which deliverables are required%EOL%and which are to be completed if necessary.
      Determine Prioritization Process
      Determine how requirements will be prioritized and how those priorities will be used to define the solution scope. Methods%EOL%of prioritizing requirements can be found below in Guidance.
      Determine Change Procedures
      Determine how changes to requirements will be handled. Consider the expected likelihood and frequency of change and ensure that the change management process is effective for those levels of changes. Once the requirements document is signed off on by the Sponsor and the project is handed off to the Designer, all changes to requirements should be tracked and logged in the PPM tool.
      Determine Communication Method(s) with Stakeholders
      Communications may be written or verbal, formal or informal. Decisions must be made at the outset of the project as to the applicability of such communications technologies, such as email, with regards to project decision making and approval of deliverables.
      Determine Project Complexity

      The complexity of the project, the nature of deliverables, and the overall risk to the business need to be taken into consideration. The factors listed below, among others, increase the complexity of analysis efforts as they increase:

      • Number of stakeholders.
      • Number of affected business units.
      • Number of systems affected.
      • Amount and nature of risk.
      • Uniqueness of requirements.
      • Number of technical resources required.