4. Planning and managing performance Flashcards
- What is requirements management?
○ Throughout project life cycle - from initial phase of project - to facilitate development of agreed scope management
- What process do you need to go through for requirements management?
○ Gather - after stakeholder analysis - gather thoughts on requirements from stakeholders. Important to record what people want to get out of the project
○ Analysis - function analysis or function cost analysis will provide detail on value of requirements and how they will benefit the organisation. This can help identify where there are conflicts in requirement expectations. Consensus should be reached through discussions if gaps found
○ Justifying requirements - functional requirements which link to benefits should be prioritised (eg. Using MOSCOW). Then important to communicate outcomes to stakeholders to avoid misunderstandings
○ Baseline needs - Functional requirements form baseline of outcomes - then PM needs to determine deliverables linked to these, manage change and mitigate scope creep
- What is functional analysis?
○ Should only accept benefits at a cost that makes them worthwhile ie. Creates value for the organisation
○ Value must be created at beginning of project through dev of business case and options chosen - then maintained throughout project
○ Functional analysis helps identify cost to value of delivering project. Different ways of doing this but broadly involves looking at time and resource taken to change and contribution towards overall objective
○ Tests assumptions with key stakeholders
○ Output is agreed set of options for functional requirements - used to examine value of different solutions
○ Value highlighted is amount of benefit that will be gained from requirement to justify it’s priority
- What are some prioritisation techniques?
○ MoSCoW
§ Must have
§ Should have
§ Could have
§ Wont have
○ May get rid of shoulds and coulds if project running over cost
○ Way to manage disputes if must haves agreed and should haves etc established with stakeholders
- What is configuration management and what are the steps?
○ Way to plan, protect and control changes to requirements
○ Stages:
§ Planning - defines processes and procedures
§ Identification - divides project into different items that can be moved around - each with different name
§ Control - changes to these items controlled and relationships understood to understand impacts of interdependencies
§ Status accounting - ensures tracability throughout development. Recordkeeping
§ Verification audit - ensures deliverable confirms to requirements and configuration. Should be done throughout project lifecycle
- What is solutions development?
○ Systematic solution to identify analyse and implement responses to challenges and opportunities
○ Requires innovation and problem solving as new things emerge - ensures adaptability
○ Evaluates and prioritises different options to solve a problem - explores these until optimal solution arrived at
- What are some criteria to consider when identifiying solutions?
○ Technical - process material software
○ Social - people interactions needs
○ Procurement - lease buy make service
○ Management - lifecycle governance
○ Transition - phased or all at once
- How can you prioritise requirements within scope?
○ Can use MOSCOW again
○ Ensures essentials are met
○ Can also consider
§ Investment appraisel
§ Stakeholder commitment to solution
§ Market capability
○ Or can use these other tools
§ ABC model - level of importance
§ 5 whys method -why is this requirement necessary
§ Numerical assignment
- How are different approaches used for different life cycles?
○ Linear life cycle - options are analysed early on - optimum solution agreed with scope - then confirmed and managed through change control if needed
○ Iterative - can look at solutions for longer as the project develops - explore options and deliver in increments. Can have must have requirements in form of a minimum viable product. Following feedback options can be developed
- What is quality planning?
○ Process of establishing quality requirements
○ Uses defined scope and lists criteria to validate that outputs fit for purpose
○ Forms quality plan which approved by sponsor and wider board
○ Quality plan sets out “what good looks like” - compliance with regulations, work in scope in line with business case, how it will be assessed
○ Giodes quality control and assurance activities to confirm outputs meet requirements - require resource and influence tasks on project
○ Need to get stakeholder agreement on plan to support a handover
- What does a quality plan include?
○ Methods of verifiying outputs meet requirements
○ Pass and fail criteria
○ Frequency of tests or checks
○ Resources required to complete quality assurance
- What is quality management?
○ Verifiying compliance of output to requirements - quality assurance providing confidence that right processes and methods used to deliver it
○ In iterative life cycle - acceptance criteria defined at different phases - verified for the final product
What is the difference between quality control and quality assurance?
○ Quality control - outputs
§ Inspection measurement and testing to confirm project outputs meets acceptance criteria as previously set
§ Focussed on finding problems to stop them being an issue for customers
§ Member of project team
§ Plans test plans agreed during planning and managed through change control
§ Test plans must think about size of tests, test protocols, independent performance or test witnessing
§ Outputs checked against degree of conformance to requirements and crieria. If outputs don’t conform, decision on what to do needs to be made
§ Answer is either pass or fail - no in between
○ Quality assurance - processes
§ Build in quality using standard processes to ensure delivery is being done in the right way
§ Done by people independent to the project
§ Aims to maintain stakeholder confidence
§ Should be applied as soon as project management starts
§ In event of deviation - decision needed on what action is needed
§ Even is quality assurance not fully followed outputs can still be acceptable
- What is integrated planning?
○ Strategic approach combining planning processes to enhance efficiency coordination and communication
○ Brings together planning benefits, scope, quality, scheduling, budget risk and ommmunication into a single project management plan
- What is the project management plan?
○ Captures key components of plan to deliver outcomes
○ Coalating all existing documents etc into single place
○ Depends on size and complexity of pojrct
○ Should be integrated into everything and should set out the 5 Ws and how of a project
- What should a project management plan include?
○ Benefits - why? - BC - value of project benefits
○ Scope - what? - decription f scope involved - product and work breakdown
○ Time - when? Time needed, timeline, deliverables for each bit
○ Resources - who? Roles and responsibilities and reporting lines - organisational breakdown structure
○ Cost - how mcuh - how the budget has been assigned - cost breakdown structure
○ Delivery logistics - where? - delivery requirements, security, environmental constraints
○ Management - how? How deployment will be managed, risks and issues, comms etc
- What is an integrated PM Plan important?
○ Ensures:
§ Comms is presented to stakeholders
§ Reference source for all stakeholders
§ Contract between PM and project sponsor providing clarity on what’s expected
§ Guidance for project team
§ Baseline measurement to understand progress
- What is schedule management?
○ Finds best way to allocate resource (external and internal) and time
○ It:
§ It used to develop schedules of work
§ Time based and based on actual activities
§ Develop and maintain schedules
§ Shows when work is planned to be done
§ Considers dependencies
- What is scope and how do you define it?
○ Scope defined to outputs, outcomes and benefits - high level scope should be recorded in business case
- What are outputs, outcomes and benefits?
○ Tangible or intangible deliverables created which produce outcomes of changes circumstances, behaviours or practices to create benefits in line with acceptance criteria
Outputs -> outcomes -> benefits
- What are breakdown structures and what are some examples?
○ Different ways to illustrate what needs to be done to ensure project outputs are met
○ Product breakdown structure
○ Work breakdown structure
○ Cost breakdown structure
What is a product breakdown structure?
○ PBS identifies scope of project to be delivered - final output placed at top level and broken down by outputs - then next level etc until can’t be broken down any further ie. Individual products
- What is work breakdown structure?
○ Defines basline scope of work - activities needs to be completed to deliver requirements. Lower level of detail is by work package. WBS focusses on work and skills needed to do the work - work types can be grouped
- What is cost breakdown structure?
○ CBS financial view by breaking down project into cost elements - shows costs of people, equipment, materials etc - or costs of different parts of the organisation or external parties. Used to track achievement against spend