The document outlines an agenda for a vision and scope discovery workshop over 4 days. The workshop aims to establish a common understanding of objectives, pain points, scope, and requirements. Key activities include setting SMART business objectives, analyzing process pain points and themes, developing a context diagram, and establishing scope inclusions and exclusions. Breakout groups will work to define requirements, user stories, and draft process mini-specifications. The workshop concludes with evaluating progress made and planning for quality review.

1. 
High performance teams
collaborating to achieve great things
Vision & Scope Discovery
Strategy Analysis

2. 
Vision & Scope Workshop Agenda
Workshop Module Comment Date Duration
Coffee for 9:00 am
1. Introduction – Business Analysis
 Overview - Requirements Analysis Plan & Approach
 Handouts
Presentation 1.5
2. Vision for the future - Begin with the end in mind…
 Business and project objectives
 Classify project objective
 Describe business & project objectives
10-20 SMART business & project objectives Day 1 - 3-4 hours
3. Analyse process pain points
 Focus on pain point identification and prevention
 Describe pain point impact summary
~80 issues grouped into ~10 themes
Evaluate 12 themes business impact
Hand outs: Business objectives
Day 2 - 3-4 hours
4. Develop context diagram & scope definition
 Prepare context diagram
 Confirm business processes
 Verify actors / personas
 Verify data subjects
 Verify existing Systems
 Identify scope inclusions & exclusions
 Elicited Requirements
7-9 Product Lists, i.e.
~10 information flows
7-9 business process
~10 personas
5-7 data subjects
~30 legacy systems (heat map)
~10 inclusions +~10 exclusion
~30-70 user stories
Day 3 - 3-4 hours
3-4 hours
5. Establish a common process understanding
 Describe process, activity list and metrics
 Revised information flow, persona, systems, data
subject catalogue descriptions
Breakout Teams
~7-9 backlog catalogues revised
Day 4 - 3-4 hours
6. Evaluate Progress Evaluation forms 15 mins
8. Quality Review 3 -5 days after product distribution ¼ Day - 2 hour
2
Notes:
1. ~ Approximately

3. 
Dimensions of Scope
• A statement of the business problem to be solved. The statement needs to cover the following
dimensions;
Products: The range of products that need to be supported.
Organisation: The departments affected by the new solution.
Process: A description of the functional scope .
Capabilities: The strategic business capabilities expected / outcome desired.
Geographic: The global coverage of the solution.
Interfaces: The internal and external information flows that need to be supported.
Conversion: The existing systems to be decommissioned on successful completion of the project.
• A clarification of the items that are excluded from the scope to clear understanding to the
items out of scope have been stated.
• A list of any specific financial conditions or constraints that need to be taken
into account.
Scope defines the project boundaries, setting the expectations which determine the level satisfaction and
degrees of success. It provides the authority of the work undertaken and the basis for managing change.

4. 
Vision for the future
Begin with the end in mind…
1. Breakout teams
2. What is my vision for the future?
3. If my vision succeeds, how will I differ?
4. What are my critical success factors?
5. What are my critical measures?

5. 
Objectives - Four Perspectives
6
Financial Perspective Client Perspective
Internal Business Process Perspective Learning Perspective
Vision & Priorities
If my vision succeeds, how will I differ?

6. 
Pain Point Root Cause Analysis
1. Breakout teams
2. Pain Point Identification
3. Pain Point Themes
4. Pain Point Root Cause Analysis

7. 
Existing Process Pain Points
1. Root Cause
• Pain Points
2.
•
3.
•
4.
•
5.
•
6.
•
7.
•
8.
•
9.
•
10.
•
?

8. 
Context Diagram
1. Identify business events
2. Classify event response priorities
3. Identify the information flow
4. Name the supplier of information
5. Name the process response
6. Pinpoint pain point impact areas

9. 
Context Diagram
Why Statement – Concise statement of the problem and why the project must be undertaken in a sentence.
1Dollar
Process Data
?
?
?
?
?
?
?

