Business Analysis Planning and Monitoring

Nota:

• To define the approach that would have to be adopted for conducting Business Analysis • Processes to be followed • Tasks to be performed • Techniques to be adopted • Deliverables to be produced    

1. Approaches

   Nota:

   • Areas to Consider Documentation, Changes,            Communication   
   1. Plan Driven

      Nota:

      • Solution is fully specified before beginning technical work (waterfall)    
   2. Change Driven

      Nota:

      • Solution is specified in increments as the technical work proceeds (agile)    
   3. Techniques
      1. Start

         Nota:

         • Decision Analysis • To compare the different approaches available and  adapt the most suited one    
      2. During

         Nota:

         • Process Modelling   Structured Walkthroughs    
2. Input
   1. Output

Nota:

• -To identify user stakeholders –  To determine the roles and responsibilities in their business area–  To determine their level of interest in the project and their influence on the project    

1. Complexity

   Nota:

   • Complexity of Stakeholder Groups –  Direct end users–  Users affected indirectly through interfacing business processes and automated systems    
2. Attitude

   Nota:

   • Attitude (will dictate interest in the project) and Influence  
   1. Attitude or Interest

      Nota:

      • Classify stakeholders as –  challengers–  enthusiasts–  Followers  
   2. Influence

      Nota:

      •       Classify stakeholders as –  Very high–  Medium–  Low 
   3. Map & Decide

      Nota:

      • - Map the stakeholders in a suitable matrix                   –  Decide on strategy for each stakeholder    
      1. Stakeholder Involvement
         1. RACI Matrix

            Nota:

            • Responsible – does the work Accountable - decision maker for work Consulted - during work Informed - notified of outcomes    
3. Techniques
   1. Start
      1. Stakeholder Mapping
      2. RACI Matrix
   2. During
      1. Organisation Modelling
      2. Process Modelling
   3. Input
      1. Output

Nota:

• To determine activities to be performed and how these have to be done –  To determine the deliverables to be produced–  To determine the effort for each activity and the timeframe allowed to complete that activity –  To decide on the management tools that will aid in monitoring and controlling progress    

1. Considerations
   1. Locations

      Nota:

      • Location of the Stakeholders – Collocated • Lendsitselftoface-to-facemeetings – Dispersed • Have to decide on teleconferencing or video conferencing;will require additional and extensive documentation and therefore these will add additional activities    
   2. Type

      Nota:

      • Type of Project / Initiative influences the activities to be carried out    
      • Feasibility studies; process improvements; organisational change; new software development (in house); outsourced new software development; software maintenance and enhancement; software package selection etc.    
   3. Deliverables

      Nota:

      • Depends on what BA Methodologies / Techniques that are required to be used; these may include    
      • - Process and functional Modelling Techniques • Behavioural Modelling Techniques • Structural Modelling Techniques • User Stories (in an Agile environment)    
2. Techniques
   1. Estimating Techniques
   2. Functional Decomposition
3. Input
   1. Output

Nota:

• o make the Right Business Analysis Information available in the Right Format to the Right Stakeholder at the Right Time using the Right Means and Right Media in a Cost Effective manner.    

1. Considerations
   1. Geographical location

      Nota:

      • Communication requirements will vary depending on the  geographical location e.g. Not possible to have a daily short stand-up meeting when participants are in different time zones    
   2. Culture

      Nota:

      • - Language barriers           –  Time: some cultures look at deadlines as firm commitments while  in some other cultures deadlines are considered as goals to achieve–Taskcompletion requirestrustandhumanrelationship          –  Contracts–letterofthelaworspiritofthecontract–  Formal and informal authority – centralised power structure vs involve all stakeholders in making and approving decisions    
   3. Project types

      Nota:

      • New customised software development project – Requires all requirements to be specified in sufficient detail  • Upgrading technology infrastructure of a current system – Requires only the technical requirements to be included  • Change in business process or new data for an existing application – Requires the new process, data, business rules, functional and technical requirements  • Purchase of a Software Package through a RFP – Requires the specifications for business, technical and functional requirements  • Short focussed agile style iterations of software development   –  Specify very little or no formal requirements documentation –  Uses white boards, flip charts and user stories –  Focus in Agile is in creating minimum documentation during the progress of the project  –  Documentation is produced after the solution is delivered     
2. Techniques
   1. Information Requirement Analysis

      Nota:

      • Technique to analyse the information required by each stakeholder based upon his / her role and responsibility    
   2. Input
      1. Output

Nota:

• deals with managing the process of business analysis    
• - to ensure BA plans are adhered to • to ensure the resources, tools and techniques required for carrying out business analysis are made available    

1. Considerations
2. Techniques

   Nota:

   • - Decision analysis • Problem tracking • Risk analysis    
   1. Input
      1. Output

Nota:

•       – To measure using an appropriate metric the work performed by the Business Analyst – To track, assess and report on the quality of work performed by the Business Analyst    

1. Considertion
2. Technique
   1. Input
      1. Output