PMI PBA: Need Assessment Study Guideline

Exclusive forum for iZenBirdge PMI-PBA® clients to discuss issues / tips related to PMI-PBA® exam.
Posts: 2276
Joined: Fri Jul 11, 2014 11:57 am

PMI PBA: Need Assessment Study Guideline

Postby seema.sonkiya Wed Dec 17, 2014 7:08 am

Study Guideline for Need Assessment based on:

1. Flow described viewtopic.php?f=24&t=1745 based on Business Analysis Practice Guide.
2. PMI PBA content outline: ... tline.ashx
3. Section “Want to start preparing for the exam? Here are few ideas:” taken from ... I-PBA.aspx
4. Valuable insight given by lead author of Business Analysis Practices Guide @Project Management Institute: ... mr_6661117
5. PMI's definition of requirements management mentioned in PMI-Pulse-Requirements-Management-In-Depth-Report : ... eport.ashx

6. Excerpts taken from ... Qs_v2.ashx
“What will PMI do to develop a body of knowledge in Requirements Management and Business Analysis?
PMI plans to publish a practice guide on Business Analysis and a practice standard on Requirements Management.
The Business Analysis practice guide will link good Requirements Management practices from A Guide to the Project Management Body of Knowledge (PMBOK® Guide) to the practical implementation of Business Analysis within organizations.
Business Analysis subject matter experts will author the guide and PMI plans to keep the community apprised of the initiative.
The Requirements Management practice standard is a full consensus, common standard presently in development and slated for launch in 2015. This unique standard will be a collaboration between: Project Managers; Value, Software and Systems Engineers; and Business and Agile Analysts. It will address the common components of requirements across these disciplines.”
A good essence can be visualized if we see above mentioned details on one table altogether:

Valuable facts discovered from abovementioned context:
1. The practice guide and the PMI-PBA are complementary products, but neither is based solely on the other. The reference list (accessible from the PMI-PBA certification page) identifies sources that along with the business analysis practice guide can help you fill in knowledge gaps, help you understand processes or techniques you may not have had the experience to perform on the job; but it's the culmination of your experience, and these resources that will help you best prepare for the PMI-PBA. -----Laura Paton (Lead Author of Business Analysis Practise guide)

2. Keep in mind that the PBA exam is 'experienced-based', therefore simply memorizing content is not the best indicator -Laura Paton (Lead Author of Business Analysis Practise guide)

3. People, processes and culture are the requirement management capabilities. Organizations as a whole — and both top management and executive/project sponsors, specifically — do not fully value requirements management as a critical competency for projects and strategic initiatives --- PMI's Pulse of the Profession In-Depth Report on Requirements Management

Hence my conclusion on the basis of above points: upcoming release requirement management practice guide will shed light in requirement management for Need Assessment domain as well (kindly note above - the word i.e. strategic initiative) in terms of people, processes and culture as these are requirement management capabilities  mentioned above.

4. Now we are not having requirement management practice guide, however we know that whenever it will come, it will not present things beyond outside of reference books. Hence we need to fill the gaps with help of reference books.

5. Out of all the reference books, Business Analysis tools and techniques – 72 essential tools for success is one where Need Assessment domain is in main focus. So we need to fill the gap with help of this reference book.

6. Strategic tools and techniques are included in content outline in Knowledge and Skills section

7. In 72 tools and techniques book, it is clearly indicated that Business Analyst work precedes that of the Project Manager and a Business Analyst should know about strategic tools and techniques.

8. In Business Analysis Practice guide, it is clearly mentioned that once situation statement get approved, Business Analyst should review Strategy documents. If strategy documents are not available, in that case he/she should develop Goals and objectives in collaboration with Key Stakeholders. Now goals and objectives discovered with help of Vision and Mission of the organisation. Therefore understanding and developing process of vision, mission, goals, objectives, strategies and tactics are important to business analyst.

9. Strategy documents also clarify details about Market share, competition, available and potential products and services. These details are output of strategy development and refinement. Hence business analyst should be aware about how to assess external and internal business environment as strategy development and refinements required assessment of both external and internal business environment.

10. Need Assessment in business analysis practice guide mentioned importance of assessment of external and internal business environment and these assessments use strategic tools and techniques. We already observed that strategic tools and techniques included in content outline.

11. During analysis of current capabilities and desired capabilities, requirement management is also performed in terms of people, processes and culture. So Gap Analysis is also need to be referenced from 72 tools and techniques. Business Analysis practise guide focus on identification of capabilities for each problem and root cause while 72 tools and techniques focus on how desired business processes are developed with help of CATWOE, Business Activity Modelling, Business Event Analysis and with help of process map. Current or actual view of capabilities in business analysis practise guide are described with help of review of process flows, external business architecture and capability framework. While in 72 tools and techniques it is identified by Use Cases, Swim lane diagrams (similar to process flow), rich pictures and with help of mind maps.

