SlideShare une entreprise Scribd logo
1  sur  17
Télécharger pour lire hors ligne
BA Core Skills - Overview & Intro




© Ability Engineering 2007                                       Page 1 of 26
BA Core Skills - Overview & Intro




© Ability Engineering 2007                                       Page 2 of 26
BA Core Skills - Overview & Intro




Imagine a typical business project which a BA may get called into.
The departments involved have a process, but only sort-of, and nobody really sticks to it.
Also, each different group within the department has their own set of tools & techniques for getting the
job done, and their own private stores of knowledge.
Mostly, they are using MS Word and Excel, with a bit of MS Project thrown in occasionally. Mapping
the interactions between the teams is a challenge: it’s mostly done via emails and meetings, with some
information kept on a shared drive, but with no clear organisation.

Those who, like me, are contract BAs are now looking forward to many months of lucrative work,
organising the business processes, understanding who produces what, and organising the knowledge of
the team.
Confident that we can significantly improve their business performance.

Except this isn’t a business project: this is an IT department. And the groups are all part of IT. There
are BAs, 6-sigma process modellers, UI and Ux designers and testers.

Sure, we have a process - sort-of. The BAs probably use one tool for requirements management and
another for use cases. The 6-sigma people another for processes.
And the UI designers use something else to create their wireframes. But they take input from the User
experience team, who use PowerPoint for their User Stories. And the testers use another toolset, but it’s
OK, because they get a 1-off email with a spreadsheet of the requirements, and keep their test cases
somewhere else….

And the poor Project Manager tries to make sense of it all with occasional snap-shots from everyone, but
keeps their own list of risks & issues. And the plan lives in MS Project.

And stranger still: this situation hasn’t changed that much in the 20 years that this author has been
involved in large-scale IT projects.
Has anything interesting happened in IT in the last 20 years…..


 © Ability Engineering 2007                                                                Page 3 of 26
BA Core Skills - Overview & Intro




BAs are typically charged with creating a single, coherent set of information about a project. We’ll call
that coherent set of data a ‘model’. Examples of models are Process, Use case, conceptual,
Requirements or User story/Journey.
These models have defined types of information within them, and many books get written about how
they can be created.
This presentation will suggest that just having one model type as the focus of a project means the project
will be limited in what is formally ‘known’ about the project, and that having multiple, linked models
can be hugely beneficial, both to the quality of the focal model, and to the project in general.


Some model types have evolved to capture particular kinds of knowledge. For example, the Business
Process Modelling Notation allows an accurate picture to be created for the processes within an
organisation. It records who does what activities, in what order, and what deliverables are produced and
consumed by each activity.


A great many specialist tools exist, which focus on the capture of individual knowledge types....




 © Ability Engineering 2007                                                               Page 4 of 26
BA Core Skills - Overview & Intro




Even if a project is focussed on one model type – for example, a BPMN Process Model – then there’s
much more knowledge which the project encounters as that model is created. So in a process model, the
BA will discover that some processes use functions of particular software systems, where those
functions might be captured in another form – the use case model for those systems. They may also
capture information about the organisation: not just who does which processes, but how those people fit
into the organisation, and who has what roles within the project.




 © Ability Engineering 2007                                                             Page 5 of 26
BA Core Skills - Overview & Intro




Having a number of different models in a project means we need to start to apply some of our BA skills
to ourselves. If this was a business, we might create a domain/conceptual/data model of what things are
known by the business. For a BP Model, it might look like this.




 © Ability Engineering 2007                                                             Page 6 of 26
BA Core Skills - Overview & Intro




A simple meta-model for Use Cases




© Ability Engineering 2007                                              Page 7 of 26
BA Core Skills - Overview & Intro




And another for the domain model of the business.




 © Ability Engineering 2007                                             Page 8 of 26
BA Core Skills - Overview & Intro




..and there are lots more.
These are particularly important. They are part of the life of most BAs, but rarely make it into a
structured analysis tool. But they are vital to keeping a project moving forward in an organised way.
Knowing who’s doing what, who owns what, what the risks & issues are is just as important knowing
what the requirements & user journeys are.




 © Ability Engineering 2007                                                             Page 9 of 26
BA Core Skills - Overview & Intro




This is the one you’ll have learned on most UML courses: take the nouns from the text of the Use Cases,
and form them into a domain model.




© Ability Engineering 2007                                                            Page 10 of 26
BA Core Skills - Overview & Intro




A more obscure example, but one which spans two areas which are normally spread across time and
organisation. Those who design a Data Warehouse or MI system to monitor a process, and those who
design the process in the first place may work in very different ways, but the ‘Business Event’ is a
shared idea.
So, link the Business Event from the Process world with the ‘fact’ in a fact/dimension model which the
data people use.




© Ability Engineering 2007                                                             Page 11 of 26
BA Core Skills - Overview & Intro




A more down-to-earth example.
Most projects have loads of lists & spreadsheets of risks and issues, notes of meetings and actions, so
why not hook them up to the requirements/analysis/design artefacts which they refer to? This makes
reporting on them more informative: Risks know what ‘thing’ (requirement/use case/component ) is
causing the risk, and those elements know that there is a risk associated with them.
Simple stuff, but powerfull.




