Chapter 10 - Mgmt Issues is Sys Dev Flashcards
What is a project?
- Related tasks or activities
- Achieve a similar goal
- Within a certain period of time
What is the goal of project management?
Achieve the projects goals within the given constraints
Why are IT projects harder?
Usually projects deliver something tangible, but with IT projects you are delivering something intangible
What is IT project management?
Planning, organizing and delegating an info tech project
What are some roles of a project manager?
- Initiation, planning, designing, execution, monitoring, controlling and closure of a project
Also minimizing risk
End - Getting feedback
What are the five phases of PM?
Initialization (Bus Case + Project Charter)
Planning (Scope, Budget, WBS, Gantt, Comm plan, RM)
Execution (status tracking, KPI, forecasting)
Monitor Performance (Obj, quality deliverable, effort and cost tracking, performance)
Closure (post mortem, project punchlist, reporting)
What is the goal of project initiation?
Define the project at a high level
- bus case
- project feasibility
- Economic feasibility and other feasaibility
What is the goal of project planning?
Developing a roadmap everyone will follow
- two approaches to goal: SMART, CLEAR (collab, limited, emotional, appreciable, refineable)
Scope
PM Plan
Cost, qual, avail resources, realistic time table
Baseline and performance measures
What are some key docs in proj planning?
Scope statement
WBS
Milestones - high level goals, included in Gantt Charts
Gantt Charts
Communication plan (how and when communciate)
RM Plan - identify risks (unrealistic time, cost, customer review, budget cuts, lack of resources)
What is Project execution phase?
Phase where deliverables are developed and completed
What is the project monitoring performance phase?
Measuring project progression, ensuring everything aligns with PM plan
Use KPI to determine this.
PM will pick 2-5 KPIs
PM will detemrine if it is one time and on budget. If not, need to align back on track.
What is project closure
- Contractors terminated
- PM hold post mortem
- Project punchlist of stuff not complete
- Final budget and final report
- Store all documents
What is risk management?
The process of identifying and controlling threats to the project.
IT risks have become a top priority to digitized companies
What are some benefits to risk management?
- Safe ans secure work environment
- increases stability
- decreases liability
- provides protection against things thaat are bad for company and env
- protects all involved people
- helps insureance premiums
What is the RM Process?
Steps the PM can take to manage risks
1) Establish context (and criteria)
2) Risk identification
3) Risk anal (likelihood and consequences)
4) Risk mitigation
5) Risk monitoring
6) Communicate and consult
What are some risk strats?
Risk avoidance
Risk Reduction
Risk Sharing
Risk retaining - keep risk and deal with consequences
What is org change management?
Steps to take at a project level to support people who are impacted by project
Identifying who will have to change and in what ways
Creating a customized plan to ensure impacted people have awareness, leadership, coaching and training
What does enterprise change management mean?
Enterprises change management capabilites are embedded in roles, structs, processes, projects and leadership. effetively applied
Individuals embrace change more quckly and org can adopt new strats and tech quicker
What are the options for improving legacy systems?
1) Re-structuring - works fine but needs updating
2) Re-engineering - extracting and converting to new platform or hw
3) Refurbishing - adding new extensions to working old sys
4) Rejuvenate - addomg new features to existing system, e.g. increased efficiency
5) Re-architect - New arch
6) Replace
7) Re-write
What is the project charter?
Acts as the one source of truth for the project. Spells out the why, what, when, who and how.
Explain the risk management decision tree
There are three factors that influence risk:
- leadership of bus change
- employee perspective of bus change
- scope and urgency of change
Use the decision tree to map change
Greatest contributor of three on the left -> right
+ positive support for change
- negative support for change
Likelihood is high at top, low at bottom
PM methods mapped on the right
What are the options for improving a legacy system?
From low change to high change:
1) Restructure - make code maintainable
2) Reengineer - Move to new platform
3) Refurbish - enhance i/o
4) Rejuvenate - Give it a new more strategic role
5) Re-architect - modularize via new blueprint
6) Replace - buy new sw
7) Rewrite - make new from scratch
