"When two men in a business always agree, one of them is unnecessary."
William Wrigley, Jr.




ENSURING BUSINESS REQUIREMENTS ARE DELIVERED
 
 

While the primary tasks of Business Analysts take place during the analysis phase of projects, their job is not complete when the requirements are signed off. As the project moves through design, realization and implementation, the role of the Business Analyst remains crucial to the ongoing success of the project.

It is often the Business Analyst who must ensure:

  • The business requirements are transformed into solutions and don’t become shelfware or mere “suggestions” for the teams designing, constructing and implementing the solutions to use (or not to use) as they see fit.
  • The technology (and other) solutions remain true to the needs of the organization and focus on true functionality rather than the “sizzle” of features that have minimal business impact.
  • When trade-offs must be made between the desired business functionality and vanilla software functionality, the appropriate decisions are made as business decisions.
  • The training, promotion, and other roll-out activities take place to make sure solutions are not just on-time and on-budget, but actually in-use and delivering results.

Course Outcomes:
Students of this course will return to work:


  1. Recognizing the important roles and responsibilities in the “back-end” of projects.
  2. With techniques and instruments for ensuring that as solutions are delivered the business operations align with the organization’s strategy and the technology aligns with the business.
  3. Focused on work-product transformation for using business requirements to drive design and implementation.

Course Outline:
The Role of the Business Analyst (and Others)
  • During Definition
  • During Analysis
  • During Design
  • During Realization
  • During Implementation
  • Post Implementation
Overview of Solution Selection
  • Go/No-go: Evaluating the Business Case
  • Developing an RFP
  • Stakeholders & Consensus
  • Functions vs. Features
  • Elimination vs. Selection
  • When to Address Costs
  • Working with Vendors
The Selection Process
  • Major Selection Steps
  • Narrowing the Field
  • Evaluations
  • Selection Matrices
  • Site Visits and Demos
When the Software Functionality is Not a Perfect Business Fit
  • Overall approach to gap analysis
  • Pros/cons of the “vanilla” approach
  • Pros/cons of full customization
  • Making the business decision
  • Importance of “As-Built” Models
Testing
  • Quality control vs. quality assurance
  • Phased verification & validation
  • System testing
  • Intention testing
  • User acceptance testing
Business Driven Roll-Out
  • Traditional Views of Roll-Out
  • Terminology
  • Perspectives in Life-cycle
  • Characteristics of a Successful Roll-Out
Effecting Culture Change
  • Identifying Anticipated Challenges
  • Analyzing Stakeholders
  • Creating Strategies for Overcoming Actual Losses
  • Developing & Delivering Messages
Implementation Activities
  • Monitoring conversion, migration, installation, decommission, activation, etc.
  • Training business staff
  • Transitioning to Production
Post-Implementation
  • Post-implementation review
  • Consolidation of lessons learned
  • On-going support

Who Should Attend:
Business Analysts

Course Duration:
Two Days

Class Availability: Request It Now!

 

Home |  About Us |  Key Services |  Problems Solved |  Resources |  Contact Us
Copyright © 2017 Advanced Strategies, Inc.
Feedback and Suggestions