© Ability Engineering 2007                                                               Page 12 of 26
BA Core Skills - Overview & Intro




But these models are all part of a larger picture. Together, then represent a rich picture of what we can
know about a project, from many points of view.
BUT, only if we choose to link the meta-models together.
So we might say that, for example, we may link
•   RISK to a DOMAIN MODEL CLASS, to indicate that there’s a problem
•   STAKEHOLDER to an ACTIVITY to indicate that the person OWNS the activity
•   ACTION to a USE CASE, to remember that there’s an action arising from a review meeting which
    we need to do concerning that use case.
•   ACTIVITY to USE CASES, so show that the process activity needs to use that use case




© Ability Engineering 2007                                                                Page 13 of 26
BA Core Skills - Overview & Intro




This is a fragment of a metamodel from a recent telecoms project.
The key item here is the Product Feature. This was the way that the product manager spoke about what
the solution did, and what the scope should be – always in terms of this- or that- feature.
So we made Feature the focus of the analysis.
Each product feature had a number of Use Cases: usually in two kinds: some where the user was USING
the feature, and some more where they were setting-up or administering the feature (this detail not
shown).
We tried to express as much as possible of the function of each feature into Use Cases, but there were
still some aspects which needed declarative requirements. A special type of requirement was the non-
functionals, attached to each Use Case, which specified the performance, frequency and volume
requirements for each use case – really useful for the designers downstream.
Unusually for this project, we also reverse-engineered some existing parts of the administration users
interface, to discover the Feature Settings. We made sure each setting got used in a use case somewhere,
and each action on the UI was a step in a use case.
Finally, we captured the Risk & Issues in the model, and linked those to any of the other items (links not
shown for clarity).
Also, we captured which product release each use case, requirement and feature setting was
implemented (links also not shown).




© Ability Engineering 2007                                                               Page 14 of 26
BA Core Skills - Overview & Intro




This represents WAY too much information to manage manually – this is what computers are for.
So, get yourself some kind of tool, to which everyone can contribute knowledge, and from which
everyone can pull information, and whatever format they want: reports, spreadsheets, documents,
diagrams.
And find/write some standards about what knowledge belongs where (your own meta-model) and stick
to it.




© Ability Engineering 2007                                                            Page 15 of 26
BA Core Skills - Overview & Intro




© Ability Engineering 2007                                       Page 16 of 26
BA Core Skills - Overview & Intro




© Ability Engineering 2007                                       Page 17 of 26

Contenu connexe

Tendances

Crafting Infrastructures. Requirements, scenarios and evaluation in the SPICE...
Crafting Infrastructures. Requirements, scenarios and evaluation in the SPICE...Crafting Infrastructures. Requirements, scenarios and evaluation in the SPICE...
Crafting Infrastructures. Requirements, scenarios and evaluation in the SPICE...Luca Galli
 
Maximize Project 2010 with SharePoint 2010 for PM Success
Maximize Project 2010 with SharePoint 2010 for PM SuccessMaximize Project 2010 with SharePoint 2010 for PM Success
Maximize Project 2010 with SharePoint 2010 for PM SuccessTimCermak
 
Good software architecture for business
Good software architecture for business Good software architecture for business
Good software architecture for business Anil Sharma
 
P-Camp 2008 - PM & UX - Meghan Ede 2
P-Camp 2008 - PM & UX - Meghan Ede 2P-Camp 2008 - PM & UX - Meghan Ede 2
P-Camp 2008 - PM & UX - Meghan Ede 2Meghan Ede
 
The Agile Gap: Closing it with User Experience
The Agile Gap: Closing it with User ExperienceThe Agile Gap: Closing it with User Experience
The Agile Gap: Closing it with User Experiencekalebwalton
 
Confessions of an HR Executive
Confessions of an HR ExecutiveConfessions of an HR Executive
Confessions of an HR Executivehdonbrown
 
Thoughts On Architecting V4 2
Thoughts On Architecting V4 2Thoughts On Architecting V4 2
Thoughts On Architecting V4 2bmercer
 
Project builder apresentação institucional (inglês) 2010
Project builder apresentação institucional (inglês)   2010Project builder apresentação institucional (inglês)   2010
Project builder apresentação institucional (inglês) 2010Project Builder
 
Integrate IT Strategic Planning with Performance Measurement
Integrate IT Strategic Planning with Performance MeasurementIntegrate IT Strategic Planning with Performance Measurement
Integrate IT Strategic Planning with Performance MeasurementYan Zhao
 
How UC Pays For Itself
How UC Pays For ItselfHow UC Pays For Itself
How UC Pays For ItselfLanair
 
How to effectively utilize project 2010 with share point 2010 mpugsemi_feb2012
How to effectively utilize project 2010 with share point 2010 mpugsemi_feb2012How to effectively utilize project 2010 with share point 2010 mpugsemi_feb2012
How to effectively utilize project 2010 with share point 2010 mpugsemi_feb2012TimCermak
 
