RFI: Request For Information

RFQ: Request For Quote（报价）

RFT: Request For Tender（招标 最正式）

RFP: Request For Proposal（建议书）

估算方法：

1.Top-down 粗

2.Bottom-up 细

3.Parametric Estimation 样例估算

4.Rough Order of Magnitude 很粗

5.Rolling Wave 由粗到细

6.Delphi 专家经验统计分析

7.PERT （3 point estimation）

预测型方法论 &&  适应型方法论

BA的工作方式不同，预测型模式中主要集中工作在前期，适应型模式中工作量分布是比较平均的，在每一个迭代过程中都会涉及

6个领域30个task

6大知识领域

1. strategy analysis

2. elicitation collaboration

3. business analysis planning and monitoring

4. requirements analysis and design definition

5. solution evaluation

6. Requirements lifecycle management

Task: input

         output

         guidelines and tools  

         stakeholders

         techniques

         elements(implement steps/ factors)

requirement schema

1. business

2.stakeholds

3.solution

4.transition

Business Analysis Key Concept

Knowledge Area

Underlying Competencies

Techniques

Perspectives

Benefits

Task

Input output

Stakeholders

Technique

瀑布

螺旋

敏捷

3.5识别BA表现

从形式：

书面或者口头衡量

考核，收集并分析数据，比如报告

衡量绩效方法：

准确性完整性

有效性

效率

组织层面支持程度

时效性

战略

分析结果

用center of excellence或者老板来主导

基于结果发现的问题，用根本原因分析法，基于根本原因改进。

预防，降低发生问题可能性

纠正，减小事件带来影响

改进，使事件影响变得更好

需求的层次：

enterprise requirements

stakeholder requirements

solution requirements

tansition requirements

定战略目标，细化阶段任务，实施路径（解决方案） 

考试技巧：每个task的输入输出背下来。

guidelines & Tools、stakeholders、 Techniques 要理解下来

discrete 离散的

iteratively 迭代地

simultaneously 同步的

解决方案评价（solution evaluation）和现状分析（strategy analysis）是最有可能开启BA工作的

由整体到细节，先花时间把整体定义清楚再逐步到细节，不要过早的陷入到细节的讨论。

考试技巧：分析需求属于哪个层级的，可以先根据提出需求的句子中的主语来辅助判断。

Transition Requirements：针对某个需求，前期已有部分工作准备或者不完整的方案和数据，新设计的方案需要对该部分进行继承和迁移。

what和how之间的关系。

BA的重点方向更多是what，定义需求

how更多的由解决方案设计者完成。

风险、问题、机会。

Business Analysis information:

Elicitation, analysis and maintainance 

in V3.0 may not be only information only but focus group stakeholder analysis mention information such as requirements/ limittion/ assumption/ risk /concerns etc.

Eliciation results becaues the inforamtion captured via collection only when the information is evalute tehn passed then it will be then passed. 

Design: How  Process handling/ structue Design is a solution 

Requirements: What need to achieve

Needs- representation of a need. 

Enterprise is one or more organisation including internal or external.  BA Plan: Stakeholder register/ communication channel/ change management/information maintain etc.

Plan: Use approach which covers various forms of the output during the planning process. Depenencies/ schedule/sequence etc.

Risk: In V

Discovery, synthsizing or category then analysis information to capture the information within the enterprise including tools, process documents and stakeholders. 

Align the design solution requiremetns with the stakeholder requirements to satisfy the stakeholder needs. 

Specialist

Generilist: Consultant from service provider. 

Hybird: Overlap of business analysis and PM.

Business Analysis is the practice of enabling change in an enterprise by defining needs and recomending solution that delivery value to delivery stakeholders. 

Defining the needs/ Recommend the solution that delivery value to delivery value to the stakeholders. enterprise- organisation including the customer/suppliers/external parties. First to unerstand the problem/opportunites Nees is input understanding the why then generate the requirements as output as business requirements. Then based on the business requirements recommending solutions to the stakeholders solution evaluation via providing some recommendation. Solutions not only a software but also process enhancement/structure enhancements. Business focus on the value and requirements. 

收集信息方式：

Affinity Map 亲和力图

Fishbow 鱼缸

Focus Group 焦点小组

    pre-qualified participants 预先经过挑选的参与人员

    qualitative research 定性研究

    homogeneous

    hetrogeneous

Interview 访谈

affinity map 亲和图

fishbowl   鱼缸

assumption 假设

reveal 显示、揭露

encourage 鼓励

reserve   保留

participant  参与者

observer 观察者

moderator   主持人、调解人

vocal  直言不讳的

sway   影响

1.strategy analysis 战略分析

定义问题

2.requirements analysis & design difination 需求分析与设计定义

3.solution evaluation 方案评估

前提：已完成解决方案。BA不提供解决方案，给解决方案提建议，例如修改组织架构。了解解决方案的使用情况等。

4.elicitation & collaboration 启发（挖掘需求）与协作

5.requirements life cycle management 需求生命周期管理

6.business analysis planning & monitoring 业务分析计划与监控

对工作实际效果监控，规划工作预期

knowledge area tasks包括：

inputs（必须有），outpus，guidelines & tools（非必须，着重理解，不用背），stakeholders，techniques，elements

characteristics of a task

模块化，顺序，迭代，不是方法论，没有流程，类似工具箱，提供工具

transition requirement过渡需求