Visão Geral

Este curso define as atividades do Business Analyst desde a identificação de um problema de negócios a ser resolvido até a implementação final da solução para esse problema. O papel do Business Analyst é definir o problema, identificar a solução e gerenciar o produto por meio do System Development Life Cycle. O curso enfatiza as principais responsabilidades do Business Analyst na definição dos requisitos para o produto, ao mesmo tempo em que aborda as questões importantes de comunicação e garante uma solução de qualidade.

Objetivo

Ao final do curso, você aprenderá a:

• As funções e responsabilidades do Analista de Negócios
• O conceito de requisitos e sua importância para o desenvolvimento de sistemas de qualidade
• A diferença entre coletar informações e gerar requisitos
• A importância de definir primeiro o problema
• Um processo para transformar informações coletadas em requisitos de qualidade
• Como comunicar com as comunidades empresariais e de desenvolvimento, negociar e facilitar um projeto bem-sucedido
• Os processos de desenvolvimento para transformar requisitos em uma solução
• Os fatores que contribuem para confirmar que a solução entregue resolve o problema de uma forma aceitável para as partes interessadas

Publico Alvo

• Analistas de negócios, gerentes de projeto e qualquer pessoa responsável por converter um problema de negócios em uma solução de TI bem-sucedida.

Informações Gerais

FORMATO:

• 100% On-Line na presença de um instrutor/consultor ativo no mercado e docente em sala de aula.
• In-company.
• Presencial.

PERÍODO:

• Noturno em noites intercaladas exemplo: terça-feira e quinta-feira das 19h às 23h,total de 4h por encontro.
• Aos sábados das 8h às 12h, total de 4h ou das 09h às 18h, total de 8h.
• Integral consultor disponibilidade

LAB:

• Apostila
• Laborátorio individual
• Exercícios práticos

Conteúdo Programatico

Overview

• The Business Analyst (BA)
  1. Roles and Responsibilities
  2. Objectives
  3. Relationship of IT to Business
• Business Analyst Relationships
• Role of an Intermediary
  1. Communication Specialist
  2. Facilitation
  3. Mediation
  4. Potential Problems
• Define the Requirements to Solve the Problem
  1. Definition of Terms
  2. Purpose of Requirements
  3. Requirements Process
• The BA’s Role Throughout the System Development Life Cycle
• Unit Summary and Best Practices

Information Gathering Plan

• Information Gathering Process
  1. Six Stages of Information Gathering
  2. Research Questions
  3. What Information Is Needed
• Where Is the Information Located?
  1. Problem Domain
  2. Stakeholders Defined
  3. Users Defined
• Methods of Information Gathering
  1. Forms of One-On-One Information Gathering
  2. Requirements Sessions
  3. Brainstorming
  4. Observation
  5. Demonstration
• Workshop: Building an Information Gathering Plan
• Unit Summary and Best Practices

The Product Scope

• Defining the Problem
  1. Components of the Problem
  2. Basic Problem Definition
  3. Identifying the Real Problem
  4. Establishing the Product Vision
• Workshop: Defining the Real Problem
• Business Orientation
  1. Justification
  2. Impact Analysis
  3. Risk and Product Constraints
  4. ROI Analysis
  5. Cost / Benefit Analysis
  6. Tangible and Intangible Benefits
• Establishing Product Scope
  1. Functional Goals
• Estimating: Round One
  1. Estimating the Cost of the Product Scope
• Unit Summary and Best Practices

Information Gathering Techniques

• Gathering Information
  1. What Information to Gather
  2. Iterative Information Acquisition
• Interview Approaches
  1. Management
  2. Stakeholder
• Interview Techniques to Get the Most Information
  1. Five Stages of an Interview
  2. Preparation
  3. Using the Problem Definition
  4. Establishing Rapport
  5. Be Receptive
  6. Inquire Skillfully
  7. Getting the Most Information
  8. Listen Loudly
  9. Listen Actively
  10. Other Interview Considerations
• Information Gathering Tips and Techniques
  1. Meetings
  2. Brainstorming
  3. Use Cases
• Unit Summary and Best Practices

Requirements Analysis

• Analyzing Requirements
  1. What to Do with the Information
  2. Defining the Problem Environment
  3. Using the Problem Definition
  4. Classification
• Modeling
  1. Purpose of Modeling Requirements
  2. Modeling Options
  3. Modeling Results
• Requirements Classification
  1. Requirements Classification Summary Trade-Offs
  2. Requirements Progression
  3. Classes of Requirements—Overview
  4. Tips on Classifying Requirements
  5. Prioritizing Requirements
  6. Quality Issues
• Gap Analysis
  1. Functional Goals
  2. Deriving the Functional Requirements from the Gap
• Workshop: Producing Requirements
• Unit Summary and Best Practices

Requirements Documentation

• Requirements Document Contents
  1. Organizing the Document
  2. Document Structure
• Requirements Representation
  1. Documentation and Specification
  2. Functional and Systems Requirements
  3. Quality Requirements Definition
• Requirements Documentation Guidelines
  1. Writing Valid Requirements
  2. The Structured Approach
  3. Good Requirements Form
• Workshop: Documenting Requirements
• Unit Summary and Best Practices

Requirements Communication and Approval

• Communication
  1. Requirements Confirmation Methods
  2. Communication and Information
  3. Presenting the Results
  4. Facilitating the Confirmation Meeting
  5. Confirmation Process
• Validation
  1. Inspection Overview
  2. Inspection Process
• The Purpose of Approval
• Approval and Sign Off
  1. Formal Approval
  2. Alternatives
• Negotiation
  1. Negotiating with Customers/Users
  2. Negotiating with Developers
  3. Collaborative Negotiating
  4. Handling Conflict
• Unit Summary and Best Practices

Managing Product Quality

• Designing the Requirements
  1. Development Integrity
  2. Maintaining Quality
• Traditional Life Cycle Approach
  1. Requirements to Design
  2. Designing the Requirements
  3. Analysis and Design
  4. Logical and Physical Design
  5. Constraining the Design
  6. Trade-Off Issues
  7. Mapping Requirements to Design
• Agile Just in Time Requirements
  1. User Stories
  2. Epics and Themes
  3. Product Backlogs
  4. Grooming and Managing
• Requirements Management
  1. The Problem
  2. The Need for Requirements Management
  3. Change Management
• Tracing the Requirements
  1. Requirements Traceability
  2. The Traceability Matrix
  3. Traceability Example
  4. Multilevel Traceability
• Unit Summary and Best Practices

Confirming a Quality Product

• Creating the Test Plans and Cases
  1. Testing the Requirements
  2. Writing Test Cases from Requirements
• Test Stages
  1. Unit Test Cases
  2. Integration Test Procedures
  3. System Test Scenarios
  4. Acceptance Test Methods
• Unit Summary and Best Practices

The Bottom Line

1. The Business Analyst Process
2. Where to Go for More Information