Designing The User Experience In The Contact Center
Designing The User Experience In The Contact CenterDesigning The User Experience In The Contact Center
Designing The User Experience In The Contact CenterRobert Schumacher
 
Adapting to case management
Adapting to case managementAdapting to case management
Adapting to case managementTom Shepherd
 
Service Orientation Today and Tomorrow
Service Orientation Today and TomorrowService Orientation Today and Tomorrow
Service Orientation Today and TomorrowSalim Sheikh
 
Design Thinking + IT Services = Innovation Excellence (White Paper)//Motiv St...
Design Thinking + IT Services = Innovation Excellence (White Paper)//Motiv St...Design Thinking + IT Services = Innovation Excellence (White Paper)//Motiv St...
Design Thinking + IT Services = Innovation Excellence (White Paper)//Motiv St...Motiv Strategies
 

Tendances (18)

Agile modeling
Agile modelingAgile modeling
Agile modeling
 
Crafting Infrastructures. Requirements, scenarios and evaluation in the SPICE...
Crafting Infrastructures. Requirements, scenarios and evaluation in the SPICE...Crafting Infrastructures. Requirements, scenarios and evaluation in the SPICE...
Crafting Infrastructures. Requirements, scenarios and evaluation in the SPICE...
 
Testers Career Development Vaidyanathan Ramalingam
Testers Career Development Vaidyanathan RamalingamTesters Career Development Vaidyanathan Ramalingam
Testers Career Development Vaidyanathan Ramalingam
 
EA 101
EA 101EA 101
EA 101
 
Maximize Project 2010 with SharePoint 2010 for PM Success
Maximize Project 2010 with SharePoint 2010 for PM SuccessMaximize Project 2010 with SharePoint 2010 for PM Success
Maximize Project 2010 with SharePoint 2010 for PM Success
 
Good software architecture for business
Good software architecture for business Good software architecture for business
Good software architecture for business
 
P-Camp 2008 - PM & UX - Meghan Ede 2
P-Camp 2008 - PM & UX - Meghan Ede 2P-Camp 2008 - PM & UX - Meghan Ede 2
P-Camp 2008 - PM & UX - Meghan Ede 2
 
The Agile Gap: Closing it with User Experience
The Agile Gap: Closing it with User ExperienceThe Agile Gap: Closing it with User Experience
The Agile Gap: Closing it with User Experience
 
Confessions of an HR Executive
Confessions of an HR ExecutiveConfessions of an HR Executive
Confessions of an HR Executive
 
Thoughts On Architecting V4 2
Thoughts On Architecting V4 2Thoughts On Architecting V4 2
Thoughts On Architecting V4 2
 
Project builder apresentação institucional (inglês) 2010
Project builder apresentação institucional (inglês)   2010Project builder apresentação institucional (inglês)   2010
Project builder apresentação institucional (inglês) 2010
 
Integrate IT Strategic Planning with Performance Measurement
Integrate IT Strategic Planning with Performance MeasurementIntegrate IT Strategic Planning with Performance Measurement
Integrate IT Strategic Planning with Performance Measurement
 
How UC Pays For Itself
How UC Pays For ItselfHow UC Pays For Itself
How UC Pays For Itself
 
How to effectively utilize project 2010 with share point 2010 mpugsemi_feb2012
How to effectively utilize project 2010 with share point 2010 mpugsemi_feb2012How to effectively utilize project 2010 with share point 2010 mpugsemi_feb2012
How to effectively utilize project 2010 with share point 2010 mpugsemi_feb2012
 
Designing The User Experience In The Contact Center
Designing The User Experience In The Contact CenterDesigning The User Experience In The Contact Center
Designing The User Experience In The Contact Center
 
Adapting to case management
Adapting to case managementAdapting to case management
Adapting to case management
 
Service Orientation Today and Tomorrow
Service Orientation Today and TomorrowService Orientation Today and Tomorrow
Service Orientation Today and Tomorrow
 
Design Thinking + IT Services = Innovation Excellence (White Paper)//Motiv St...
Design Thinking + IT Services = Innovation Excellence (White Paper)//Motiv St...Design Thinking + IT Services = Innovation Excellence (White Paper)//Motiv St...
Design Thinking + IT Services = Innovation Excellence (White Paper)//Motiv St...
 

En vedette

Common challenges in adopting Agile: IIBA Northampton event 23rd August 2011
Common challenges in adopting Agile: IIBA Northampton event 23rd August 2011Common challenges in adopting Agile: IIBA Northampton event 23rd August 2011
Common challenges in adopting Agile: IIBA Northampton event 23rd August 2011IIBA UK Chapter
 
Anatomy of a Business Analyst
Anatomy of a Business Analyst Anatomy of a Business Analyst
Anatomy of a Business Analyst IIBA UK Chapter
 
Adapting Agile in Large Organisations
Adapting Agile in Large OrganisationsAdapting Agile in Large Organisations
Adapting Agile in Large OrganisationsIIBA UK Chapter
 

En vedette (6)

