Price: $3,999.00

Length: 3 Days
Print Friendly, PDF & Email

Mobile Applications Business Analysis Course Description

Mobile Applications Business Analyst Training Course provides skills and roadmaps for initiatives supporting the planning, development and execution of mobile applications projects  though lessons, theory, practical examples, case studies and group projects.

In this course, the role of the “business analyst” is defined as an intermediary managing the interests and needs of business management  project management and IT communities in mobile applications development process.

You will work with a logical framework to conduct key business analysis activities throughout the various phases of the mobile applications business analysis life cycle.

Business Analyst usually supports all aspects of the mobile applications projects from start to finish with a particular emphasis on requirements development and participation project quality activities.

Analysts involved in mobile applications development usually collaborate with Business Users, Project Managers, Product Managers, and other Business Analysts to elicit and gather requirements. The Business Analyst may occasionally serve as the project lead on smaller, well defined projects or provide support to Systems Managers in mobile project initiation activities. Business Analysts involved in mobile app development insure that all IT groups and vendors have the sufficient clarity towards requirements and appropriate detailed requirements are gathered by other groups and will be involved in requirements review; proactively speak up as well as follow up, in the event of missing requirements or gaps and ensure that these are appropriately filled.

Business Analyst responsibilities include communication conduit between the stakeholders and the mobile applications development team to represent the stakeholder community to the development team if the developers themselves don’t have direct access, and to translate the business needs for the team.

Some of the Learning Objectives for the Mobile Applications Business Analysis related to Business Analysts (BA) working on mobile apps:

  • Discover and define mobile applications requirements in the space of business goals, business needs, defining the true problem, scoping the business case for making an investment , and discovering the business process and related changes.
  •  Learn how to  provide subject matter expertise and analytical support to help facilitate mobile app projects and operations of apps
  • Understand how to play a key role in creating and executing mobile strategy for your organization and work across functional groups (eg, Marketing, IT) to coordinate efforts and ensure success.
  • Discover how to work with Customer Care and Social Media teams to ensure they have adequate training to answer customer questions related to mobile initiatives
  • Learn how to report on best practices, mobile industry standards, competitor’s products and legal requirements associated with assigned mobile app projects
  • Discover how to partner with Product Manager to provide business evaluation, revenue optimization, feature recommendations and on-going support for mobile apps
  • Understand the initiatives throughout the mobile app project life cycle; including discovery and initial assessment, program and/or requirements definition, creative brief, program implementation and launch, and ongoing measurement and reporting
  • Learn how to help integrate initiatives with internal partners in Marketing, IT, Creative, Sales, Operations, etc.
  • Work closely with  engineering, design, operations, finance, and marketing leaders to bring mobile app products to market and develop and grow business opportunities for your organization.
  • Understand how to review and supervise mobile design components
  • Learn how to create training materials and coordinate training for Customer Care and Social Media teams
  • Learn how to integrate  Interactive Marketing, Mobile and e-Business strategies, channels, technologies, principles, and processes
  • Understand how to be part of the development of the product strategy and vision for mobile app products
  • Create buy-in for the mobile app product vision both internally and with key external partners
  • Oversee the definition and management of high quality, mobile app product roadmaps based on team strategy and vision
  • Manage prioritization and trade-offs among customer experience, performance and operational support load

 

Who Should Attend

Project Managers and Business Analysts working with mobile applications. Any other team member or stakeholder involved in mobile applications development process. Business analysts including functional managers, project managers, developers and testers, may benefit greatly from this interactive training program.

 

Outline

Introduction to Mobile Applications

  • What are mobile applications?
  • Mobile applications platforms
  • Mobile applications business analysis
  • Identify business needs and determine solutions to business problems
  • Mobile applications requirements
  • Conceptual apps
  • Process augmentation apps
  • Overview for designing mobile applications

