如题所述
第1个回答 2022-07-01
项目管理过程的目的是在项目需求和约束的背景下, 识别、建立和控制项目生成产品所必需的活动和资源。
简单来说是指:通过对<项目实施所必要活动(必要活动能保证输出质量)> 和 <资源(人力资源、设备资源等)>的管理,使项目能达成既定的项目目标,如时间目标、质量目标、成本目标等。
接下来我们来看一下VDA Guideline中的相关规则:
(1) 工作范围
<ASPICE模型要求>
MAN.3.BP1: 定义工作范围 / Define the scope of work
确定项目的目标、动机和边界
Identify the project's goals, motivation and boundaries.
项目的工作范围包括项目范围和产品范围;项目的内容、边界、限制、项目目标等。
[MAN.3.RL.1] If the scope of work (BP1) is a product description only, the indicator BP1 must not be rated higher than L.
老杨解读:如果工作范围仅仅是产品描述,则BP1的打分不能高于L。
[MAN.3.RC.1] If the scope of work (BP1) does not address the responsibilities of all affected parties regarding the project and product, the indicator BP1 should not be rated higher than L.
老杨解读:如果工作范围没有考虑所有项目和产品的相关方的责任划分,则BP1的打分不能高于L。
[MAN.3.RL.2] If the scope of work (BP1) is not appropriately documented at project start, the indicator BP1 must not be rated higher than L.
老杨解读:如果工作范围没有在项目开始时文档化,则BP1的打分不能高于L。
(2) 承诺
<ASPICE模型要求>
MAN.3.BP1: 定义工作范围 / Define the scope of work
确定项目的目标、动机和边界
Identify the project's goals, motivation and boundaries.
MAN.3.BP3: 评估项目的可行性 / Evaluate feasibility of the project
在时间、项目估计和可用资源范围内,在技术限制的范围内,评估实现项目目标的可行性。
Evaluate the feasibility of achieving the goals of the project in terms of technical feasibility within constraints with respect to time, project estimates, and available resources.
MAN.3.BP5: 定义、监控和调整项目估计和资源 / Define, monitor and adjust project estimates and resources
根据项目目标、项目风险、项目理由和边界,定义、监控和调整项目工作量和资源的估计。
Define, monitor, and adjust project estimates of effort and resources based on project's goals, project risks, motivation and boundaries
MAN.3.BP8: 定义、监控和调整项目进度 / Define, monitor and adjust project schedule
为活动分配资源,并安排整个项目中的每一项活动的日程安排。在项目生命周期内,项目日程安排必须持续更新。
Allocate resources to activities, and schedule each activity of the whole project. The schedule has to be kept continuously updated during lifetime of the project.
[MAN.3.RC.2] If the commitment is not fulfilled by delaying the timeline of the project or by cancelling functionality etc., the indicators BP1 and BP3 should not be rated higher than L.
老杨解读:如果未能通过延迟项目时间或取消功能等方式履行承诺,则BP1和BP3的打分不应高于L。
[MAN.3.RL.3] If the commitment is not fulfilled by delaying the timeline of the project or by cancelling functionality etc., the indicator BP5 and BP8 must not be rated higher than L.
老杨解读:如果未能通过延迟项目时间或取消功能等方式履行承诺,则BP5和BP8的打分不应高于L。
注:与相关方达成一致后的项目交付时间延迟或功能取消是可以的。
(3) 活动定义
<ASPICE模型要求>
MAN.3.BP4: 定义、监控和调整项目活动 / Define, monitor and adjust project activities
根据定义的项目生命周期和预估,定义、监视和调整项目活动及其依赖关系。根据需要调整活动及其依赖关系。
Define, monitor and adjust project activities and their dependencies according to defined project life cycle and estimations. Adjust activities and their dependencies as required
MAN.3.BP8: 定义、监控和调整项目进度 / Define, monitor and adjust project schedule
为活动分配资源,并安排整个项目中的每一项活动的日程安排。在项目生命周期内,项目日程安排必须持续更新。
Allocate resources to activities, and schedule each activity of the whole project. The schedule has to be kept continuously updated during lifetime of the project.
[MAN.3.RC.3] If the activities are not described with input and output artifacts, the indicator BP4 should not be rated higher than P.
老杨解读:如果活动定义中未包括输入和输出,则BP4的打分不能高于P。
[MAN.3.RC.4] If the dependencies between activities are not identified, the indicator BP4 should not be rated higher than L.
老杨解读:如果未识别活动之间的依赖关系,则BP4的打分不能高于L。
[MAN.3.RC.5] If the work packages are too big (e.g. longer than the update cycle for the schedule), the indicator BP8 should be down-rated.
老杨解读:如果工作包的颗粒度太大(如:大于Schedule的更新周期),则BP8的打分应降低。
注:Schedule中Work Package的颗粒度需要小于项目的监控周期(如:周),如果存在特殊的Case,无法拆分,则也不能超过2个项目监控周期。
(4) 工作量和资源估计
<ASPICE模型要求>
MAN.3.BP5: 定义、监控和调整项目估计和资源 / Define, monitor and adjust project estimates and resources
根据项目目标、项目风险、项目理由和边界,定义、监控和调整项目工作量和资源的估计。
Define, monitor, and adjust project estimates of effort and resources based on project's goals, project risks, motivation and boundaries
[MAN.3.RC.6] If the estimation method used is not comprehensible, the indicator BP5 should not be rated higher than P.
老杨解读:如果使用的估计方法是不可理解的,则BP5的打分不能高于P。
[MAN.3.RC.7] If the estimates are too high level, e.g. based on high-level packages rather than on actual activities, the indicator BP5 should not be rated higher than P.
老杨解读:如果估计的颗粒度太高,如:基于高层次的工作包,而不是基于实际的活动,则BP5的打分不能高于P。
[MAN.3.RC.8] If there are not sufficient resources to cover the estimated effort, the indicator BP5 should not be rated higher than P.
老杨解读:如果缺少足够的资源来满足预计的工作量,则BP5的打分不能高于P。
[MAN.3.RC.9] If the resources are sufficient to cover the estimates but a monitoring of actual effort versus the estimates is missing, the indicator BP5 should not be rated higher than L.
老杨解读:如果有足够的资源来满足预计的工作量,但是缺少对工作量的监控,则BP5的打分不能高于L。
[MAN.3.RC.10] If the rationale for the estimates is missing, the indicator BP5 should not be rated higher than L.
老杨解读:如果缺失估计的必要理由,则BP5的打分不能高于L。
(5) 变更请求和问题解决(缺陷解决)的估计
<ASPICE模型要求>
MAN.3.BP2: 定义项目的生命周期 / Define project life cycle
定义项目的生命周期,与项目的范围、上下文、量级和复杂程度相适应。
Define the life cycle for the project, which is appropriate to the scope, context, magnitude and complexity of the project.
MAN.3.BP4: 定义、监控和调整项目活动 / Define, monitor and adjust project activities
根据定义的项目生命周期和预估,定义、监视和调整项目活动及其依赖关系。根据需要调整活动及其依赖关系。
Define, monitor and adjust project activities and their dependencies according to defined project life cycle and estimations. Adjust activities and their dependencies as required
MAN.3.BP5: 定义、监控和调整项目估计和资源 / Define, monitor and adjust project estimates and resources
根据项目目标、项目风险、项目理由和边界,定义、监控和调整项目工作量和资源的估计。
Define, monitor, and adjust project estimates of effort and resources based on project's goals, project risks, motivation and boundaries
MAN.3.BP8: 定义、监控和调整项目进度 / Define, monitor and adjust project schedule
为活动分配资源,并安排整个项目中的每一项活动的日程安排。在项目生命周期内,项目日程安排必须持续更新。
Allocate resources to activities, and schedule each activity of the whole project. The schedule has to be kept continuously updated during lifetime of the project.
[MAN.3.RC.11] If the definition of activities, effort and resource estimation, and the preparation of schedule(s) do not sufficiently reflect expectable change requests and problem resolution, the indicators BP4, BP5 and BP8 should be downrated.
老杨解读:如果在活动定义、工作量和资源估计、制定进度表等方面没有充分反映对变更请求或缺陷解决方面的考虑,则BP4, BP5, BP8的打分应降低。
[MAN.3.RC.12] If the project lifecycle does not contain phases that allow for addressing change requests and problem resolution, the indicator BP2 should be downrated.
老杨解读:如果项目生命周期中未考虑处理变更请求和缺陷解决的阶段,那么应该降低BP2的打分。
(6) 进度与跟踪
<ASPICE模型要求>
MAN.3.BP4: 定义、监控和调整项目活动 / Define, monitor and adjust project activities
根据定义的项目生命周期和预估,定义、监视和调整项目活动及其依赖关系。根据需要调整活动及其依赖关系。
Define, monitor and adjust project activities and their dependencies according to defined project life cycle and estimations. Adjust activities and their dependencies as required
MAN.3.BP5: 定义、监控和调整项目估计和资源 / Define, monitor and adjust project estimates and resources
根据项目目标、项目风险、项目理由和边界,定义、监控和调整项目工作量和资源的估计。
Define, monitor, and adjust project estimates of effort and resources based on project's goals, project risks, motivation and boundaries
MAN.3.BP7: 识别、监控和调整项目的接口和承诺 / Identify, monitor and adjust project interfaces and agreed commitments
项目与其它(子)项目、组织单元和其它受影响的利益相关者的接口,需要确定并达成一致,并监督已商定的承诺。
Identify and agree interfaces of the project with other (sub-) projects, organizational units and other affected stakeholders and monitor agreed commitments.
MAN.3.BP8: 定义、监控和调整项目进度 / Define, monitor and adjust project schedule
为活动分配资源,并安排整个项目中的每一项活动的日程安排。在项目生命周期内,项目日程安排必须持续更新。
Allocate resources to activities, and schedule each activity of the whole project. The schedule has to be kept continuously updated during lifetime of the project.
MAN.3.BP9: 确保一致性 / Ensure consistency
确保项目计划的各部分之间的一致性,包括:项目估计、人员技能、活动、日程安排、相关方之间的接口和承诺。
Ensure that estimates, skills, activities, schedules, plans, interfaces, and commitments for the project are consistent across affected parties
MAN.3.BP10: 项目评审和项目进展报告 / Review and report progress of the project
定期评审和向所有相关方报告项目状态,关于项目活动在预计的工作量和日程上的达成情况。防止发现问题再次发生。
Regularly review and report the status of the project and the fulfillment of activities against estimated effort and duration to all affected parties. Prevent recurrence of problems identified.
[MAN.3.RC.13] If action items or corrective actions are not properly tracked to closure, the corresponding indicators BP4, BP5, BP7, BP8 and/or BP10 should be downrated.
老杨解读:如果行动项或纠正措施没有恰当的跟踪直至关闭,相应的BP4, BP5, BP7及BP10的打分应降低。
[MAN.3.RL.4] If the schedule is not based on the defined activities (BP4) and estimations (BP5), the indicators BP8 and BP9 must not be rated higher than P.
老杨解读:如果Schedule没有基于已定义的活动(BP4)和估计(BP5),则BP8和BP9的打分不能高于P。
[MAN.3.RL.5] If the schedule does not contain all of the following:
a start and end date,
duration,
degree of fulfillment (for monitoring purposes),
resources,
dependencies
the indicator BP8 must not be rated higher than L.
老杨解读:如果Schedule中没有包括:开始和结束时间、持续时间、进展完成情况、资源、依赖,则BP8的打分不能高于L。
[MAN.3.RL.6] If any of the following:
start and end date,
effort,
degree of fulfillment
is missing, the indicator BP8 must not be rated higher than P.
老杨解读:如果缺失"开始和结束时间"、"工作量"和"进展完成情况",则BP8的打分不能高于P。
[MAN.3.RL.7] If the schedule is changed without a documented reason, or the change is not documented, the indicator BP8 shall be downrated.
老杨解读:如果Schedule发生了变更但缺少文档化的原因,或变更没有被记录,则BP8的打分应降低。
[MAN.3.RL.8] If the degree of activity fulfillment as tracked in the schedule is not up to date (at least biweekly depending on the project scope and release plan), the indicator BP8 shall be downrated.
老杨解读:如果活动的进展没有在Schedule中及时更新,则BP8的打分应降低。
[MAN.3.RL.9] If the critical path in a schedule is not determined, the indicator BP8 shall be downrated.
老杨解读:如果未确定Schedule中的关键路径,则BP8的打分应降低。
(7) 项目实际进展
<ASPICE模型要求>
MAN.3.BP10: 项目评审和项目进展报告 / Review and report progress of the project
定期评审和向所有相关方报告项目状态,关于项目活动在预计的工作量和日程上的达成情况。防止发现问题再次发生。
Regularly review and report the status of the project and the fulfillment of activities against estimated effort and duration to all affected parties. Prevent recurrence of problems identified.
[MAN.3.RL.10] If monitoring does not assess the correlation of actual consumption of resources, meeting of deadlines and fulfillment of activities (i.e. progress of content), the indicator BP10 must not be rated higher than P.
老杨解读:如果在项目监控时,没有考虑资源的实际消耗、最后期限的满足和活动的完成(即内容的进度)之间的相关性,则BP10的打分不能高于P。
(8) 发布管理
<ASPICE模型要求>
MAN.3.BP4: 定义、监控和调整项目活动 / Define, monitor and adjust project activities
根据定义的项目生命周期和预估,定义、监视和调整项目活动及其依赖关系。根据需要调整活动及其依赖关系。
Define, monitor and adjust project activities and their dependencies according to defined project life cycle and estimations. Adjust activities and their dependencies as required
MAN.3.BP7: 识别、监控和调整项目的接口和承诺 / Identify, monitor and adjust project interfaces and agreed commitments
项目与其它(子)项目、组织单元和其它受影响的利益相关者的接口,需要确定并达成一致,并监督已商定的承诺。
Identify and agree interfaces of the project with other (sub-) projects, organizational units and other affected stakeholders and monitor agreed commitments.
MAN.3.BP8: 定义、监控和调整项目进度 / Define, monitor and adjust project schedule
为活动分配资源,并安排整个项目中的每一项活动的日程安排。在项目生命周期内,项目日程安排必须持续更新。
Allocate resources to activities, and schedule each activity of the whole project. The schedule has to be kept continuously updated during lifetime of the project.
[MAN.3.RL.11] If product release recipients are not considered as stakeholders, the indicator BP7 must not be rated higher than P.
老杨解读:如果产品发布的接受者没有被考虑为相关方,则BP7的打分不能高于P。
[MAN.3.RL.12] If product release deadlines or milestones are not reflected in schedules (consider also consistency across different schedules), the indicator BP8 must not be rated higher than P.
老杨解读:如果产品发布的时间点或里程碑没有在Schedule中考虑,则BP8的打分不能高于P。
[MAN.3.RL.13] If the scope of the current and next release is not identified in detail (features and/or functions per release), the indicators BP7 and BP8 must not be rated higher than P.
老杨解读:如果当前发布及下一次发布的范围没有被详细识别(每次发布的功能点),则BP7和BP8的打分不能高于P。
[MAN.3.RL.14] If the mid and long-term planning of the releases does not at least cover a latest release/milestone for features and/or functions, the indicators BP7 and BP8 must not be rated higher than L.
老杨解读:如果中期计划或长期计划中没有覆盖到当前发布或里程碑,则BP7和BP8的打分不能高于L。
[MAN.3.RL.15] If for the current and next release not all the expected activities are planned and tracked (without a good reason), the indicators BP4, BP7 and BP8 shall not be rated higher than L. If less than 50% of the expected activities are planned, BP4, BP7, BP8 must not be rated higher than P.
老杨解读:如果当前发布及下一次发布中的所有活动没有被完全策划(且没有合适理由),则BP4, BP7和BP8的打分不能高于L;如果少于50%的活动没有策划,则BP4, BP7和BP8的打分不能高于P。
(9) 一致性
<ASPICE模型要求>
MAN.3.BP9: 确保一致性 / Ensure consistency
确保项目计划的各部分之间的一致性,包括:项目估计、人员技能、活动、日程安排、相关方之间的接口和承诺。
Ensure that estimates, skills, activities, schedules, plans, interfaces, and commitments for the project are consistent across affected parties
[MAN.3.RC.14] If links between different types of planning information are not supported by tools, this should not be used to downrate the indicator BP9.
老杨解读:如果项目计划相关的不同类型的信息之间的关联性不是依赖于工具,则不能基于此降低BP9的打分。
[MAN.3.RL.15] If the correlation between different plans or between estimates and plans is too high level or weak, the indicator BP9 shall be downrated.
老杨解读:如果项目计划相关的不同类型的信息之间的关联性的层次太高,则应降低BP9的打分。
(10) 风险
<ASPICE模型要求>
MAN.3.BP3: 评估项目的可行性 / Evaluate feasibility of the project
在时间、项目估计和可用资源范围内,在技术限制的范围内,评估实现项目目标的可行性。
Evaluate the feasibility of achieving the goals of the project in terms of technical feasibility within constraints with respect to time, project estimates, and available resources.
MAN.3.BP5: 定义、监控和调整项目估计和资源 / Define, monitor and adjust project estimates and resources
根据项目目标、项目风险、项目理由和边界,定义、监控和调整项目工作量和资源的估计。
Define, monitor, and adjust project estimates of effort and resources based on project's goals, project risks, motivation and boundaries
MAN.3.BP6: 确保所需的技能,知识和经验 / Ensure required skills, knowledge, and experience
根据估计,确定项目所需的技能、知识和经验,并确保选定的个人和团队及时具备这些技能和知识。
Identify the required skills, knowledge, and experience for the project in line with the estimates and make sure the selected individuals and teams either have or acquire these in time.
[MAN.3.RC.15] If risks regarding feasibility are not considered, the indicator BP3 should be downrated.
老杨解读:如果未考虑与项目可行性相关的风险,则应降低BP3的打分。
[MAN.3.RC.16] If risks regarding estimates or resources are not considered, the indicator BP5 should be downrated.
老杨解读:如果未考虑与工作量估计及资源相关的风险,则应降低BP5的打分。
[MAN.3.RC.17] If risks regarding skills or knowledge are not considered, the indicator BP6 should be downrated.
老杨解读:如果未考虑人员技能和知识相关的风险,则应降低BP6的打分。
简单来说是指:通过对<项目实施所必要活动(必要活动能保证输出质量)> 和 <资源(人力资源、设备资源等)>的管理,使项目能达成既定的项目目标,如时间目标、质量目标、成本目标等。
接下来我们来看一下VDA Guideline中的相关规则:
(1) 工作范围
<ASPICE模型要求>
MAN.3.BP1: 定义工作范围 / Define the scope of work
确定项目的目标、动机和边界
Identify the project's goals, motivation and boundaries.
项目的工作范围包括项目范围和产品范围;项目的内容、边界、限制、项目目标等。
[MAN.3.RL.1] If the scope of work (BP1) is a product description only, the indicator BP1 must not be rated higher than L.
老杨解读:如果工作范围仅仅是产品描述,则BP1的打分不能高于L。
[MAN.3.RC.1] If the scope of work (BP1) does not address the responsibilities of all affected parties regarding the project and product, the indicator BP1 should not be rated higher than L.
老杨解读:如果工作范围没有考虑所有项目和产品的相关方的责任划分,则BP1的打分不能高于L。
[MAN.3.RL.2] If the scope of work (BP1) is not appropriately documented at project start, the indicator BP1 must not be rated higher than L.
老杨解读:如果工作范围没有在项目开始时文档化,则BP1的打分不能高于L。
(2) 承诺
<ASPICE模型要求>
MAN.3.BP1: 定义工作范围 / Define the scope of work
确定项目的目标、动机和边界
Identify the project's goals, motivation and boundaries.
MAN.3.BP3: 评估项目的可行性 / Evaluate feasibility of the project
在时间、项目估计和可用资源范围内,在技术限制的范围内,评估实现项目目标的可行性。
Evaluate the feasibility of achieving the goals of the project in terms of technical feasibility within constraints with respect to time, project estimates, and available resources.
MAN.3.BP5: 定义、监控和调整项目估计和资源 / Define, monitor and adjust project estimates and resources
根据项目目标、项目风险、项目理由和边界,定义、监控和调整项目工作量和资源的估计。
Define, monitor, and adjust project estimates of effort and resources based on project's goals, project risks, motivation and boundaries
MAN.3.BP8: 定义、监控和调整项目进度 / Define, monitor and adjust project schedule
为活动分配资源,并安排整个项目中的每一项活动的日程安排。在项目生命周期内,项目日程安排必须持续更新。
Allocate resources to activities, and schedule each activity of the whole project. The schedule has to be kept continuously updated during lifetime of the project.
[MAN.3.RC.2] If the commitment is not fulfilled by delaying the timeline of the project or by cancelling functionality etc., the indicators BP1 and BP3 should not be rated higher than L.
老杨解读:如果未能通过延迟项目时间或取消功能等方式履行承诺,则BP1和BP3的打分不应高于L。
[MAN.3.RL.3] If the commitment is not fulfilled by delaying the timeline of the project or by cancelling functionality etc., the indicator BP5 and BP8 must not be rated higher than L.
老杨解读:如果未能通过延迟项目时间或取消功能等方式履行承诺,则BP5和BP8的打分不应高于L。
注:与相关方达成一致后的项目交付时间延迟或功能取消是可以的。
(3) 活动定义
<ASPICE模型要求>
MAN.3.BP4: 定义、监控和调整项目活动 / Define, monitor and adjust project activities
根据定义的项目生命周期和预估,定义、监视和调整项目活动及其依赖关系。根据需要调整活动及其依赖关系。
Define, monitor and adjust project activities and their dependencies according to defined project life cycle and estimations. Adjust activities and their dependencies as required
MAN.3.BP8: 定义、监控和调整项目进度 / Define, monitor and adjust project schedule
为活动分配资源,并安排整个项目中的每一项活动的日程安排。在项目生命周期内,项目日程安排必须持续更新。
Allocate resources to activities, and schedule each activity of the whole project. The schedule has to be kept continuously updated during lifetime of the project.
[MAN.3.RC.3] If the activities are not described with input and output artifacts, the indicator BP4 should not be rated higher than P.
老杨解读:如果活动定义中未包括输入和输出,则BP4的打分不能高于P。
[MAN.3.RC.4] If the dependencies between activities are not identified, the indicator BP4 should not be rated higher than L.
老杨解读:如果未识别活动之间的依赖关系,则BP4的打分不能高于L。
[MAN.3.RC.5] If the work packages are too big (e.g. longer than the update cycle for the schedule), the indicator BP8 should be down-rated.
老杨解读:如果工作包的颗粒度太大(如:大于Schedule的更新周期),则BP8的打分应降低。
注:Schedule中Work Package的颗粒度需要小于项目的监控周期(如:周),如果存在特殊的Case,无法拆分,则也不能超过2个项目监控周期。
(4) 工作量和资源估计
<ASPICE模型要求>
MAN.3.BP5: 定义、监控和调整项目估计和资源 / Define, monitor and adjust project estimates and resources
根据项目目标、项目风险、项目理由和边界,定义、监控和调整项目工作量和资源的估计。
Define, monitor, and adjust project estimates of effort and resources based on project's goals, project risks, motivation and boundaries
[MAN.3.RC.6] If the estimation method used is not comprehensible, the indicator BP5 should not be rated higher than P.
老杨解读:如果使用的估计方法是不可理解的,则BP5的打分不能高于P。
[MAN.3.RC.7] If the estimates are too high level, e.g. based on high-level packages rather than on actual activities, the indicator BP5 should not be rated higher than P.
老杨解读:如果估计的颗粒度太高,如:基于高层次的工作包,而不是基于实际的活动,则BP5的打分不能高于P。
[MAN.3.RC.8] If there are not sufficient resources to cover the estimated effort, the indicator BP5 should not be rated higher than P.
老杨解读:如果缺少足够的资源来满足预计的工作量,则BP5的打分不能高于P。
[MAN.3.RC.9] If the resources are sufficient to cover the estimates but a monitoring of actual effort versus the estimates is missing, the indicator BP5 should not be rated higher than L.
老杨解读:如果有足够的资源来满足预计的工作量,但是缺少对工作量的监控,则BP5的打分不能高于L。
[MAN.3.RC.10] If the rationale for the estimates is missing, the indicator BP5 should not be rated higher than L.
老杨解读:如果缺失估计的必要理由,则BP5的打分不能高于L。
(5) 变更请求和问题解决(缺陷解决)的估计
<ASPICE模型要求>
MAN.3.BP2: 定义项目的生命周期 / Define project life cycle
定义项目的生命周期,与项目的范围、上下文、量级和复杂程度相适应。
Define the life cycle for the project, which is appropriate to the scope, context, magnitude and complexity of the project.
MAN.3.BP4: 定义、监控和调整项目活动 / Define, monitor and adjust project activities
根据定义的项目生命周期和预估,定义、监视和调整项目活动及其依赖关系。根据需要调整活动及其依赖关系。
Define, monitor and adjust project activities and their dependencies according to defined project life cycle and estimations. Adjust activities and their dependencies as required
MAN.3.BP5: 定义、监控和调整项目估计和资源 / Define, monitor and adjust project estimates and resources
根据项目目标、项目风险、项目理由和边界,定义、监控和调整项目工作量和资源的估计。
Define, monitor, and adjust project estimates of effort and resources based on project's goals, project risks, motivation and boundaries
MAN.3.BP8: 定义、监控和调整项目进度 / Define, monitor and adjust project schedule
为活动分配资源,并安排整个项目中的每一项活动的日程安排。在项目生命周期内,项目日程安排必须持续更新。
Allocate resources to activities, and schedule each activity of the whole project. The schedule has to be kept continuously updated during lifetime of the project.
[MAN.3.RC.11] If the definition of activities, effort and resource estimation, and the preparation of schedule(s) do not sufficiently reflect expectable change requests and problem resolution, the indicators BP4, BP5 and BP8 should be downrated.
老杨解读:如果在活动定义、工作量和资源估计、制定进度表等方面没有充分反映对变更请求或缺陷解决方面的考虑,则BP4, BP5, BP8的打分应降低。
[MAN.3.RC.12] If the project lifecycle does not contain phases that allow for addressing change requests and problem resolution, the indicator BP2 should be downrated.
老杨解读:如果项目生命周期中未考虑处理变更请求和缺陷解决的阶段,那么应该降低BP2的打分。
(6) 进度与跟踪
<ASPICE模型要求>
MAN.3.BP4: 定义、监控和调整项目活动 / Define, monitor and adjust project activities
根据定义的项目生命周期和预估,定义、监视和调整项目活动及其依赖关系。根据需要调整活动及其依赖关系。
Define, monitor and adjust project activities and their dependencies according to defined project life cycle and estimations. Adjust activities and their dependencies as required
MAN.3.BP5: 定义、监控和调整项目估计和资源 / Define, monitor and adjust project estimates and resources
根据项目目标、项目风险、项目理由和边界,定义、监控和调整项目工作量和资源的估计。
Define, monitor, and adjust project estimates of effort and resources based on project's goals, project risks, motivation and boundaries
MAN.3.BP7: 识别、监控和调整项目的接口和承诺 / Identify, monitor and adjust project interfaces and agreed commitments
项目与其它(子)项目、组织单元和其它受影响的利益相关者的接口,需要确定并达成一致,并监督已商定的承诺。
Identify and agree interfaces of the project with other (sub-) projects, organizational units and other affected stakeholders and monitor agreed commitments.
MAN.3.BP8: 定义、监控和调整项目进度 / Define, monitor and adjust project schedule
为活动分配资源,并安排整个项目中的每一项活动的日程安排。在项目生命周期内,项目日程安排必须持续更新。
Allocate resources to activities, and schedule each activity of the whole project. The schedule has to be kept continuously updated during lifetime of the project.
MAN.3.BP9: 确保一致性 / Ensure consistency
确保项目计划的各部分之间的一致性,包括:项目估计、人员技能、活动、日程安排、相关方之间的接口和承诺。
Ensure that estimates, skills, activities, schedules, plans, interfaces, and commitments for the project are consistent across affected parties
MAN.3.BP10: 项目评审和项目进展报告 / Review and report progress of the project
定期评审和向所有相关方报告项目状态,关于项目活动在预计的工作量和日程上的达成情况。防止发现问题再次发生。
Regularly review and report the status of the project and the fulfillment of activities against estimated effort and duration to all affected parties. Prevent recurrence of problems identified.
[MAN.3.RC.13] If action items or corrective actions are not properly tracked to closure, the corresponding indicators BP4, BP5, BP7, BP8 and/or BP10 should be downrated.
老杨解读:如果行动项或纠正措施没有恰当的跟踪直至关闭,相应的BP4, BP5, BP7及BP10的打分应降低。
[MAN.3.RL.4] If the schedule is not based on the defined activities (BP4) and estimations (BP5), the indicators BP8 and BP9 must not be rated higher than P.
老杨解读:如果Schedule没有基于已定义的活动(BP4)和估计(BP5),则BP8和BP9的打分不能高于P。
[MAN.3.RL.5] If the schedule does not contain all of the following:
a start and end date,
duration,
degree of fulfillment (for monitoring purposes),
resources,
dependencies
the indicator BP8 must not be rated higher than L.
老杨解读:如果Schedule中没有包括:开始和结束时间、持续时间、进展完成情况、资源、依赖,则BP8的打分不能高于L。
[MAN.3.RL.6] If any of the following:
start and end date,
effort,
degree of fulfillment
is missing, the indicator BP8 must not be rated higher than P.
老杨解读:如果缺失"开始和结束时间"、"工作量"和"进展完成情况",则BP8的打分不能高于P。
[MAN.3.RL.7] If the schedule is changed without a documented reason, or the change is not documented, the indicator BP8 shall be downrated.
老杨解读:如果Schedule发生了变更但缺少文档化的原因,或变更没有被记录,则BP8的打分应降低。
[MAN.3.RL.8] If the degree of activity fulfillment as tracked in the schedule is not up to date (at least biweekly depending on the project scope and release plan), the indicator BP8 shall be downrated.
老杨解读:如果活动的进展没有在Schedule中及时更新,则BP8的打分应降低。
[MAN.3.RL.9] If the critical path in a schedule is not determined, the indicator BP8 shall be downrated.
老杨解读:如果未确定Schedule中的关键路径,则BP8的打分应降低。
(7) 项目实际进展
<ASPICE模型要求>
MAN.3.BP10: 项目评审和项目进展报告 / Review and report progress of the project
定期评审和向所有相关方报告项目状态,关于项目活动在预计的工作量和日程上的达成情况。防止发现问题再次发生。
Regularly review and report the status of the project and the fulfillment of activities against estimated effort and duration to all affected parties. Prevent recurrence of problems identified.
[MAN.3.RL.10] If monitoring does not assess the correlation of actual consumption of resources, meeting of deadlines and fulfillment of activities (i.e. progress of content), the indicator BP10 must not be rated higher than P.
老杨解读:如果在项目监控时,没有考虑资源的实际消耗、最后期限的满足和活动的完成(即内容的进度)之间的相关性,则BP10的打分不能高于P。
(8) 发布管理
<ASPICE模型要求>
MAN.3.BP4: 定义、监控和调整项目活动 / Define, monitor and adjust project activities
根据定义的项目生命周期和预估,定义、监视和调整项目活动及其依赖关系。根据需要调整活动及其依赖关系。
Define, monitor and adjust project activities and their dependencies according to defined project life cycle and estimations. Adjust activities and their dependencies as required
MAN.3.BP7: 识别、监控和调整项目的接口和承诺 / Identify, monitor and adjust project interfaces and agreed commitments
项目与其它(子)项目、组织单元和其它受影响的利益相关者的接口,需要确定并达成一致,并监督已商定的承诺。
Identify and agree interfaces of the project with other (sub-) projects, organizational units and other affected stakeholders and monitor agreed commitments.
MAN.3.BP8: 定义、监控和调整项目进度 / Define, monitor and adjust project schedule
为活动分配资源,并安排整个项目中的每一项活动的日程安排。在项目生命周期内,项目日程安排必须持续更新。
Allocate resources to activities, and schedule each activity of the whole project. The schedule has to be kept continuously updated during lifetime of the project.
[MAN.3.RL.11] If product release recipients are not considered as stakeholders, the indicator BP7 must not be rated higher than P.
老杨解读:如果产品发布的接受者没有被考虑为相关方,则BP7的打分不能高于P。
[MAN.3.RL.12] If product release deadlines or milestones are not reflected in schedules (consider also consistency across different schedules), the indicator BP8 must not be rated higher than P.
老杨解读:如果产品发布的时间点或里程碑没有在Schedule中考虑,则BP8的打分不能高于P。
[MAN.3.RL.13] If the scope of the current and next release is not identified in detail (features and/or functions per release), the indicators BP7 and BP8 must not be rated higher than P.
老杨解读:如果当前发布及下一次发布的范围没有被详细识别(每次发布的功能点),则BP7和BP8的打分不能高于P。
[MAN.3.RL.14] If the mid and long-term planning of the releases does not at least cover a latest release/milestone for features and/or functions, the indicators BP7 and BP8 must not be rated higher than L.
老杨解读:如果中期计划或长期计划中没有覆盖到当前发布或里程碑,则BP7和BP8的打分不能高于L。
[MAN.3.RL.15] If for the current and next release not all the expected activities are planned and tracked (without a good reason), the indicators BP4, BP7 and BP8 shall not be rated higher than L. If less than 50% of the expected activities are planned, BP4, BP7, BP8 must not be rated higher than P.
老杨解读:如果当前发布及下一次发布中的所有活动没有被完全策划(且没有合适理由),则BP4, BP7和BP8的打分不能高于L;如果少于50%的活动没有策划,则BP4, BP7和BP8的打分不能高于P。
(9) 一致性
<ASPICE模型要求>
MAN.3.BP9: 确保一致性 / Ensure consistency
确保项目计划的各部分之间的一致性,包括:项目估计、人员技能、活动、日程安排、相关方之间的接口和承诺。
Ensure that estimates, skills, activities, schedules, plans, interfaces, and commitments for the project are consistent across affected parties
[MAN.3.RC.14] If links between different types of planning information are not supported by tools, this should not be used to downrate the indicator BP9.
老杨解读:如果项目计划相关的不同类型的信息之间的关联性不是依赖于工具,则不能基于此降低BP9的打分。
[MAN.3.RL.15] If the correlation between different plans or between estimates and plans is too high level or weak, the indicator BP9 shall be downrated.
老杨解读:如果项目计划相关的不同类型的信息之间的关联性的层次太高,则应降低BP9的打分。
(10) 风险
<ASPICE模型要求>
MAN.3.BP3: 评估项目的可行性 / Evaluate feasibility of the project
在时间、项目估计和可用资源范围内,在技术限制的范围内,评估实现项目目标的可行性。
Evaluate the feasibility of achieving the goals of the project in terms of technical feasibility within constraints with respect to time, project estimates, and available resources.
MAN.3.BP5: 定义、监控和调整项目估计和资源 / Define, monitor and adjust project estimates and resources
根据项目目标、项目风险、项目理由和边界,定义、监控和调整项目工作量和资源的估计。
Define, monitor, and adjust project estimates of effort and resources based on project's goals, project risks, motivation and boundaries
MAN.3.BP6: 确保所需的技能,知识和经验 / Ensure required skills, knowledge, and experience
根据估计,确定项目所需的技能、知识和经验,并确保选定的个人和团队及时具备这些技能和知识。
Identify the required skills, knowledge, and experience for the project in line with the estimates and make sure the selected individuals and teams either have or acquire these in time.
[MAN.3.RC.15] If risks regarding feasibility are not considered, the indicator BP3 should be downrated.
老杨解读:如果未考虑与项目可行性相关的风险,则应降低BP3的打分。
[MAN.3.RC.16] If risks regarding estimates or resources are not considered, the indicator BP5 should be downrated.
老杨解读:如果未考虑与工作量估计及资源相关的风险,则应降低BP5的打分。
[MAN.3.RC.17] If risks regarding skills or knowledge are not considered, the indicator BP6 should be downrated.
老杨解读:如果未考虑人员技能和知识相关的风险,则应降低BP6的打分。