Common challenges in adopting Agile: IIBA Northampton event 23rd August 2011
Common challenges in adopting Agile: IIBA Northampton event 23rd August 2011Common challenges in adopting Agile: IIBA Northampton event 23rd August 2011
Common challenges in adopting Agile: IIBA Northampton event 23rd August 2011
 
The Power of Story
The Power of StoryThe Power of Story
The Power of Story
 
Anatomy of a Business Analyst
Anatomy of a Business Analyst Anatomy of a Business Analyst
Anatomy of a Business Analyst
 
Adapting Agile in Large Organisations
Adapting Agile in Large OrganisationsAdapting Agile in Large Organisations
Adapting Agile in Large Organisations
 
The power of story
The power of storyThe power of story
The power of story
 
Communities of practice
Communities of practiceCommunities of practice
Communities of practice
 

Similaire à IIBA Multimodels

Enterprise Architecture Justification Paper Va Dmv
Enterprise Architecture Justification Paper Va DmvEnterprise Architecture Justification Paper Va Dmv
Enterprise Architecture Justification Paper Va DmvWendy Fox
 
BPMS Buyer's Tool Kit - Sample RFP
BPMS Buyer's Tool Kit - Sample RFPBPMS Buyer's Tool Kit - Sample RFP
BPMS Buyer's Tool Kit - Sample RFPBonitasoft
 
Process architecture vs modeling
Process architecture vs modelingProcess architecture vs modeling
Process architecture vs modelingGraham McLeod
 
40411923 business-analyst
40411923 business-analyst40411923 business-analyst
40411923 business-analystHar Da
 
Mohan Kumar Abbanna
Mohan Kumar AbbannaMohan Kumar Abbanna
Mohan Kumar AbbannaMohan Kumar
 
Java TechTalk "Spring boot made life easier with Kubernetes and Microservices"
Java TechTalk "Spring boot made life easier with Kubernetes and Microservices"Java TechTalk "Spring boot made life easier with Kubernetes and Microservices"
Java TechTalk "Spring boot made life easier with Kubernetes and Microservices"GlobalLogic Ukraine
 
Modeling techniques forthe business analyst
Modeling techniques forthe business analystModeling techniques forthe business analyst
Modeling techniques forthe business analystbestip
 
A Model-Driven Approach to Align Business Processes with User Interfaces
A Model-Driven Approach to Align Business Processes with User InterfacesA Model-Driven Approach to Align Business Processes with User Interfaces
A Model-Driven Approach to Align Business Processes with User Interfaceskenia.sousa
 
Southern Pulp &Amp; Paper
Southern Pulp &Amp; PaperSouthern Pulp &Amp; Paper
Southern Pulp &Amp; PaperNicole Savoie
 
NUX October 6th 2014 - UX in a traditional enterprise
NUX October 6th 2014 - UX in a traditional enterpriseNUX October 6th 2014 - UX in a traditional enterprise
NUX October 6th 2014 - UX in a traditional enterprisepjhauser
 
Secrets of going codeless - How to build enterprise apps without coding
Secrets of going codeless - How to build enterprise apps without codingSecrets of going codeless - How to build enterprise apps without coding
Secrets of going codeless - How to build enterprise apps without codingNewton Day Uploads
 
When a Process diagram is not Enough
When a Process diagram is not EnoughWhen a Process diagram is not Enough
When a Process diagram is not EnoughGeoffrey Long
 
Innovation in model driven software
Innovation in model driven softwareInnovation in model driven software
Innovation in model driven softwareSagi Schliesser
 
Effective Business Analysis
Effective Business AnalysisEffective Business Analysis
Effective Business AnalysisKailash Sumana
 
Driving Your BA Career Roles
Driving Your BA Career RolesDriving Your BA Career Roles
Driving Your BA Career RolesShankar Karthik
 
Define and Manage Requirements with IBM Rational Requirements Composer
Define and Manage Requirements with IBM Rational Requirements ComposerDefine and Manage Requirements with IBM Rational Requirements Composer
Define and Manage Requirements with IBM Rational Requirements ComposerAlan Kan
 

Similaire à IIBA Multimodels (20)

Project Estimating....The Squeeze is On
Project Estimating....The Squeeze is OnProject Estimating....The Squeeze is On
Project Estimating....The Squeeze is On
 
Enterprise Architecture Justification Paper Va Dmv
Enterprise Architecture Justification Paper Va DmvEnterprise Architecture Justification Paper Va Dmv
Enterprise Architecture Justification Paper Va Dmv
 
BPMS Buyer's Tool Kit - Sample RFP
BPMS Buyer's Tool Kit - Sample RFPBPMS Buyer's Tool Kit - Sample RFP
BPMS Buyer's Tool Kit - Sample RFP
 
Process architecture vs modeling
Process architecture vs modelingProcess architecture vs modeling
Process architecture vs modeling
 
40411923 business-analyst
40411923 business-analyst40411923 business-analyst
40411923 business-analyst
 
Mohan Kumar Abbanna
Mohan Kumar AbbannaMohan Kumar Abbanna
Mohan Kumar Abbanna
 