10. 
Scope Inclusions & Exclusion
Inclusions
• Capability
BENEFIT: xxxx
Exclusions
• Item
IMPLICATION: xxxx

11. 
Requirements
1. Breakout Teams
2. Brainstorm requirements on a
post-it notes
3. Evaluate and verify final list
Footer 13

12. 
•User Stories
2.
•
3.
•
4.
•
5.
•
6.
•
7.
•
8.
•
Requirement Story Map
14
Process
Activity
Strategy
Business Objective
Business Process

13. 
Establish Common Understanding
1. Breakout Teams
2. Mini-specification templates
3. Draft mini-specifications
Extending the label…
to communicate meaning in 1-2 sentences

14. 
Mini-Specification Example
Business Objectives
Date: Analyst:
BO ID: Owner:
Objective
What the project is aiming to achieve?
Each objective must establish a clear, concrete target that must be accomplished in a specific time frame that is attainable;
Specific clear, concrete statement of direction
Measurable
Must be Achievable
Results oriented
Time bound
Output:
What the project will actually deliver?
Outcome:
What the organisation will gain from the project’s output?

15. 
Scope Dimension Priorities
Survey Forms
1. Events an Information Flows
2. Actor/ Personas / User Class
3. Processes
4. Subject Areas
5. Existing System
6. User Stories
7. Product Release Options

16. 
Process Design Prioritisation
Process
ProcessHealth
MosCowPriority
Product1
Product2
Product3
Product4
Product5
Product6
Product7
Product8
Product9
New Service Registration
Service Data Transmission Testing
Collection Data Acquisition & Validation
Service Compliance Monitoring
Data Quality Monitoring
Data Collection Consolidation
Information Requests Management
Collection Specification Change Management
Data Warehouse Operational Support
Column Values Ranking Description
Process Health U,I,S,G,E Unsatisfactory, Needs Improvement, Satisfactory, Good, Excellent
Project Priority M,S,C,W Must Have, Should Have, Could Have, Would Have
Product  or Blank  = Included in product scope, blank = not in product scope

17. 
Summarise & evaluate progress
1. What visual images, statements or themes stood out during
the discovery workshop?
2. What where the highs and lows of the workshop?
3. How do you feel this workshop output conveys the teams
requirements?
4. What is the greatest insight discovered during the workshop?
5. Thinking about the path we have travelled over the last few
days, where would you look to improve this process so we can
be more efficient and effective in realising our project goals,
and objectives?

18. 
Recap: Vision & Scope Products
1. The five minute rule, where only five minutes will be
spent discussing each issue. When five minutes is up
the discussion topic will be noted as an issue for later
resolution. A participant may be identified to resolve
the issue prior to the next workshop.
2. No ideas should be criticised. If a participant is
unhappy or disagrees with an idea, they should offer
an alternative to the team for consideration.
3. Carry out assignments on schedule.
4. Avoid actions that delay progress
5. Don't give solutions give causes first.
6. Praise every improvement no matter how little.
7. Respect other participants time by being punctual.
8. Keep an open mind and look for merit in the ideas of
other team members.
9. Every workshop team member is responsible for the
team's progress and what they attain from the
experience.
designer DATA
Vision & Scope
1. Business objectives setting project direction
• Management confirmation
• Project direction
2. Pain points to help resolve
• Visibility of operational issues
• Project direction
3. Context Diagram
• Scope
• Customer Interactions
• Common understanding of the whole
4. Inclusions and Exclusions
• Agreed capabilities that add value
• Ground not covered confirmed

19. 
Quality Review
1. Assess product against the completion
criteria
• Understandable
• Testable
• Flexible
• Traceable
• Standards compliance
• Complete
2. Record review results on evaluation
form noting the reasons for your results
3. If you disagree with any content be
prepared to offer an alternative

20. 
How to get there?
Technology architecture & solutions are justified at a strategic and financial level by
preparing a business case.