12. However practically approach of gap analysis depends on organisation enterprise architecture that includes people, processes, applications etc. Business Analysis practice guide used the review of enterprise architecture as a tool to assess current capabilities. In addition requirement management capabilities includes people, processes and culture and hence it is direct indication that we need to see every business analysis activity from these dimensions. Therefore 72 tools and techniques approach of gap analysis is relevant to both business analysis practice guide and requirement management practice guide.

13. I communicated during 13th June 2014 clarification session that we need to follow 72 tools and techniques, but for gap analysis approach we are not required to refer it. But now based on my recent research, I take my words back. Now based on abovementioned facts, approach of gap analysis in Need Assessment is still relevant from 72 tools and techniques.

14. Now process of evaluating options for the development of business case in 72 Tools and Techniques:
i. Identify options: map to the include high level approach for adding capabilities. Where how the outcome of gap analysis (which are project deliverables) are acquired to fill the gap.
ii. Shortlist options: Map to the provide alternative options for satisfying business need, identifying constraints, assumptions & risk for each option, assess feasibility & organisational impacts for each option, and recommending the most viable option. For shortlisting options, 72 tools and techniques use tools like SWOT analysis, PESTLE analysis, Feasibility analysis and force field analysis. All of these are relevant to the content outline.
iii. Prepare Business Case map to the cost benefit analysis of business analysis practice guide.
So evaluating options section of 72 tools and techniques is also need to refer for details for the examination

Items relevant to Need Assessment extracted from Content Outline:
1. Problem and Opportunity analysis techniques for example

Value Engineering
Scenario Analysis
User Journey Map

2. Valuation Tools and Techniques for Value Proposition
Cost Benefit Analysis
Force field Analysis
Kano Model
Net Promoter Score
Purpose Alignment Model
SWOT Analysis
Value Stream Map

3. Collaborate in the development of project goals and objectives – clarification on Business Need.

4. Identify RACI – appropriate parties are represented, informed and involved

5. Determine stakeholder Values using elicitation techniques  prioritising requirements.

From Knowledge and Skills section of content outline:

6. Analytic tools and techniques (for example, decomposition, progressive elaboration, dependency analysis, gap analysis, impact analysis, risk analysis, and assessment)

7. Business Rule Analysis tools and techniques (Decision Table, Decision Tree, Rule Catalog

8. Collaboration Tools and Techniques

9. Communication skills, techniques, and tools (for example, technical writing, business writing, working with virtual teams, presentation skills, verbal and nonverbal communication)

10. Conflict management and resolution tools and techniques

11. Elicitation tools and techniques (for example, brainstorming, focus groups, interviewing techniques, workshop facilitation, observation, document analysis, research, surveys, and questionnaires)

12. Facilitation tools and techniques

13. Negotiation tools and techniques

15. Organization assessment (for example, organizational readiness)

16. Planning tools and techniques (for example, strategic and tactical)

17. Prioritization tools and techniques (for example, multi-voting, weighted criteria, MoSCoW)

18. Process analysis tools and techniques (for example, user stories, use cases, process model, data flow diagrams, dependency graphs, events)

19. Reporting tools and techniques

20. Root cause analysis (for example, Ishikawa/fishbone, 5 Whys)

21. Stakeholder analysis (for example, personas, role definition [RACI], job analysis, skills assessment)

important note to conclude:
1. Tools and techniques are not domain specific; we are expected to use tools which are relevant to specific situation or process. Hence above analysis should not be interpreted as scope of Need Assessment is too high. We are just required to understand the essence of each business analysis tools and techniques and then we can think to apply them to the relevant process of any domain. That is the reason, we are developing online course where tools and techniques are described separately and to communicate flow and processes of domains, we are including binding videos.
We need to understand here, what are the processes of need assessment in terms of flow, and whatever tools are applicable, we can see them in the context.

This flow will need to be understand from practical implementation point of view in the organisations and that flow will constitute approx. 18% of questions in the examination i.e. approx. 35-40 questions.

2. Chapter 1 to 5 of Business Analysis tools and techniques – 72 essential tools for success are relevant to Need Assessment.
Posts: 84
Joined: Fri Nov 03, 2017 1:10 pm

Re: PMI PBA: Need Assessment Study Guideline

Postby Sam Thu Jan 18, 2018 9:03 pm

Excellent article

Do you have Study Guidelines but for other domains?

Return to “PMI-PBA® Queries and Tips”

Who is online

Users browsing this forum: No registered users and 4 guests