Business Analyst - Revision history

Cpd at 02:31, 4 March 2018

2018-03-04T02:31:51Z

← Older revision		Revision as of 02:31, 4 March 2018
Line 3:		Line 3:


	Thao Lan NGUYEN ~~THI~~ organized 2 training sessions about the job of '''Business Analyst''' (also known as "'''BA'''") in IT Development in May 2016 and April 2017.		Thao Lan NGUYEN HOANG organized 2 training sessions about the job of '''Business Analyst''' (also known as "'''BA'''") in IT Development in May 2016 and April 2017.

Cpd at 03:11, 31 January 2018

2018-01-31T03:11:40Z

← Older revision		Revision as of 03:11, 31 January 2018
Line 1:		Line 1:
	[[File:Nobody mess with my Best Amigos (BA) !.png]]		[[File:Nobody mess with my Best Amigos (BA) !.png]]
	~~<BR>~~


	Thao Lan NGUYEN THI organized 2 training sessions about the job of '''Business Analyst''' (also known as "'''BA'''") in IT Development in May 2016 and April 2017.		Thao Lan NGUYEN THI organized 2 training sessions about the job of '''Business Analyst''' (also known as "'''BA'''") in IT Development in May 2016 and April 2017.


	== Session 1 ==		== Session 1 ==

Cpd at 03:10, 31 January 2018

2018-01-31T03:10:33Z

← Older revision		Revision as of 03:10, 31 January 2018
Line 222:		Line 222:

	=== Analysis ===		=== Analysis ===
			{\| class="wikitable" style="width: 60%;"
			\|-
			\| '''Definition'''\|\| Requirements analysis involves refining the requirements to ensure that all stakeholders understand them and scrutinizing them for errors, omissions, and other deficiencies.

	~~==== Definition ====~~		\|-
	~~Requirements analysis involves refining the requirements to ensure that all stakeholders understand them and scrutinizing them for errors, omissions, and other deficiencies~~		\| '''Frequently used techniques'''\|\|

	~~====~~Frequently used techniques ~~& output ====~~
	'''~~Techniques :'''~~

	* Prioritize the requirements		* Prioritize the requirements
	* Create a data dictionary		* Create a data dictionary
	* Analyze requirement feasibility		* Analyze requirement feasibility
			\|-
	'''Output'''		\| '''Output'''\|\| Requirements [solid]: Prototype (visual form), Document (textual form)
			\|}
	Requirements [solid]: Prototype (visual form), Document (textual form)

	=== Specification ===		=== Specification ===
			{\| class="wikitable" style="width: 60%;"
	==== Definition ~~====~~		\|-
	Requirements specification is to document requirements of different types in a consistent, accessible, and reviewable way that is readily understandable by the intended audiences		\|'''Definition'''\|\| Requirements specification is to document requirements of different types in a consistent, accessible, and reviewable way that is readily understandable by the intended audiences.
			\|-
	~~====~~Frequently used techniques ~~& output ====~~		\| '''Frequently used techniques'''\|\|
	~~'''Techniques :~~'''
	* Specify non-functional requirements		* Specify non-functional requirements
	* Record business rules		* Record business rules
	* Identify requirement origins		* Identify requirement origins
			\|-
	'''~~Output:~~'''		\| '''output''' \|\| User requirements typically are represented in the form of use cases or user stories.
			\|}
	User requirements typically are represented in the form of use cases or user stories.

	===Validation===		===Validation===
			{\| class="wikitable" style="width: 60%;"
	~~==== Definition ==~~==		\|-
			\|\| '''Definition''' \|\| Validation ensures that the requirements are correct, demonstrate the desired quality characteristics, and will satisfy customer needs. Requirements that seem fine when you read them might turn out to have ambiguities and gaps when developers try to work with them.
	Validation ensures that the requirements are correct, demonstrate the desired quality characteristics, and will satisfy customer needs. Requirements that seem fine when you read them might turn out to have ambiguities and gaps when developers try to work with them		\|-
			\| '''Frequently used techniques'''\|\|
	~~====~~Frequently used techniques ~~& output ====~~
	~~'''Techniques :~~'''
	* Simulate the requirements		* Simulate the requirements
	* Define acceptance criteria		* Define acceptance criteria
			\|-
			\| '''output''' \|\| User requirements typically are represented in the form of use cases or user stories, that are understood correctly by Dev team and Stakeholders
			\|}

	~~'''Output:'''~~

	~~User requirements typically are represented in the form of use cases or user stories, that are understood correctly by Dev team and Stakeholders~~

	===Sources===		===Sources===