Mobile Application Development

  • Introduction to Mobile Applications Development Process
  • Functional Requirements
  • Interface Requirements
  • Performance Requirements
  • Other non-functional attributes
  • Security
  • Compatibility
  • Reliability
  • Maintainability
  • Portability
  • Extensibility
  • Reusability
  • Application Affinity/Compatibility
  • Resource Utilization
  • Serviceability
  • Operational Scenarios
  • Preliminary Use Case Models and Sequence Diagrams
  • Updated Schedule and Budget

Mobile Applications Requirements Specifications

  • Stakeholder Analysis Specification
  • Business Analysis Plan
  • Current State Analysis
  • Scope Statement
  • Functional requirements
  • Visual Specifications
  • Workflow diagrams
  • Information or Data Model Specification
  • Test Plans, Test Cases, or User Acceptance Test Plans
  • Change Management
  • Throughout the Project

Mobile Applications Development Best Practices

  • Agree on goals for the program
  • Understand your target users
  • Build a user testing focus group
  • Identify a minimally viable solution set
  • Plan for multiple releases
  • Stakeholder identification and analysis
  • Elicitation techniques
  • Affinity diagramming
  • Brainstorming activity for gathering and prioritizing business needs
  • Planning a focus group session
  • Creation of a discussion guide
  • Workflow diagramming
  • Writing business objectives
  • Understanding of the business analyst competency model
  • Methodology
  • Development Skills
  • Design
  • API Management
  • Security
  • Testing and User Experience
  • Application Analytics
  • Feedback Mechanism
  • Other things to consider before developing mobile applications

Defining  Mobile Applications Development Business Analysis

  • Overview of the business analysis discipline
  • Key roles and responsibilities
  • Business analysis framework

Mobile Application Business Analysis and Needs

  • Organizational direction, objectives, operations, processes, systems/applications and users
  • Mobile SDLC methodology framework
  • Mobile applications scope and objectives
  • Interpret business needs
  • Translating the initial high-level vision into something realistic
  • Translate conceptual business and user requirements into mobile applications functional requirements
  • Mobile apps project scope and vision
  • Constraints, dependencies, assumptions, risks and issues
  • Project stakeholders and key influencers
  • Elicit business and user requirements
  • Interviews, workshops, questionnaires, surveys, site visits, workflow storyboards, use cases, scenarios, user stories, process modeling, analysis of existing systems and documentation, and other methods
  • Requirements specifications and standard templates
  • Interpretation of requirements into feasible options, and communicate options to the stakeholders, Project managers and sponsors
  • Manage and track the status of requirements throughout the project lifecycle; enforce and redefine as necessary
  • Identify business rules 
  • Project details and requirements
  • Process models, specifications, diagrams, and charts to provide direction to solution designers and developers and/or the mobile app project team
  • Translate technical issues
  • Prototypes of interfaces and attributes based on the user requirements or assist solution designers in doing the same Test and validation
  • Changes, enhancements, and modifications of requirements according to the established process

Mobile Applications Business Analysis Process Framework

  • Capturing Business Requirements through Elicitation
  • Gathering business needs
  • Performing need analysis and assessment
  • Choosing the best elicitation technique
  • Assessing mobile business capabilities and gaps
  • Measuring the feasibility of options
  • Anticipating mobile app project benefits and costs
  • Defining and documenting critical project parameters
  • Planning and Monitoring the Business Analysis Process
  • Planning for requirements analysis
  • Assumptions, ground rules and templates
  • Communication plan
  • Performing stakeholder analysis
  • Managing the change control process
  • Executing the communication plan
  • Assessing and Validating Solutions
  • Assessing organizational readiness
  • Identifying organizational capability gaps
  • Defining business and technical organizational impacts

 

 

Request More Information

Please enter contact information followed by your questions, comments and/or request(s):
  • Please complete the following form and a Tonex Training Specialist will contact you as soon as is possible.

    * Indicates required fields

  • This field is for validation purposes and should be left unchanged.

Request More Information

  • Please complete the following form and a Tonex Training Specialist will contact you as soon as is possible.

    * Indicates required fields

  • This field is for validation purposes and should be left unchanged.