Gaps in knowledge Flashcards
Fill Gaps in knowledge
Kotter’s 8 step model
Create urgency
Powerful coalition
Vison
Communicate vision
Empower action
Quick wins
Make it stick
What is information management process?
Collection
Storage
Curation
Dissemination
Archiving
Destruction
IM - Collection explanation
Has to be a uniform filing structure with documents (digital, audio etc), how will it be collected? How sensitive is the information you have collected?
IM - Storage
Access levels considered, any legal implications of storing the information? Will it be digital or physical? How secure is it?
IM - Curation
make decisions about the data, how will it be ordered and sequenced
IM - Dissemination
Who needs the information and when? Look at with communications plan, what format will they receive it? Do the relevant people have access? If too much, may be overlooked, not enough. Reporting
IM - Archiving
Provides audit trail. Consideration before destruction is may be needed in future.
IM - Destruction
This has to be in accordance with legislation compliance- particularly if digital. Has to be unretrievable.
Explain different types of estimates (bottom up)
Delphi – subject matter experts
Analytical – WBS, CBS, PBS. Used when the scope is more clear
Explain different types of estimates (top down)
Analogous – from projects that you’ve done historically. Used when the organisation has a mature project history
Parametric - which is used by looking at data or units to multiply/ work out estimates. Used when there is scalable data available historically that can be used,
Explain 3 characteristics of a matrix organisation structure when used by an organisation to deliver a change initiative
Dual identities (PM also has functional role)
Works better with BAU for the change as there is some level of oversight into the functional side of business
Resources are drawn from BAU
Authority flows sideways between functional and PM
Explain 2 characteristics of a functional organisation structure when used by an organisation to deliver a change initiative
Usually smaller projects, functional manager manages project within department
No dedicated project team, done within BAU team
Authority flows downwards from functional manager
Explain 2 considerations when using an organisation breakdown structure to create a responsibility assignment matrix.
Cost of the resources that have been assigned
If the individuals within the structure have the knowledge and experience
Whether context has been considered in assigning responsibilities
Describe 2 ways in which a project management office can assist a project manager to successfully deliver a project.
Give the PM more time to work with the project team by dealing with administrative tasks.
Allocating resources by looking at what is available across the pool of the business
Provide consistency and ensure compliance
Explain 3 ways in which a project would be influenced by the implementation of project governance
Health and safety need to be considered in budget
Changes in legislation may impact scope
Change control (escalated may mean closing of project)
Explain the 3 differences between linear and iterative life cycles.
Linear has 4 defined phases – concept, definition, deployment, transition whereas iterative doesn’t have defined phases, but works in iterations/ time boxes. Linear usually gives deliverables at the end of the project, iterative deliverables can be throughout. Linear doesn’t necessarily need constant user feedback, iterative does.
Explain reasons why an iterative lifecycle might be used to deliver a project rather than a linear life cycle option.
Time is crucial, as iterative can start iterations pretty much start straight away. You have lots of access to user feedback. Scope isn’t clear at the start of the project. Project that is looking at product development or software, as iterative approach favours this kind of project due to constant amendments and user feedback. Used when predictable.
Linear is more for projects that have more risk, as there is a clear structure. May be used if resources need to be planned clearly across the project. Construction because need to know clear size and scale before you start
Explain 3 reasons why information management may support the effective management of a project.
Helps to generation of ideas and solutions
Avoids repetition of mistakes and improves lessons learnt
You can also anticipate and understand changing conditions
Cultivates talent management
Explain 3 benefits of conducting reviews throughout the lifecycle of a project.
Close early
Update stakeholders
Provide confidence
Manage risk
Failing fast
Plan resource for next phase
Helps sponsor oversight
Explain three ways in which projects and programmes can help an organisation deliver strategic change.
Tangible investment into the change
provides clear path to delivering change to show stakeholders
programmes may assist in changing BAU
rationalises resources to work to the change
Programmes can help manage the projects with similar goals to make sure they aligned to strategic change