Cpd at 02:39, 31 January 2018

2018-01-31T02:39:27Z

← Older revision		Revision as of 02:39, 31 January 2018
Line 1:		Line 1:
	[[File:Nobody mess with my Best Amigos (BA) !.png]]		[[File:Nobody mess with my Best Amigos (BA) !.png]]
			<BR>
	Thao Lan NGUYEN THI organized 2 training sessions about the job of '''Business Analyst''' (also known as "BA") in IT Development in May 2016 and April 2017.		Thao Lan NGUYEN THI organized 2 training sessions about the job of '''Business Analyst''' (also known as "'''BA'''") in IT Development in May 2016 and April 2017.

	== Session 1 ==		== Session 1 ==

Cpd at 02:38, 31 January 2018

2018-01-31T02:38:04Z

← Older revision		Revision as of 02:38, 31 January 2018
Line 272:		Line 272:
	* Microsoft.Press.Software.Requirements.3.3rd.Edition.Aug.2013.pdf		* Microsoft.Press.Software.Requirements.3.3rd.Edition.Aug.2013.pdf
	* [https://www.slideshare.net/MarrajuBollapRagada/agile-vs-iterativevswaterfall Quick understanding about Waterfall / Iterative / Agile]		* [https://www.slideshare.net/MarrajuBollapRagada/agile-vs-iterativevswaterfall Quick understanding about Waterfall / Iterative / Agile]

			== References ==
			* [https://docs.google.com/presentation/d/1O94mnfFULC_mSGIw63lmPuIUBHK25ENIMz9T7-CMDYk BA Training Course - Part 1 (by Thao Lan NGUYEN HOANG)]
			* [https://docs.google.com/presentation/d/1sPMHC_HnyKx4s6ewHeYxZ-DUWe_1R70-Q--Dop_bZVQ BA Training Course - Part 2 (by Thao Lan NGUYEN HOANG)]
			* [https://docs.google.com/presentation/d/1T0P99QI7L5Ha9Xf8teJLWpnPIrFHhyptn8m0P8pqGrE BA Training Course - Part 3 (by Thao Lan NGUYEN HOANG)]
			* [https://docs.google.com/presentation/d/12HM3EQTGqkcofnOmSpfirRC5T3by5Zbn3ojfQesNiH0 BA Training Course - Part 4 (by Thao Lan NGUYEN HOANG)]

Cpd at 07:16, 30 January 2018

2018-01-30T07:16:01Z

← Older revision		Revision as of 07:16, 30 January 2018
Line 1:		Line 1:
	[[File:BA~~-is-a-skill~~.~~jpg~~]]		[[File:Nobody mess with my Best Amigos (BA) !.png]]

	Thao Lan NGUYEN THI organized 2 training sessions about the job of '''Business Analyst''' (also known as "BA") in IT Development in May 2016 and April 2017.		Thao Lan NGUYEN THI organized 2 training sessions about the job of '''Business Analyst''' (also known as "BA") in IT Development in May 2016 and April 2017.
Line 8:		Line 8:
	Business Analysis is the practice of enabling change in an organizational context, by defining needs and recommending solutions that deliver value to stakeholders. (IIBA definition)		Business Analysis is the practice of enabling change in an organizational context, by defining needs and recommending solutions that deliver value to stakeholders. (IIBA definition)

			[[File:BA-is-a-skill.jpg]]

	=== What is a Business Analyst? ===		=== What is a Business Analyst? ===

Cpd at 06:53, 30 January 2018

2018-01-30T06:53:17Z

← Older revision		Revision as of 06:53, 30 January 2018
Line 200:		Line 200:

	== Session 4==		== Session 4==

			=== Elicitation ===

			====Definition====

			#to draw forth or bring out (something latent or potential)
			#to call forth or draw out (as information or a response)
			These definitions highlight the need to actively engage the stakeholders in defining requirements.

			====Frequently used techniques & output ====
			'''Techniques :'''
			* Hold elicitation interviews
			* Identify champion product
			* Perform document analysis

			'''Output'''

			* Requirements [Stated]: Described from the perspective of the stakeholder. Stated requirements describe the stakeholder’s need from the stakeholder’s perspective.
			* Stakeholder Concerns: Includes issues identified by the stakeholder, risks, assumptions, constraints, and other relevant information

			=== Analysis ===

			==== Definition ====
			Requirements analysis involves refining the requirements to ensure that all stakeholders understand them and scrutinizing them for errors, omissions, and other deficiencies

			====Frequently used techniques & output ====
			'''Techniques :'''

			* Prioritize the requirements
			* Create a data dictionary
			* Analyze requirement feasibility

			'''Output'''

			Requirements [solid]: Prototype (visual form), Document (textual form)

			=== Specification ===

			==== Definition ====
			Requirements specification is to document requirements of different types in a consistent, accessible, and reviewable way that is readily understandable by the intended audiences

			====Frequently used techniques & output ====
			'''Techniques :'''
			* Specify non-functional requirements
			* Record business rules
			* Identify requirement origins

			'''Output:'''

			User requirements typically are represented in the form of use cases or user stories.

			===Validation===

			==== Definition ====

			Validation ensures that the requirements are correct, demonstrate the desired quality characteristics, and will satisfy customer needs. Requirements that seem fine when you read them might turn out to have ambiguities and gaps when developers try to work with them

			====Frequently used techniques & output ====
			'''Techniques :'''
			* Simulate the requirements
			* Define acceptance criteria

			'''Output:'''

			User requirements typically are represented in the form of use cases or user stories, that are understood correctly by Dev team and Stakeholders

			===Sources===
			* [https://lostechies.com/joeocampo/2007/09/20/agile-vs-traditional-development-cost-models-maybe Traditional Methodology Resource Cost Chart]
			* BABOK v2.0
			* Microsoft.Press.Software.Requirements.3.3rd.Edition.Aug.2013.pdf
			* [https://www.slideshare.net/MarrajuBollapRagada/agile-vs-iterativevswaterfall Quick understanding about Waterfall / Iterative / Agile]

Cpd at 06:31, 30 January 2018

2018-01-30T06:31:19Z

← Older revision		Revision as of 06:31, 30 January 2018
Line 18:		Line 18:
	* BA as a skill		* BA as a skill
	* BA is not only a single person.		* BA is not only a single person.

			===Sources===
			* [http://www.iiba.org/Careers/What-is-Business-Analysis.aspx What is Business Analysis by iiba.org]
			* BABOKv2.0.pdf


	== Session 2 ==		== Session 2 ==
Line 120:		Line 125:
	*Enterprise Architect		*Enterprise Architect
	\|}		\|}

			=== Sources ===
			*[http://www.iiba.org/Careers/Careers/business-analyst-career-roadmap.aspx\|Business Analyst career roadmap by iiba.org]
			*[http://www.iiba.org/Careers/Business-Analysis-Careers.aspx Business Analysis Careers by iiba.org]


	[[File:You-dont-need-IT-knowledge-to-be-BA.jpg]]		[[File:You-dont-need-IT-knowledge-to-be-BA.jpg]]


	==Session 3==		==Session 3==
Line 184:		Line 194:

	=== Sources ===		=== Sources ===
	* [https://lostechies.com/joeocampo/2007/09/20/agile-vs-traditional-development-cost-models-maybe/ ~~“Traditional~~ Methodology Resource ~~Cost”~~ Chart]		* [https://lostechies.com/joeocampo/2007/09/20/agile-vs-traditional-development-cost-models-maybe/ Traditional Methodology Resource Cost Chart]
	* BABOK v2.0		* BABOK v2.0
	* Microsoft.Press.Software.Requirements.3.3rd.Edition.Aug.2013.pdf		* Microsoft.Press.Software.Requirements.3.3rd.Edition.Aug.2013.pdf
	* [https://www.slideshare.net/MarrajuBollapRagada/agile-vs-iterativevswaterfall Quick understanding about Waterfall / Iterative / Agile]		* [https://www.slideshare.net/MarrajuBollapRagada/agile-vs-iterativevswaterfall Quick understanding about Waterfall / Iterative / Agile]

			== Session 4==

Cpd at 06:22, 30 January 2018

2018-01-30T06:22:43Z

@@ Line 1: / Line 1: @@
 Thao Lan NGUYEN THI organized 2 training sessions about the job of '''Business Analyst''' (also known as "BA") in IT Development in May 2016 and April 2017.
@@ Line 10: / Line 12: @@
 Job titles for business analysis practitioners include not only business analyst, but also business systems analyst, systems analyst, requirements engineer, process analyst, product manager, product owner, enterprise analyst, business architect, management consultant, business intelligence analyst, data scientist, and more. Many other jobs, such as management, project management, product management, software development (dev), quality assurance (test/QC) and interaction design (UI/ UX design) rely heavily on business analysis skills for success.
 '''To remember :'''
@@ Line 116: / Line 120: @@
 *Enterprise Architect
 |}

Cpd: Created page with "Thao Lan NGUYEN THI organized 2 training sessions about the job of '''Business Analyst''' (also known as "BA") in IT Development in May 2016 and April 2017. == Session 1 == =..."

2018-01-30T05:54:11Z

Created page with "Thao Lan NGUYEN THI organized 2 training sessions about the job of '''Business Analyst''' (also known as "BA") in IT Development in May 2016 and April 2017. == Session 1 == =..."

New page

Thao Lan NGUYEN THI organized 2 training sessions about the job of '''Business Analyst''' (also known as "BA") in IT Development in May 2016 and April 2017.

== Session 1 ==
===What is Business Analysis? ===

Business Analysis is the practice of enabling change in an organizational context, by defining needs and recommending solutions that deliver value to stakeholders. (IIBA definition)

=== What is a Business Analyst? ===

Job titles for business analysis practitioners include not only business analyst, but also business systems analyst, systems analyst, requirements engineer, process analyst, product manager, product owner, enterprise analyst, business architect, management consultant, business intelligence analyst, data scientist, and more. Many other jobs, such as management, project management, product management, software development (dev), quality assurance (test/QC) and interaction design (UI/ UX design) rely heavily on business analysis skills for success.

'''To remember :'''
* BA as a skill
* BA is not only a single person.

== Session 2 ==

=== What’s my career path in BA? ===

{| class="wikitable"
|-
! Business Focused !! IT focused
|-style="vertical-align:top"
| style="width:300px"|
# Business Requirements Analyst: help the business to meet its objectives and goals
# Business Process Analyst: bring change to organizations that keep organizations running and manage the changes of those processes.
# Decision Analyst – In Demand (often referred to as a Business Intelligence Analyst)
|style="width:300px"|
# Business Systems Analyst
# Agile Analyst
# Functional Analyst
# Systems Analyst
# Service Request Analyst

|}

====Decision Analyst====

Often referred to as a '''Business Intelligence Analyst'''
{| class="wikitable"
|-
! Input !! Output
|-
|style="width:300px"| Data & Statistical Methods
|style="width:300px"| The ability to gain insight and to drive business planning
|}

===Business analysis job profiles===

{| class="wikitable"
|-
! !! Project/ IT Executes projects !! Transition/ Functional Guides projects !! Enterprise/ Strategic Creates projects
|-
| '''Generalist'''
|style="vertical-align:top;"|
*Business Analyst
*(Project) Management Consultant
|style="vertical-align:top;"|
*Account Manager
*Business Consultant
*Customer Relationship Manager
*Management Consultant
*Portfolio Manager
|style="vertical-align:top;"|
*Account Manager
*Business Architect
*Management Consultant
*Strategic Planner

|-
| '''Specialist'''
|style="vertical-align:top;"|
*Agile Business Analyst
*Business Intelligence Analyst
*Business Rules Analyst
*Data Analyst
*Domain Expert (SME)
*Process Analyst
*Product Owner
*Requirements Engineer/Manager
*Systems Analyst
|style="vertical-align:top;"|
*Business Intelligence Analyst
*Domain Expert (SME)
*Functional Business Analyst
*Process Owner
*Product Manager
*Service Owner
*Systems/Solution Architect
|style="vertical-align:top;"|
*Domain Expert (SME)
*IT Strategist
*Process Architect

|-
| '''Hybrid'''
|style="vertical-align:top;"|
*BA+PM QA, Development
*DBA
*Information Architect
*Product Manager
*Project Manager
*QA Analyst
*Systems Analyst
*Usability/UXP
|style="vertical-align:top;"|
*Mid-to Senior Management
*Product Manager
*Solution Architect
*Systems Analyst
|style="vertical-align:top"|
*CXO
*Enterprise Architect
|}