When it comes to business analysis, requirements play a crucial role in defining the success of a project. They serve as the foundation for designing and developing the desired outcome. The International Institute of Business Analysis (IIBA) has identified various types of requirements that are essential for a project’s success. In this blog post, we will explore these different types of requirements and how they are modeled.
Functional Requirements
Functional requirements describe what the system or product must do to meet the needs of its users. These requirements specify the features, capabilities, and functionalities that are expected from the solution. They are typically documented using techniques such as use cases, user stories, or activity diagrams.
For example, if you are developing a mobile banking application, functional requirements might include features like account balance inquiries, fund transfers, and bill payments. These requirements are crucial for ensuring that the solution meets the expectations of its users and delivers the intended functionality.
Non-Functional Requirements
While functional requirements focus on what the system does, non-functional requirements focus on how the system performs. These requirements outline the quality attributes and constraints of the solution, such as performance, security, reliability, and user experience.
Non-functional requirements are often critical for the success of a project, as they define the overall user satisfaction and system performance. They are typically documented using techniques like quality attribute scenarios, performance benchmarks, or usability studies.
Business Requirements
Business requirements define the needs and objectives of the organization. They provide a high-level view of the desired outcomes and help align the project with the overall business strategy. Business requirements are often captured through interviews with key stakeholders, surveys, or workshops.
For example, if a retail company wants to expand its operations to online sales, some of the business requirements might include increasing revenue, reaching a wider customer base, and improving customer satisfaction. By clearly defining these requirements, the project team can ensure that the solution supports the business goals.
Conclusion
Understanding and effectively managing requirements is essential for the success of any project. By recognizing the different types of requirements, such as functional, non-functional, and business requirements, project teams can develop solutions that meet the needs of the users and align with the overall business objectives. So, whether you are embarking on a new project or looking to enhance an existing one, make sure to give the due importance to requirements and their modeling for unlocking the path to success.
Please note: That is an “agile” world that both functional and non-functional requirements are defined as User Stories
In the dynamic world of business, the role of a Business Analyst (BA) is pivotal. They bridge the gap between IT and business needs, ensuring that projects align with strategic goals. To excel in this role, comprehensive Business Analysis Training is essential. Among the myriad of options available, the Better Business Analysis Institute (BBA Institute) stands out as the premier choice. Here’s why:
Comprehensive Curriculum: The BBA Institute offers a robust curriculum that covers all aspects of business analysis. From understanding business needs and requirements management to solution evaluation, the course ensures a holistic understanding of the BA role.
Experienced Instructors: The BBA Institute boasts a team of seasoned professionals who bring real-world experience to the classroom. Their insights and practical examples enrich the learning experience, making the theoretical concepts more relatable.
Flexible Learning Options: The BBA Institute understands the need for flexibility, especially for working professionals. They offer both online and in-person training options, allowing you to learn at your own pace and convenience.
Certification Recognition: The BBA Institute’s certification is widely recognized in the industry. It adds significant value to your resume and increases your marketability in the job market.
Interactive Learning Environment: The BBA Institute emphasizes interactive learning. Their courses include case studies, group discussions, and projects that simulate real business scenarios, fostering a deeper understanding of the subject matter.
Post-training Support: Unlike many other institutes, the BBA Institute provides post-training support. This includes access to course materials, webinars, and forums where you can discuss your queries with peers and instructors.
Value for Money: The BBA Institute’s courses are competitively priced, offering high-quality training at an affordable cost. They also offer corporate training packages, making it a cost-effective solution for organizations looking to upskill their teams.
When compared to other training providers, the BBA Institute’s comprehensive curriculum, experienced instructors, flexible learning options, and post-training support make it a standout choice. Whether you’re an aspiring BA or a seasoned professional looking to upskill, the BBA Institute offers a training solution that’s tailored to your needs.
In conclusion, the Better Business Analysis Institute is a leading provider of Business Analysis Training. Their commitment to quality education, practical learning, and ongoing support ensures that their students are well-equipped to excel in their roles as Business Analysts. Choose the BBA Institute for your Business Analysis Training and take the first step towards a successful BA career.
Get your CBBA – Level 1 today for only $550 USD ($899 NZD)
or Complete the Free Introduction to Business Analysis Course today
Kia ora Everyone, Happy Thursday! Today we are going to talk about another exciting AI diagramming tool that is more like a MURAL, Miro style whiteboarding tool. Some of the feature like process flow still be a bit of work (alpha stage) but some of the other areas will take hours off your tasks.
Jeda.ai is amazing and states that it is a “Generative Ai Online Whiteboard for Interstellar Visual Collaboration” which makes me think the name is play on the word “Jedi” and this thing can do some serious AI magic.
You can sign up for free here https://go.jeda.ai/register and: “Experience Jeda.ai Online Whiteboard with generative AI for exceptional template analysis, diagram creation, and more. Claim 10,000 free Ai Karma tokens daily and access exclusive features to elevate your projects. Embrace the future of content creation with Jeda.ai!”
So what does it do? We have been looking into the use case every Business Analysis could use this tool for. The list is long and includes:
Online whiteboard for brainstorming
AI Process Modelling
Strategic planning
Design Thinking
Here is one of the examples we tried:
We used the Ai Recipes to generate a go-to-market-strategy with the following inputs
The output was the following diagram (with some label movement need):
Not only is the content pretty damn cool (and i don’t need to format anything), I can now a share and work on this whiteboard with my team.
I think this is one to have a serious play with and please flick me any insights you find out.
Are you looking to become a successful business analyst? Look no further! In this podcast episode, Benjamen Walsh from The Better Business Analysis Institute shares valuable insights on what to look for when hiring a business analyst and how to succeed in the job search process.
Benjamen emphasises the importance of gaining experience and completing certified courses to move up to an intermediate level.
Candidates should also tailor their CV and cover letter to the specific job and company they are applying for, and showcase their personality and connection with the company in their application.
For hiring managers, Benjamen suggests having a structured interview process, including technical and culture fit interviews, and creating a job description specific to the level and job being hired for.
So, if you’re looking to become a successful business analyst, take these tips to heart and start your journey today!
How Business Analysts Can Help Companies Survive a Recession
The current financial climate has seen a recession not only in New Zealand but also overseas, leading to companies looking for ways to cut costs, restructure, and even merge to survive. Business analysts can play a crucial role in helping companies during this period by focusing on continuous improvement and business transformation.
Continuous improvement involves applying process-level improvements to reduce waste in the organization. Business analysts can help by focusing on reducing waste at the process level, making processes more efficient, and providing clarity to senior leaders about the impact of cost-cutting measures. On the other hand, business transformation involves a top-down approach where a company reflects on its business model and unique value proposition (UVP). Business analysts can assist by reviewing the company’s UVP and identifying areas where fundamental changes can be made.
During a recession, companies tend to focus on their UVP, which is what customers come to them for. This may result in turning off services that are not core to the business or not what makes them unique to their target customers. It’s important for businesses to be conservative with their spending and to look for ways to cut costs. However, this can be a difficult time for many people, and it’s important to remember that there are ways to help.
Business analysts can use their skills and knowledge to advise friends and family who may be affected by the recession, helping them to identify new career opportunities and navigate the job market. By focusing on continuous improvement and business transformation, business analysts can help companies and individuals survive and thrive during a recession.
The BBAI template library gives business analysts everything they need to deliver professional, consistent work — from requirements gathering through to solution validation. All templates are free. Use them as-is or adapt them to your project context.
The most-used templates in a BA’s toolkit. Requirements templates help you capture, document, and manage what the business needs from a solution.
Business Requirements Document (BRD)
The BRD captures what the business needs to achieve, independent of how the solution will be built. Use at the start of a project to align stakeholders before solution design begins.
Section
Content to Include
1. Executive Summary
Problem statement, business opportunity, and recommended approach (1 page)
2. Business Objectives
SMART goals the solution must achieve, linked to strategic objectives
3. Current State
As-is process description, pain points, and root causes
4. Scope
In-scope processes, systems, and stakeholder groups. Explicit out-of-scope list.
5. Stakeholders
Key stakeholders, roles, and approval authorities
6. Business Requirements
Numbered list: BR-001, BR-002… Each with priority (MoSCoW) and owner
7. Assumptions & Constraints
Known limitations, dependencies, regulatory requirements
8. Success Criteria
How the business will measure whether the solution delivered value
9. Glossary
Business terms and definitions used in this document
Functional Requirements Specification (FRS)
Translates business requirements into specific, testable functional behaviours. Used by development teams to understand what the system must do. Write this after the BRD is approved.
Field
Description
Example
FR-ID
Unique reference number
FR-001
Title
Short name for the requirement
User Login
Description
What the system must do
The system shall allow registered users to log in using email and password
Source
Business requirement it traces to
BR-003
Priority
MoSCoW classification
Must Have
Acceptance Criteria
How to confirm it works
Given [context], When [action], Then [expected outcome]
Owner
Stakeholder responsible
Product Owner
Status
Draft / Approved / Implemented / Tested
Draft
Requirements Traceability Matrix (RTM)
Maps each business requirement through to functional requirements, test cases, and implementation. Ensures nothing is missed and every requirement can be tested. Essential for projects with regulatory compliance requirements.
BR-ID
Business Requirement
FR-ID
Functional Requirement
Test Case ID
Test Status
Sign-off
BR-001
Users must authenticate securely
FR-001, FR-002
Login, Password Reset
TC-001, TC-002
Pass
✓
BR-002
[Requirement text]
[FR-IDs]
[FR titles]
[TC-IDs]
Pending
User Story Template
Captures requirements from the user’s perspective in agile projects. Each story should be independently deliverable and testable. Use the INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable) to validate stories before sprint planning.
Field
Format / Example
Story ID
US-001
As a…
[Type of user / role]
I want to…
[Goal or action]
So that…
[Business value or outcome]
Acceptance Criteria
Given [context], When [action], Then [result]. Add one row per criterion.
Story Points
[Effort estimate]
Priority
Must Have / Should Have / Could Have
Dependencies
[Other story IDs]
Notes
Edge cases, exclusions, open questions
Use Case Template
Describes a system interaction from the actor’s perspective. Use cases are more detailed than user stories and are better suited to complex workflows or compliance-heavy projects.
Field
Content
Use Case ID
UC-001
Title
Descriptive name (verb + noun: “Submit Expense Claim”)
Primary Actor
Who initiates the use case
Secondary Actors
Other systems or roles involved
Preconditions
What must be true before this can start
Main Success Scenario
Step-by-step numbered list of the happy path
Alternative Flows
Valid variations of the main flow (Alt-1, Alt-2…)
Exception Flows
Error conditions and how the system handles them
Postconditions
System state after successful completion
Business Rules
Rules that govern this use case (link to BR-IDs)
Business Rules Template
Documents the operational policies, regulations, and constraints that govern how the business works. Business rules are separate from functional requirements — they define the boundaries of acceptable system behaviour.
Rule ID
Rule Statement
Category
Source
Impact
Owner
BR-001
All purchase orders above $10,000 must have two approvals
Approval
Finance Policy v3.1
High
CFO
BR-002
[Write rule as: Entity must/shall/must not verb condition]
Validation / Approval / Calculation / Restriction
[Policy, regulation, or SME]
High / Medium / Low
[Name]
Data Dictionary Template
Defines every data element used in a system or process — its name, format, valid values, and business meaning. Essential for integration projects, data migration, and anywhere multiple systems exchange data.
Field Name
Business Definition
Data Type
Format
Valid Values
Mandatory?
Source System
CustomerID
Unique identifier for a customer account
String
CUST-NNNNNN
CUST-000001 to CUST-999999
Yes
CRM
[Field name]
[Plain English meaning]
String / Integer / Date / Boolean / Decimal
[Pattern or example]
[List or range]
Yes / No
[System name]
Analysis & Assessment Templates
Gap Analysis Template
Compares the current state to the desired future state to identify what needs to change. Use early in a project to scope the work and justify investment.
Dimension
Current State (As-Is)
Desired State (To-Be)
Gap
Priority
Recommended Action
Process
Manual data entry, 3-day cycle
Automated, same-day processing
No automation; manual errors
High
Implement workflow automation
Technology
[Current tools]
[Target tools]
[Difference]
High / Med / Low
[Action]
People / Skills
[Current capability]
[Required capability]
[Skills gap]
[Training / hiring]
Data
[Current data state]
[Required data state]
[Data gap]
[Migration / cleanse]
Root Cause Analysis — 5 Whys Template
Traces a problem back to its root cause by asking “why” repeatedly. Works best for process failures where human or system factors compound. Use before defining requirements so you solve the actual problem, not just the symptom.
Level
Question
Answer
Problem Statement
What is the observable problem?
[Describe the symptom clearly]
Why 1
Why does this problem occur?
[First cause]
Why 2
Why does [Why 1 answer] happen?
[Second cause]
Why 3
Why does [Why 2 answer] happen?
[Third cause]
Why 4
Why does [Why 3 answer] happen?
[Fourth cause]
Why 5
Why does [Why 4 answer] happen?
[Root cause]
Corrective Action
What addresses the root cause?
[Recommended action]
SWOT Analysis Template
Evaluates a business, product, or initiative across four dimensions. Use in enterprise analysis, feasibility studies, and strategic planning workshops. Facilitating a SWOT session is a core BA skill — include it in your stakeholder workshop plan.
Strengths (Internal, Positive)
Weaknesses (Internal, Negative)
What advantages does the organisation/product have? What does it do well? What unique resources does it have?
What could be improved? What is done poorly? What should be avoided?
Opportunities (External, Positive)
Threats (External, Negative)
What opportunities exist in the market? What trends could be exploited? What changes in technology/regulation help?
What obstacles exist? What are competitors doing? What regulations or market shifts threaten success?
Cost-Benefit Analysis Template
Quantifies the financial case for a change initiative. Required for most business cases. Identify both tangible (measurable) and intangible (qualitative) costs and benefits.
Item
Type
Year 1
Year 2
Year 3
Total
Notes
COSTS
Software licences
One-off
$50,000
—
—
$50,000
CRM platform
Implementation / development
One-off
$80,000
—
—
$80,000
Training
One-off
$15,000
—
—
$15,000
Ongoing maintenance
Recurring
$10,000
$10,000
$10,000
$30,000
Per year
Total Costs
$155,000
$10,000
$10,000
$175,000
BENEFITS
Labour savings (automation)
Recurring
$40,000
$40,000
$40,000
$120,000
2 FTE
Revenue uplift
Recurring
$60,000
$75,000
$90,000
$225,000
5% conversion lift
Total Benefits
$100,000
$115,000
$130,000
$345,000
Net Benefit
-$55,000
$105,000
$120,000
$170,000
ROI: 97%
Risk Register Template
ID
Risk Description
Category
Likelihood (1–5)
Impact (1–5)
Score
Response Strategy
Owner
Status
R-001
[What could go wrong]
Technical / People / Process / External
3
4
12
Mitigate / Accept / Transfer / Avoid
[Name]
Open
Stakeholder Management Templates
Stakeholder Register Template
A living document that records every stakeholder involved in or affected by a change initiative. Build this at project kick-off and update it throughout delivery.
Name
Role / Title
Organisation
Interest in Project
Influence (H/M/L)
Impact on Them (H/M/L)
Engagement Level
Communication Preference
BA Notes
[Name]
[Role]
[Dept/Org]
[What they care about]
H
M
Champion / Supporter / Neutral / Critic / Blocker
Email weekly / Meeting bi-weekly
[Key concerns, motivators]
Power / Interest Stakeholder Matrix
Maps stakeholders by their power to influence the project and their interest in its outcome. Determines your engagement strategy for each group.
Low Interest
High Interest
High Power
Keep Satisfied Manage their concerns. Keep informed at a high level. Avoid surprises. Example: Executive sponsor who isn’t involved day-to-day.
Manage Closely Engage actively. Involve in decisions. Regular detailed communication. Example: Project sponsor, key business owner.
Low Power
Monitor Minimal effort. Keep on distribution list. Example: End users not yet in scope.
Keep Informed Provide regular updates. Involve in workshops. Example: End users, subject matter experts.
RACI Matrix Template
Defines who is Responsible, Accountable, Consulted, and Informed for each activity or deliverable. Use to eliminate confusion about ownership and prevent decisions stalling. Every activity should have exactly one Accountable person.
Activity / Deliverable
BA
Project Manager
Product Owner
Developer
Business SME
Executive Sponsor
Requirements Elicitation
R
C
A
I
C
I
BRD Sign-off
R
C
C
I
C
A
UAT Planning
A
C
R
C
R
I
[Activity]
Key: R = Responsible (does the work) · A = Accountable (owns the outcome, approves) · C = Consulted (input needed) · I = Informed (kept updated)
Requirements Elicitation Interview Template
Structure your stakeholder interviews to consistently capture requirements, pain points, and priorities. Adapt these questions to your project context.
Category
Questions
Context Setting
Can you walk me through your current process? What does a typical day/week look like for you in this area?
Pain Points
What are the biggest frustrations with how things work today? Where does the process break down most often? What takes longer than it should?
Requirements
What would the ideal solution look like for you? What does the new system/process absolutely must do? What would be a nice-to-have but not essential?
Constraints
Are there any systems this must integrate with? Are there regulatory or policy requirements we must comply with? What timeline or budget constraints should we be aware of?
Success
How will you know this project has been successful? What does “done” look like from your perspective?
Wrap-up
Is there anyone else I should speak to? Is there any documentation I should review? Is there anything I haven’t asked that’s important?
Process & Workflow Templates
SIPOC Template
SIPOC maps a process at a high level before diving into detailed modelling. Use it at the start of any process improvement or requirements project to scope the work and align stakeholders on what the process actually is.
Suppliers
Inputs
Process (High Level)
Outputs
Customers
Who provides the inputs?
What materials, data, or information enter the process?
Top 5 risks with likelihood, impact, and mitigation. Reference risk register.
8. Recommendation
Decision requested from the approving authority.
Project Scope Statement Template
Field
Content
Project Name
Project Sponsor
Business Objective
One sentence: what the project must achieve for the business
In Scope
Bulleted list of what IS included
Out of Scope
Explicit list of what is NOT included (prevents scope creep)
Deliverables
Tangible outputs the project will produce
Milestones
Key dates and decision points
Constraints
Fixed budget, deadline, technology, regulatory
Assumptions
What you’re assuming to be true (if wrong, replan)
Dependencies
What this project depends on / what depends on it
Approved by
[Sponsor name and date]
Testing & Quality Templates
UAT Test Plan Template
The BA typically owns UAT planning. This template ensures every business requirement has at least one test case and that the right stakeholders are doing the testing.
TC-ID
Requirement (BR/FR ID)
Test Scenario
Test Steps
Test Data
Expected Result
Actual Result
Pass/Fail
Tester
Date
TC-001
FR-001
User logs in with valid credentials
1. Navigate to login page 2. Enter valid email 3. Enter valid password 4. Click Login
Templates are only as useful as the analyst using them. The Certified Better Business Analyst (CBBA) course teaches you how to apply every template above in real delivery contexts — not just fill in the boxes, but understand what questions to ask, when to use which tool, and how to turn completed templates into decisions and action.
✓ 80+ lessons covering the full BBAI Framework ✓ Practical assignments using real project scenarios ✓ Verifiable digital certificate ✓ Self-paced — complete in 4–8 weeks
Start free → Try the Introduction to Business Analysis course — no payment required.
When you read the title of this blog post you might be tempted to ask the question – Isn’t Project management software for Project Managers? Well, the short answer is yes, but as Business Analysts are a large part of managing the scope of work through the delivery journey (which is primarily focused on delivering requirements) we should have the skills to understand stand up and run the delivery-focused project management software.
Business Analysts may use project management software such as Jira, Trello, Asana, MS Project, and Excel to manage project tasks, track progress, and collaborate with team members. Again, yes this should be owned by the Project Manager or sometimes the Scrum master but in many situations you will find that Business Analyst is creating, updating or managing the content within these tools.
I would like to spend some time talking about 3 of these tools that focus on the Delivery & Requirement Managements sides of things:
Excel
Jira
Azure DevOps
As a Business Analyst, your Requirements Traceability Matrix should be managed within one of these 3 tools (or more than) or something very similar.
Excel
Excel is a great tool for any business professional to learn however as a Business Analyst you should have advanced Excel knowledge.
Creating a Requirement Traceability Matrix in Excel is a simple task however there is no UX or system joins, dependencies or constraints between the Objectives, Epics and User Stories.
Define the requirements: Business Analysts can use Excel to capture and organize the requirements in a structured format. This may include columns for the requirement ID, description, priority, status, and any other relevant information. You may also use Excel to create a traceability matrix that maps the requirements to the project objectives.
Categorize the requirements: To make it easier to manage and prioritize requirements, BAs may use Excel to categorize them based on their functional or non-functional attributes. This may include creating columns for the requirement type, category, and sub-category.
Track changes and updates: Requirements are likely to change throughout the project lifecycle, so BAs can use Excel to track changes and updates to the requirements. This may include creating a separate column for change history, where BAs can document any changes made to the requirements and the reason for the change.
Use formulas and filters: Excel allows BAs to use formulas and filters to quickly analyze and manipulate data. For example, BAs can use formulas to calculate the total number of requirements, or use filters to sort requirements by priority, status, or category.
Generate reports: Finally, BAs can use Excel to generate reports on the requirements, such as a requirements traceability matrix or a requirements status report. These reports can help keep stakeholders informed of the progress of the project and ensure
Jira
Jira is a popular project management tool that can be used to manage requirements for software development projects
Create a project in Jira: The first step is to create a new project in Jira, or use an existing one. Make sure to select the appropriate project type based on your needs.
Define requirements: Once the project is created, define the requirements that need to be tracked. You can create a new issue type called “requirement” or use an existing one like “user story” or “feature” to represent the requirements.
Create issues: Create an issue for each requirement and enter a summary and description that clearly explains what the requirement is and what it should accomplish. You can also add labels, attachments, and comments to provide additional context.
Link requirements: To link related requirements, use the “link” feature in Jira to establish relationships between issues. For example, you can link a “parent” requirement to several “child” requirements that are necessary to fulfill the parent requirement.
Prioritise requirements: Use Jira’s priority system to prioritise requirements based on their importance and impact. You can assign a priority level to each requirement, such as “critical”, “high”, “medium”, or “low”.
Assign requirements: Assign requirements to team members responsible for implementing them. You can assign issues to specific individuals or to a team, and set due dates to ensure timely completion.
Track progress: Use Jira’s reporting features to track progress on requirements. You can generate reports to show the status of individual requirements, the progress of the entire project, and any issues that need attention.
Azure DevOps
Azure DevOps is a cloud-based project management tool that can be used to manage requirements for software development projects.
Create a project in Azure DevOps: The first step is to create a new project in Azure DevOps or use an existing one. Make sure to select the appropriate project type based on your needs.
Define requirements: Once the project is created, define the requirements that need to be tracked. You can create a new work item type called “requirement” or use an existing one like “user story” or “feature” to represent the requirements.
Create work items: Create a work item for each requirement and enter a title and description that clearly explains what the requirement is and what it should accomplish. You can also add labels, attachments, and comments to provide additional context.
Link requirements: To link related requirements, use the “link” feature in Azure DevOps to establish relationships between work items. For example, you can link a “parent” requirement to several “child” requirements that are necessary to fulfill the parent requirement.
Prioritise requirements: Use Azure DevOps’ priority system to prioritise requirements based on their importance and impact. You can assign a priority level to each requirement, such as “critical”, “high”, “medium”, or “low”.
Assign requirements: Assign requirements to team members responsible for implementing them. You can assign work items to specific individuals or to a team, and set due dates to ensure timely completion.
Track progress: Use Azure DevOps’ reporting features to track progress on requirements. You can generate reports to show the status of individual requirements, the progress of the entire project, and any issues that need attention.
There a number of specialist requirements management tools, such as IBM Rational DOORS or Jama Connect however in our opinion the above 3 tools are your best option.
We have defined our strategic objectives and now we need to look at how we are going to get after them.
A lot of big businesses have a project management office that manages the programme of work for the year and have project managers, business analysis and solution architects that collectively work on a project to complete a piece of work.
As far as a project owner and/or sponsor is concerned this is a great model and they can define their requirement and get a solution implemented through the solution delivery lifecycle.
What is sometimes forgotten when you work on projects is that generally your project is part of a greater programme and what is more commonly missed is that those programmes exist to help achieve a strategic objective.
With the structure of corporate being quite hierarchical with multiple department heads wanting to get their project funded the programme of work can get messy very quickly. Linking the Strategy objectives to each programme and then project can help prioritise what is important and what will give the business the biggest bang for buck!
In order to keep programme planning simple I am going to take our example from chapter 4 – Just Law and I am going to work down from the Strategic objectives. Be well aware that most companies’ programmes of work are already in flight from the year before and strategic objectives are hardly even linked or used to prioritise one programme against another – this is changing however!
In the case of Just Law we have our 3 strategic objectives which we examined in more detail. To meet SO1 John firstly needs to work out how he plans to get more clients in the door.
For S02 John’s needs a change project to reduce steps in his current sales and purchase management process and finally for S03 johns needs to have a small recruitment project to find and hire the right lawyer.
As I have been involved in many projects I would go ahead and state that John will have a programme consisting of at least 3 projects: 1. Investigate the options for increasing client number and implement, Implement a streamline sales and purchase process and recruit a lawyer.
Seeing as John wants to increase revenue this year through client number he will use a reserve fund to hire a business analyst who has recruitment skills to help him get after this change programme.
