How to apply Microsoft Azure DevOps for business analyst - key OOB features and wide possibilities with process customization.

1. How to apply ALM to
Enterprise Business Analysis
ThinkersWare ALM Consulting
http://alm.thinkersware.com

2. Антон Витязь
Enterprise Solutions Consultant @ ThinkersWare
Group Leader @ Infopulse Ukraine
• 18 лет в IT
• Developer -> System Analyst -> Business Analyst -> Consultant
• Java, C/AL, X++, C#, Typescript, React
• Navision, Axapta, SharePoint, Dynamics
• Web, Mobile
• Проекты в разных странах - Украина, Бруней, Исландия,
Норвегия, Швеция, Швейцария, Венгрия, Чехия
• Спикер ИТ конференций – BACON, Thinkstage, DAKIRY

3. Agenda
Today we are focus on Business Analyst
practice and how we can improve it with
better ALM adoption based on Microsoft
Azure DevOps Tools.

4. 1
What is ALM for you
Current practices, how your BA practice fit with
ALM, why you out of ALM and what issues and
risks affect you and your team.
Agenda

5. 2
3
ALM OOB
What Microsoft Azure DevOps offers to your
NOW with out of the box? What you can use ang
got benefits now.
Extend ALM
Microsoft Azure DevOps offers process model
extensions: you can add custom work types, add
new fields and change work item forms.
Understand SWOT of customized ALM, some
suggestions and next steps

6. 4
Explore
Explore customized process and some sample
cases
Think. Do. Repeat

7. 1. What is ALM for you?

8. Azure DevOps
W h a t a n a m e
Thanks to the new name for TFS we got some cognitive
confusions when we are talking about Microsoft Azure DevOps
services. Its perceived as a solely tech tools for wired engineers at
the -1 floor of the software development factory.

9. Business Analyst
W h a t a p l e a s u r e t o b e
Something very nice and very business. Full of insights,
model and communication with stakeholders

10. Common ALM
applications
Y o u r c u r r e n t p r a c t i c e
Pipelines
CICD, testing
Work
Backlog, Bugs, Issues
Code
Git repository
Communication
Team chats, wiki

11. 01
02
03
04
Gather requirements
Analyze, Model,
Design
Communicate
Gain approvals
Start from inputs documents, notes. Create
process and domain model, detail use cases.
Plan communications, clarify questions. Track
approvals.
Business analyst

12. Out of ALM things
W R I T E H E R E S O M E T H I N G A B O U T
Documents
01 MoM
02 Stakeholders
03Not stored in version control Questions and answers,
agenda and participants
List of stakeholders, linked
requirements
Initial inputs
04 Business Process
05 Domain Model
06 Entities, attributesBusiness process modelStakeholder raw inputs, initial
requirements
Use Cases
07 FR and NFR
08 Approvals
09 Track what has been
approved by customer
List of functional and non-
functional requirements
Detailed description for Use
Cases

13. Convenient tools
Word, Excel and Visio fully supports basic
documents, data and models. Simple tools
accepted by all stakeholders and team
members.
Big tools is Big tools
Matter of license cost, complex adoptions, non
flexible models. Rarely team could purchase all
licenses for all stakeholder and than adopt it.
Time limits
But I must explain to you how all this mistaken
idea of denouncing pleasure and praising pain
was born and I will give you a complete account
of the system

14. Versions trap
Documents and records are out of version
control.
Limited collaboration
In most cases one user work with one
document.
Complexity
Big documents with a lot of information. It’s hard
to divide parts by state (approved or not,
completed or draft)

15. Adopt ALM as-is
Start to use it widely with a current process.
Adopt repository, wiki pages and start to use
basic work items widely.
Extend process
Put in your specific BA work items: Business
process, Stakeholders etc.
Use it
Every day, each time. Promote among your
colleagues and other stakeholders.
Secret receipt
K e y i d e a s t o c h a n g e t h i n g s
How you can do better business analysis with Microsoft Azure
DevOps

16. 2. ALM Out of the Box

17. Initial setup
P U T Y O U R G R E A T S U B T I T L E H E R E
Setup Organization
It is VERY easy to get your new organization
with – https://dev.azure.com – any email
and you are @ ALM
Consider Costs
• Free for 5 users
• Free for MSDN Subscription
• Free for any Stakeholders
• Around 6$ for additional user
http://alm.thinkersware.com/setup/

