#1272 PRMG - proposed wording changes for clarity and readability change request accepted

From Jim Owens. Details attached below.

Project management PRMG

Currently	Suggested Change
typically (but not exclusively)	typically[1]
plan-driven/predictive approaches	plan-driven (predictive) approaches
or more adaptive (iterative and agile) approaches	or adaptive (iterative or agile) approaches

Project management: Level 7

Currently	Suggested Change
including application of appropriate methodologies.[2]	including selection of appropriate methodologies, and how they will be applied.
large scale projects	Large-scale projects
high impact, high risk projects	High-impact, high-risk projects
ensures that solutions to problems	ensures that treatment of risks and issues
in line with change control processes.	in line with change control policy

Project management: Level 6

Currently	Suggested Change
complex projects (typically with significant business, political, or high-profile impact, and high-risk dependencies)[3]	complex projects, which typically expose the organisation, and its reputation, to high-impact risk.
plan-driven/predictive approaches	plan-driven (predictive) approaches
or more adaptive (iterative and agile) approaches	or adaptive (iterative or agile) approaches
Ensures that effective project control, change control, risk management and testing processes are maintained.	Ensures that effective project monitoring[4] and control processes, change control, risk management and testing processes are employed and maintained.[5]
Monitors and controls resources, revenue and capital costs against	Monitors and controls resources, revenue and capital expenditures against[6]
manages expectations of all project stakeholders.	manages expectations of all key project stakeholders.
	Ensures that Lessons Learned from previous projects are reviewed for possible application to current projects.
	Ensures that Lessons Learned from current projects are recorded throughout the project.
	Ensures that own projects are formally closed and, where appropriate, subsequently reviewed, and that lessons learned are cupdated.

Project management: Level 5

Currently	Suggested Change
(typically with direct business impact and firm deadlines)	, typically with direct business impact and firm deadlines
assesses and manages risks to the success of the project	assesses and manages risk effectively[7]
or more adaptive (iterative and agile) approaches	or adaptive (iterative or agile) approaches
Ensures Quality reviews occur occur on schedule and according to procedure.	Ensures project and product Quality reviews occur on schedule and according to policy.
Manages the change control procedure,	Manages the change control process,
are completed within agreed cost, timescale and resource budgets,	are completed within agreed cost, timescale and scope,
and are signed off.[8]	and are formally accepted, by appropriate stakeholders.
	Monitors costs, times, quality and resources used, andtakes action where these exceed agreed tolerances
takes appropriate action where team performance deviates from agreed tolerances.	takes appropriate action where team performance exceeds agreed tolerances.
	Ensures that Lessons Learned from previous projects are reviewed for possible application to current projects.
	Ensures that Lessons Learned from current projects are recorded throughout the project.
	Ensures that own projects are formally closed and, where appropriate, subsequently reviewed, and that lessons learned are updated.

Project management: Level 4

Currently	Suggested Change
alone or with a small team, actively participating in all phases.	Working alone or with a small team, actively participating in all phases of the project.
manages risks to the success of the project	manages risk effectively.
plan-driven/predictive approaches	plan-driven (predictive) approaches
or more adaptive (iterative and agile) approaches	or adaptive (iterative or agile) approaches
	Ensures that Lessons Learned from current projects are recorded throughout the project.
and prepares realistic plans (including quality, risk and communications plans)	and prepares realistic project plan (including scope, schedule, quality, risk and communication plans)
Monitors costs, timescales and resources used	Monitors costs, times, quality and resources used
takes action where these deviate from[9] agreed tolerances	takes action where these exceed agreed tolerances
Ensures that own projects are formally closed and, where appropriate, subsequently reviewed, and that lessons learned are recorded.	Ensures that own projects are formally closed and, where appropriate, subsequently reviewed, and that lessons learned are updated.

[1] Redundant, but if used it should not be enclosed in brackets

[2] The sentence can be read as: the person is applying the methodologies - but in this context it needs to be clear that that person is merely directing how the methodologies will be applied

[3] This is a “dog’s breakfast”, and I’ve never heard of a “risk dependency”

[4] In keeping with the PMBOK Guide and PRINCE2

[5] No point in maintaining them if you aren’t going to use them.

[6] A “cost” may not be expended

[7] A Project Manager manages “risk” (i.e. overall project risk); the team manages “risks” (individual risk items). Compare with Level 7 description. The remainder of the sentence is redundant (and poor grammar)

[8] Too vague. This might mean signed off by the Team Manager, Project Manager, or even team member’s mother.

[9] Tolerances normally have an upper and lower limit. If a variable approaches e.g. the upper limit, it is still “within tolerance”, but has “deviated from” the agreed lower tolerance.

Proposed change applies to Project management

Current status of this request: accepted

What we decided

Included in overall readability review for SFIA 8