Java TechTalk "Spring boot made life easier with Kubernetes and Microservices"
Java TechTalk "Spring boot made life easier with Kubernetes and Microservices"Java TechTalk "Spring boot made life easier with Kubernetes and Microservices"
Java TechTalk "Spring boot made life easier with Kubernetes and Microservices"
 
Agile It 20091020
Agile It 20091020Agile It 20091020
Agile It 20091020
 
Modeling techniques forthe business analyst
Modeling techniques forthe business analystModeling techniques forthe business analyst
Modeling techniques forthe business analyst
 
A Model-Driven Approach to Align Business Processes with User Interfaces
A Model-Driven Approach to Align Business Processes with User InterfacesA Model-Driven Approach to Align Business Processes with User Interfaces
A Model-Driven Approach to Align Business Processes with User Interfaces
 
Southern Pulp &Amp; Paper
Southern Pulp &Amp; PaperSouthern Pulp &Amp; Paper
Southern Pulp &Amp; Paper
 
Domain Driven Design
Domain Driven DesignDomain Driven Design
Domain Driven Design
 
NUX October 6th 2014 - UX in a traditional enterprise
NUX October 6th 2014 - UX in a traditional enterpriseNUX October 6th 2014 - UX in a traditional enterprise
NUX October 6th 2014 - UX in a traditional enterprise
 
Secrets of going codeless - How to build enterprise apps without coding
Secrets of going codeless - How to build enterprise apps without codingSecrets of going codeless - How to build enterprise apps without coding
Secrets of going codeless - How to build enterprise apps without coding
 
When a Process diagram is not Enough
When a Process diagram is not EnoughWhen a Process diagram is not Enough
When a Process diagram is not Enough
 
Innovation in model driven software
Innovation in model driven softwareInnovation in model driven software
Innovation in model driven software
 
Effective Business Analysis
Effective Business AnalysisEffective Business Analysis
Effective Business Analysis
 
Driving Your BA Career Roles
Driving Your BA Career RolesDriving Your BA Career Roles
Driving Your BA Career Roles
 
PMC1
PMC1PMC1
PMC1
 
Define and Manage Requirements with IBM Rational Requirements Composer
Define and Manage Requirements with IBM Rational Requirements ComposerDefine and Manage Requirements with IBM Rational Requirements Composer
Define and Manage Requirements with IBM Rational Requirements Composer
 

Plus de IIBA UK Chapter

Bitesize BA techniques: business case development
Bitesize BA techniques: business case developmentBitesize BA techniques: business case development
Bitesize BA techniques: business case developmentIIBA UK Chapter
 
IT VM for BAs - A Closer Look (Part I) - 300823.pdf
IT VM for BAs - A Closer Look (Part I) - 300823.pdfIT VM for BAs - A Closer Look (Part I) - 300823.pdf
IT VM for BAs - A Closer Look (Part I) - 300823.pdfIIBA UK Chapter
 
Business Analysis and the Art of Storytelling
Business Analysis and the Art of StorytellingBusiness Analysis and the Art of Storytelling
Business Analysis and the Art of StorytellingIIBA UK Chapter
 
IIBA_Cheltenham_D_Paul_C_Lovelock_LeadingTheBAServiceV05.pdf
IIBA_Cheltenham_D_Paul_C_Lovelock_LeadingTheBAServiceV05.pdfIIBA_Cheltenham_D_Paul_C_Lovelock_LeadingTheBAServiceV05.pdf
IIBA_Cheltenham_D_Paul_C_Lovelock_LeadingTheBAServiceV05.pdfIIBA UK Chapter
 
IIBA_Manchester_D_Paul_C_Lovelock_LeadingTheBAServiceV07.pdf
IIBA_Manchester_D_Paul_C_Lovelock_LeadingTheBAServiceV07.pdfIIBA_Manchester_D_Paul_C_Lovelock_LeadingTheBAServiceV07.pdf
IIBA_Manchester_D_Paul_C_Lovelock_LeadingTheBAServiceV07.pdfIIBA UK Chapter
 
Infinite organisation - a vision of agility as growth and opportunity.pdf
Infinite organisation - a vision of agility as growth and opportunity.pdfInfinite organisation - a vision of agility as growth and opportunity.pdf
Infinite organisation - a vision of agility as growth and opportunity.pdfIIBA UK Chapter
 
Behavioural Science - IIBA UK 2022-10-26
Behavioural Science - IIBA UK  2022-10-26Behavioural Science - IIBA UK  2022-10-26
Behavioural Science - IIBA UK 2022-10-26IIBA UK Chapter
 
IT VM for BAs - The Journey and The Elephant
IT VM for BAs - The Journey and The ElephantIT VM for BAs - The Journey and The Elephant
IT VM for BAs - The Journey and The ElephantIIBA UK Chapter
 
How to thrive during change
How to thrive during changeHow to thrive during change
How to thrive during changeIIBA UK Chapter
 
Future of ba iiba slides
Future of ba   iiba slidesFuture of ba   iiba slides
Future of ba iiba slidesIIBA UK Chapter
 
