The document provides hints and tips for business analysts (BAs) on various stages of a project. It discusses important considerations when first assigned to a project like ensuring clear objectives and identifying an executive sponsor. It emphasizes the importance of planning before starting a project to avoid failure. Specific planning elements mentioned include stakeholder analysis, developing a business analysis workplan and allocating sufficient time to requirements discovery. During a project, the document notes things BAs should focus on like workshops, mentorship and requirements reviews. It also flags things to watch out for such as assumptions about domain knowledge. After a project, it discusses sign-off challenges, conducting post-implementation reviews and learning lessons around requirements quality and defects.

1. ©
Hints and Tips for the BA?
Robin Grace
Principal Consultant
Business Analysis Practice
All material in this presentation is, unless otherwise stated, the property of
IndigoCube. Copyright and other intellectual property laws protect these
materials. Reproduction or retransmission of the materials, in whole or in part,
in any manner, without the prior written consent of the copyright holder, is a
violation of copyright law.
Contact information for requests for permission to reproduce or distribute
materials are listed below:
info@indigocube.co.za

2. Agenda
• When you are assigned to a Project
• Before you Start a Project
• During The Project
• After the Project

3. When you are assigned to a Project
Most projects fail before they are started,
because of poor objectives.

4. When you are assigned to a Project
Project Objectives
• Time frames
• Measurable
• Business Value
P=R-C
Why is this project being done?

5. When you are assigned to a Project
Executive Sponsor?

6. Before you Start a Project
No Planning, is planning for failure.

7. Before you Start a Project
Planning
One Size Does Not Fit All
Stakeholder Analysis (RACI)
Business Impact
Business Analysis Workplan
Not enough Time Allocated to the
Requirements Discovery Process

8. Before you Start a Project
Stakeholder
Stakeholder
Stakeholder
Analysis
Stakeholder
Analysis
Stakeholder
Analysis
Worksheets
Analysis
Worksheets
Analysis
Worksheets
Worksheets
Worksheets
Project
Overview
Worksheet
Deliverable
Deliverable
Deliverable
Worksheets
Deliverable
Deliverables Worksheets
Deliverable
Worksheets
Worksheets
List Worksheets
Business
Impact
Worksheet
Business
Summarized PM Project
Analysis
Plan (WBS)
Work Plan

9. Before you Start a Project
The Result of Good Planning
What
When
Who
Why
How
Result
Not enough time allocated to the
requirements discovery process

10. During The Project
Things You We Aren’t Doing Enough
•Workshops
•Mentorship
•Peer Reviews
•Requirements Reviews

11. Things to Look Out for During The Project
• What is a System ?
• Understand What a System is
 Business Rules Wrap in Technology

12. During The Project

13. Things to Look Out for During The Project
• Domain Knowledge Assumptions
• Not Involving the Technical Team Early
• Mixing Solution Requirements with
Business Requirements

14. After the Project
Sign Off Blues
Post Implementation Review
Lessons Learned
What caused the Defects
Where the Requirements Weren't Good
Enough

15. Questions
The IndigoCube Business Analysis Practice is committed
to assisting clients to perform Business Analysis better
through solutions in
Business Analyst Assessment
Methodology Provisioning
Creation
Customisation
Implementation
BA Skills Development
Contact information info@indigocube.co.za
robin@indigocube.co.za