Professional Documents
Culture Documents
Strategic
Planning and Issues
Management
Learning Objectives
Identify some common triggering events that act as stimuli for strategic
change
Understand strategic decision-making modes
Use the strategic audit as a method of analyzing corporate functions and
activities
Sustainability
Refers to the use of business practices to manage the triple
bottom line
Institution theory
Organizations can and do
adapt to changing conditions
by imitating other successful
organizations
Strategic flexibility
the ability to shift from one dominant strategy to another and
requires:
Figure 1-1
Figure 1-2
1- Environmental scanning
the monitoring, evaluating and disseminating of information from
the external and internal environments to key people within the
organization
SWOT analysis
2 - Strategy formulation
Mission
the purpose or reason for the organization’s existence
Vision
describes what the organization would like to become
Objectives
the end results of planned activity
Strategy
forms a comprehensive master approach that states how the
corporation will achieve its mission and objectives
Policy
a broad guideline for decision making that links the
formulation of a strategy with its implementation
3- Strategy implementation
a process by which strategies and policies are put into action
through the development of programs, budgets and
procedures
Performance
the end result of organizational activities
includes the actual outcomes of the strategic management
process
Feedback/Learning process
revise or correct decisions based on performance
New CEO
External intervention
Threat of change of ownership
Performance gap
Strategic inflection point
Consequential
Directive
a means to assure all issues are visible to the entire team and all team members
can share accountability in issue resolution
Critical Significant impact on the project; the consequences may affect other projects or
halt the implementation; requires immediate resolution
Medium Cannot complete phase without resolution, but does not need to be addressed
immediately; may or may not require Leadership invention
Low Does not impact resources and schedule but requires resolution; may or may not
require Leadership intervention
Issue
Identify the Issue Log the Issue Qualify the Issue Issue Exists? YES Manage the Issue Escalation
Reqd?
1 2 3 5
Contact Assignee and
Team Lead
NO
NO
NO
Legend
1 Identify the Issue As the project progresses, it will be the responsibility of Input: N/A Any time Project Team
all team members to actively identify issues Output: Identified issue
2 Log the Issue Once the issue has been identified, it should be Input: Identified Issue Any time Project Team
immediately logged in the issue log (Excel – short term Output: Logged Issue (Coordinatory)
or Document Repository Tool - long term) for tracking.
To minimize access to the log, a coordinator (and
backup) will be designated , per team, to enter issues.
Note: When assigning an issue to another assignee,
particularly from another team, the assignee should
be notified via email of the assignment
3 Qualify the Issue The Project Manager will qualify the issue. If it is valid, Input: Logged Issue Any time Project Manager
the issue will continue into management (step 5). If Output: Issue Confirmed
the issue does not qualify as it issue, proceed to step 4
4 Track as Workplan If the issue does not qualify as it issue, it should be Input: Unqualified Issue Any time Project Manager
Task/Action Item and entered as a workplan task, action item or other, next Output: Closed Issue
Close Issue steps documented in the issue log and finally, the issue
closed
5 Manage the Issue Once an issue is qualified, it must be “worked” in order Input: Qualified Issue Any time Project Team
to drive to resolution. The proper resolution of an Output: Managed Issue
issue will vary depending on the circumstances of the
issue. It is key that all impacted parties should be
involved in reaching proper closure to an issue. This
involves completing Impact Assessments as necessary.
If at anytime, escalation is required to resolve an issue,
the status of the issue will change to escalated and
issue management will continue. If no escalation is
required, the issue will move forward for disposition
(step 6)
© Pearson Education Limited 2015 1-41
Process Steps
Ref Process Step Description Deliverable I/O Time Owner
ID Horizon
6 Issue Disposition There are several potential dispositions to an issue: Input: Managed Issue Any time Project Team
Resolution (step 7), Tracking as an Change Request Output: Managed Issue
(step 9), or Track as a Risk (step 10).
7 Resolve Issue In resolving an issue, it is important to involve all Input: Managed Issue Any time Project Team
impacted parties in the resolution process to minimize Output: Resolved Issue
additional problems downstream. The resolution
should be clearly documented in the issue log. The
resolution of an issue typically results in the following
impacts:
• 40%: Functional/Technical development
• 30%: Integration development
• 15%: Hardware
• 15%: Software
8 Close Issue & Execute Once the resolution has been documented, the issue Input: Resolved Issue Any time Project Team
Resolution Next Steps will be updated with next steps and the status changed Output: Closed Issue
to ‘closed’. The next steps will then be executed outside
of the issue process. Such next steps may include:
• Update workplan/action item plans
• Conduct follow up meetings/review sessions with
impacted parties (i.e. Technical, Data, etc)
• Identify/update relevant key deliverables based on
resolution
9 Close Issue & Log During the management of an issue, the problem may Input: Managed Issue Any time Project Team
Change Request escalate to a change request. At this point, the Output: New Change
resolution should be updated (closed and CR opened), Request
the status changed to ‘closed – CR initiated’ and a new
CR opened
10 Close Issue & Log Risk During the management of an issue, it may be Input: Managed Issue Any time Project Team
discovered that the problem has not yet occurred and is Output: New Risk
better tracked as a risk. The resolution should be
documented, the issue closed and a new risk logged
11 Update the Issue with If the issue and its resolution is deemed to be a key Input: Managed Issue Any time Project Manager
Decision Data decision that will have a significant impact on the Output: Key Decision
project/implementation, the issue log should be update
to reflect it is a key issue. Additionally, the key decision
makers should be noted at that time. If the Project
Manager wishes to later view all key decisions, the log
will be filtered accordingly.
There will be several meetings throughout the week where issues will be
discussed and managed.
Role Responsibility
Project Manager • Qualify issues
• Ensure proper logging of issues
• Drive tracking and resolution
• Manage issue escalation