Analysis in Action 21 September 2021
Analysis in Action 21 September 2021Analysis in Action 21 September 2021
Analysis in Action 21 September 2021IIBA UK Chapter
 
BABOK Summer Bootcamp - Chapter 8: Solutions Evaluation Date: 7 Sep 2021
BABOK Summer Bootcamp - Chapter 8: Solutions Evaluation  Date: 	7 Sep 2021 BABOK Summer Bootcamp - Chapter 8: Solutions Evaluation  Date: 	7 Sep 2021
BABOK Summer Bootcamp - Chapter 8: Solutions Evaluation Date: 7 Sep 2021 IIBA UK Chapter
 
BABOK Summer Bootcamp - Chapter 5: Requirements Lifecycle Management
BABOK Summer Bootcamp - Chapter 5: Requirements Lifecycle ManagementBABOK Summer Bootcamp - Chapter 5: Requirements Lifecycle Management
BABOK Summer Bootcamp - Chapter 5: Requirements Lifecycle ManagementIIBA UK Chapter
 
BABOK Summer Bootcamp - Chapter 7: Requirements Analysis & Design Definition
BABOK Summer Bootcamp - Chapter 7: Requirements Analysis & Design DefinitionBABOK Summer Bootcamp - Chapter 7: Requirements Analysis & Design Definition
BABOK Summer Bootcamp - Chapter 7: Requirements Analysis & Design DefinitionIIBA UK Chapter
 
BABOK Summer Bootcamp Chapter 4: Elicitation & Collaboration
BABOK Summer Bootcamp Chapter 4: Elicitation & CollaborationBABOK Summer Bootcamp Chapter 4: Elicitation & Collaboration
BABOK Summer Bootcamp Chapter 4: Elicitation & CollaborationIIBA UK Chapter
 
BABOK Summer Bootcamp - Chapter 3: Business Analysis Planning & Monitoring
BABOK Summer Bootcamp - Chapter 3: Business Analysis Planning & MonitoringBABOK Summer Bootcamp - Chapter 3: Business Analysis Planning & Monitoring
BABOK Summer Bootcamp - Chapter 3: Business Analysis Planning & MonitoringIIBA UK Chapter
 
Babok webinar strategy analysis 20210803
Babok webinar strategy analysis 20210803Babok webinar strategy analysis 20210803
Babok webinar strategy analysis 20210803IIBA UK Chapter
 
Babok webinar underlying competencies 20210727
Babok webinar underlying competencies 20210727 Babok webinar underlying competencies 20210727
Babok webinar underlying competencies 20210727 IIBA UK Chapter
 
Babok webinar key concepts pdf 20210720
Babok webinar key concepts pdf 20210720Babok webinar key concepts pdf 20210720
Babok webinar key concepts pdf 20210720IIBA UK Chapter
 

Plus de IIBA UK Chapter (20)

Bitesize BA techniques: business case development
Bitesize BA techniques: business case developmentBitesize BA techniques: business case development
Bitesize BA techniques: business case development
 
IT VM for BAs - A Closer Look (Part I) - 300823.pdf
IT VM for BAs - A Closer Look (Part I) - 300823.pdfIT VM for BAs - A Closer Look (Part I) - 300823.pdf
IT VM for BAs - A Closer Look (Part I) - 300823.pdf
 
Business Analysis and the Art of Storytelling
Business Analysis and the Art of StorytellingBusiness Analysis and the Art of Storytelling
Business Analysis and the Art of Storytelling
 
IIBA_Cheltenham_D_Paul_C_Lovelock_LeadingTheBAServiceV05.pdf
IIBA_Cheltenham_D_Paul_C_Lovelock_LeadingTheBAServiceV05.pdfIIBA_Cheltenham_D_Paul_C_Lovelock_LeadingTheBAServiceV05.pdf
IIBA_Cheltenham_D_Paul_C_Lovelock_LeadingTheBAServiceV05.pdf
 
IIBA_Manchester_D_Paul_C_Lovelock_LeadingTheBAServiceV07.pdf
IIBA_Manchester_D_Paul_C_Lovelock_LeadingTheBAServiceV07.pdfIIBA_Manchester_D_Paul_C_Lovelock_LeadingTheBAServiceV07.pdf
IIBA_Manchester_D_Paul_C_Lovelock_LeadingTheBAServiceV07.pdf
 
Infinite organisation - a vision of agility as growth and opportunity.pdf
Infinite organisation - a vision of agility as growth and opportunity.pdfInfinite organisation - a vision of agility as growth and opportunity.pdf
Infinite organisation - a vision of agility as growth and opportunity.pdf
 
Behavioural Science - IIBA UK 2022-10-26
Behavioural Science - IIBA UK  2022-10-26Behavioural Science - IIBA UK  2022-10-26
Behavioural Science - IIBA UK 2022-10-26
 
IT VM for BAs - The Journey and The Elephant
IT VM for BAs - The Journey and The ElephantIT VM for BAs - The Journey and The Elephant
IT VM for BAs - The Journey and The Elephant
 
How to thrive during change
How to thrive during changeHow to thrive during change
How to thrive during change
 