18. Out of the Box capabilities
M i c r o s o f t A z u r e D e v O p s
Work item
You can track requirements,
issues, risk, bugs etc
Customization
You can create new fields to
the current work items or
create your new one
Emails
Notify key users, sent links,
send Excel files with exported
data
Query
Advanced flat and hieararchy
flat
Repository
Store almost unlimited content
– documents, files, media,
code
Communications
Integrate to your collaboration
environments

19. Excel Sync
K i l l e r f e a t u r e
• Export any set of work items with Query – list of fields, sorting
and order
• Send it to customer / Store at Repository
• Update and sync back to Azure DevOps
• Enable offline store, Mass update, Mass inputs, Easy to create and
change hierarchy
http://alm.thinkersware.com/tools/excel/install-excel-plugin/

20. #01 Manual entering
Hundreds of requirements entered
manually from Excel and Word lists
#02 Mass updates
Repeatable operations one by one
#03 Build hierarchy
New items, child relationship done
manually
Cruel facts
L o s t h o u r s , l o s t h o p e s

21. 3. Extend your ALM

22. Extensions approaches
Minor to existing work items
– fields, change state model
Mixing work items – mix
Agile and CMMI
Completely new set of work
items

23. WeaknessStrengths
Opportunities Threats
Availability, Price, Wide adoption, Easy to use for
records, Customizable
New plugins, flexibility to adopt new Business
Analysis models
Business adoption issues
Visualization, No Lookups , Lack of BA models
adoptions
ALM for BA SWOT
H o w M i c r o s o f t A z u r e D e v O p s f i t s B A t a s k s

24. Enterprise Business Analysis Process
Extend ALM applications
• Track all information inputs
• Business Process Model
• Business Domain Model
• Link visual models with work items
• Detailed use cases description
New work items
• Process, Action, Event
• Entity, Attributes
• Stakeholder, Inputs
• Use Case, Use Case Step, Actor
http://alm.thinkersware.com/business-process-model/

25. 4. Explore Sample Case

26. Sample EBA Process
Process includes mix of Enterprise Business
Analysis work items.
Project with some demo data using this
process template -
https://dev.azure.com/ThinkersWareDemo/P
ub_Process

27. Project setup
• One sample process
• Data model
• Use Cases model

28. Work with Inputs
What you usually receives: Documents, E-
Mails, Informal information. You can dig for
external data sources.
How ALM can support you:
• Store document at Git or WiKi
• Track document register
• Document minutes of meetings
• Track key statements
• State questions, issues
< Live Demo>

29. Strategic BA & PM
Understand business motivation – what kind
of challenges stay underneath, how business
define goals and objectives. Clearly state
scope, expected deliverables and limits.
Maintain list of stakeholders.
How ALM can support you:
• Track Goals and Objectives
• Track Constraints and Decision
• Define Scope
• Track Stakeholders

30. Prepare to Meeting Collect agenda points, track participants
How ALM can support you:
• Meeting, Meeting point
• Meeting notes at Wiki

31. Share Content
Share content with multiple stakeholders,
receives their inputs and updates.
How ALM can support you:
• Wiki pages
• Excel files
• Visio files connected to work items

32. Process model
Manage business process model as-is and to-
be. Link process steps to system use cases.
Track related discussions, issues.
How ALM can support you:
• Track process as items
< Live Demo>

33. Domain model
Depict key entities and attribute. Track
approvals and changes. Link to discussions.
AL
• Entities and Attributes
• Link Questions to model

34. Use Case model
Deliver detailed use case specification with a
Use Case and Use Case Step work items ALM

35. 5. Think. Do. Repeat

36. Enjoy Azure
DevOps
• Create own organization
• Join Thinkersware Demo Instance

37. Common EBA
model01
Shared Cases
02
Share Practices
03

38. Azure DevOps
Knowledge
warehouse
R e a d
http://alm.thinkersware.com/

39. Contacts
Feel free to contact me with any questions you want to ask me 
Ukraine+380-66-0043-073Anton.Vityaz@gmail.com
Facebook: anton.vityaz
Skype: anton.vityaz