Future of ba iiba slides
Future of ba   iiba slidesFuture of ba   iiba slides
Future of ba iiba slides
 
Confidence at Work
Confidence at WorkConfidence at Work
Confidence at Work
 
Analysis in Action 21 September 2021
Analysis in Action 21 September 2021Analysis in Action 21 September 2021
Analysis in Action 21 September 2021
 
BABOK Summer Bootcamp - Chapter 8: Solutions Evaluation Date: 7 Sep 2021
BABOK Summer Bootcamp - Chapter 8: Solutions Evaluation  Date: 	7 Sep 2021 BABOK Summer Bootcamp - Chapter 8: Solutions Evaluation  Date: 	7 Sep 2021
BABOK Summer Bootcamp - Chapter 8: Solutions Evaluation Date: 7 Sep 2021
 
BABOK Summer Bootcamp - Chapter 5: Requirements Lifecycle Management
BABOK Summer Bootcamp - Chapter 5: Requirements Lifecycle ManagementBABOK Summer Bootcamp - Chapter 5: Requirements Lifecycle Management
BABOK Summer Bootcamp - Chapter 5: Requirements Lifecycle Management
 
BABOK Summer Bootcamp - Chapter 7: Requirements Analysis & Design Definition
BABOK Summer Bootcamp - Chapter 7: Requirements Analysis & Design DefinitionBABOK Summer Bootcamp - Chapter 7: Requirements Analysis & Design Definition
BABOK Summer Bootcamp - Chapter 7: Requirements Analysis & Design Definition
 
BABOK Summer Bootcamp Chapter 4: Elicitation & Collaboration
BABOK Summer Bootcamp Chapter 4: Elicitation & CollaborationBABOK Summer Bootcamp Chapter 4: Elicitation & Collaboration
BABOK Summer Bootcamp Chapter 4: Elicitation & Collaboration
 
BABOK Summer Bootcamp - Chapter 3: Business Analysis Planning & Monitoring
BABOK Summer Bootcamp - Chapter 3: Business Analysis Planning & MonitoringBABOK Summer Bootcamp - Chapter 3: Business Analysis Planning & Monitoring
BABOK Summer Bootcamp - Chapter 3: Business Analysis Planning & Monitoring
 
Babok webinar strategy analysis 20210803
Babok webinar strategy analysis 20210803Babok webinar strategy analysis 20210803
Babok webinar strategy analysis 20210803
 
Babok webinar underlying competencies 20210727
Babok webinar underlying competencies 20210727 Babok webinar underlying competencies 20210727
Babok webinar underlying competencies 20210727
 
Babok webinar key concepts pdf 20210720
Babok webinar key concepts pdf 20210720Babok webinar key concepts pdf 20210720
Babok webinar key concepts pdf 20210720
 

IIBA Multimodels

  • 1. BA Core Skills - Overview & Intro © Ability Engineering 2007 Page 1 of 26
  • 2. BA Core Skills - Overview & Intro © Ability Engineering 2007 Page 2 of 26
  • 3. BA Core Skills - Overview & Intro Imagine a typical business project which a BA may get called into. The departments involved have a process, but only sort-of, and nobody really sticks to it. Also, each different group within the department has their own set of tools & techniques for getting the job done, and their own private stores of knowledge. Mostly, they are using MS Word and Excel, with a bit of MS Project thrown in occasionally. Mapping the interactions between the teams is a challenge: it’s mostly done via emails and meetings, with some information kept on a shared drive, but with no clear organisation. Those who, like me, are contract BAs are now looking forward to many months of lucrative work, organising the business processes, understanding who produces what, and organising the knowledge of the team. Confident that we can significantly improve their business performance. Except this isn’t a business project: this is an IT department. And the groups are all part of IT. There are BAs, 6-sigma process modellers, UI and Ux designers and testers. Sure, we have a process - sort-of. The BAs probably use one tool for requirements management and another for use cases. The 6-sigma people another for processes. And the UI designers use something else to create their wireframes. But they take input from the User experience team, who use PowerPoint for their User Stories. And the testers use another toolset, but it’s OK, because they get a 1-off email with a spreadsheet of the requirements, and keep their test cases somewhere else…. And the poor Project Manager tries to make sense of it all with occasional snap-shots from everyone, but keeps their own list of risks & issues. And the plan lives in MS Project. And stranger still: this situation hasn’t changed that much in the 20 years that this author has been involved in large-scale IT projects. Has anything interesting happened in IT in the last 20 years….. © Ability Engineering 2007 Page 3 of 26
  • 4. BA Core Skills - Overview & Intro BAs are typically charged with creating a single, coherent set of information about a project. We’ll call that coherent set of data a ‘model’. Examples of models are Process, Use case, conceptual, Requirements or User story/Journey. These models have defined types of information within them, and many books get written about how they can be created. This presentation will suggest that just having one model type as the focus of a project means the project will be limited in what is formally ‘known’ about the project, and that having multiple, linked models can be hugely beneficial, both to the quality of the focal model, and to the project in general. Some model types have evolved to capture particular kinds of knowledge. For example, the Business Process Modelling Notation allows an accurate picture to be created for the processes within an organisation. It records who does what activities, in what order, and what deliverables are produced and consumed by each activity. A great many specialist tools exist, which focus on the capture of individual knowledge types.... © Ability Engineering 2007 Page 4 of 26
  • 5. BA Core Skills - Overview & Intro Even if a project is focussed on one model type – for example, a BPMN Process Model – then there’s much more knowledge which the project encounters as that model is created. So in a process model, the BA will discover that some processes use functions of particular software systems, where those functions might be captured in another form – the use case model for those systems. They may also capture information about the organisation: not just who does which processes, but how those people fit into the organisation, and who has what roles within the project. © Ability Engineering 2007 Page 5 of 26
  • 6. BA Core Skills - Overview & Intro Having a number of different models in a project means we need to start to apply some of our BA skills to ourselves. If this was a business, we might create a domain/conceptual/data model of what things are known by the business. For a BP Model, it might look like this. © Ability Engineering 2007 Page 6 of 26
  • 7. BA Core Skills - Overview & Intro A simple meta-model for Use Cases © Ability Engineering 2007 Page 7 of 26
  • 8. BA Core Skills - Overview & Intro And another for the domain model of the business. © Ability Engineering 2007 Page 8 of 26
  • 9. BA Core Skills - Overview & Intro ..and there are lots more. These are particularly important. They are part of the life of most BAs, but rarely make it into a structured analysis tool. But they are vital to keeping a project moving forward in an organised way. Knowing who’s doing what, who owns what, what the risks & issues are is just as important knowing what the requirements & user journeys are. © Ability Engineering 2007 Page 9 of 26
  • 10. BA Core Skills - Overview & Intro This is the one you’ll have learned on most UML courses: take the nouns from the text of the Use Cases, and form them into a domain model. © Ability Engineering 2007 Page 10 of 26
  • 11. BA Core Skills - Overview & Intro A more obscure example, but one which spans two areas which are normally spread across time and organisation. Those who design a Data Warehouse or MI system to monitor a process, and those who design the process in the first place may work in very different ways, but the ‘Business Event’ is a shared idea. So, link the Business Event from the Process world with the ‘fact’ in a fact/dimension model which the data people use. © Ability Engineering 2007 Page 11 of 26
  • 12. BA Core Skills - Overview & Intro A more down-to-earth example. Most projects have loads of lists & spreadsheets of risks and issues, notes of meetings and actions, so why not hook them up to the requirements/analysis/design artefacts which they refer to? This makes reporting on them more informative: Risks know what ‘thing’ (requirement/use case/component ) is causing the risk, and those elements know that there is a risk associated with them. Simple stuff, but powerfull. © Ability Engineering 2007 Page 12 of 26
  • 13. BA Core Skills - Overview & Intro But these models are all part of a larger picture. Together, then represent a rich picture of what we can know about a project, from many points of view. BUT, only if we choose to link the meta-models together. So we might say that, for example, we may link • RISK to a DOMAIN MODEL CLASS, to indicate that there’s a problem • STAKEHOLDER to an ACTIVITY to indicate that the person OWNS the activity • ACTION to a USE CASE, to remember that there’s an action arising from a review meeting which we need to do concerning that use case. • ACTIVITY to USE CASES, so show that the process activity needs to use that use case © Ability Engineering 2007 Page 13 of 26
  • 14. BA Core Skills - Overview & Intro This is a fragment of a metamodel from a recent telecoms project. The key item here is the Product Feature. This was the way that the product manager spoke about what the solution did, and what the scope should be – always in terms of this- or that- feature. So we made Feature the focus of the analysis. Each product feature had a number of Use Cases: usually in two kinds: some where the user was USING the feature, and some more where they were setting-up or administering the feature (this detail not shown). We tried to express as much as possible of the function of each feature into Use Cases, but there were still some aspects which needed declarative requirements. A special type of requirement was the non- functionals, attached to each Use Case, which specified the performance, frequency and volume requirements for each use case – really useful for the designers downstream. Unusually for this project, we also reverse-engineered some existing parts of the administration users interface, to discover the Feature Settings. We made sure each setting got used in a use case somewhere, and each action on the UI was a step in a use case. Finally, we captured the Risk & Issues in the model, and linked those to any of the other items (links not shown for clarity). Also, we captured which product release each use case, requirement and feature setting was implemented (links also not shown). © Ability Engineering 2007 Page 14 of 26
  • 15. BA Core Skills - Overview & Intro This represents WAY too much information to manage manually – this is what computers are for. So, get yourself some kind of tool, to which everyone can contribute knowledge, and from which everyone can pull information, and whatever format they want: reports, spreadsheets, documents, diagrams. And find/write some standards about what knowledge belongs where (your own meta-model) and stick to it. © Ability Engineering 2007 Page 15 of 26
  • 16. BA Core Skills - Overview & Intro © Ability Engineering 2007 Page 16 of 26
  • 17. BA Core Skills - Overview & Intro © Ability Engineering 2007 Page 17 of 26