Learning outcome 7 Flashcards
7.1 Explain how to define scope in terms of outputs, outcomes and benefits
WHAT- SCOPE OF PRODUCT
WHY- Outlining what will and will not be included in the product. Defining the scope of the product is one of the most important parts of the project as without it there would be no indication of what will be required to create it. Having a firmly defined scope of product outlined in the PMP by the PM in definitions will allow for all the other tasks follow such as resourcing, procurement and understanding the TCQ constraints that will affect the project.
What- scope of outcome, what the beneficial change is going to look like, the corporate vision
Scope of benefits… Stakeholders in concept … By outlining what is expected to be seen as a benefit and not seen will allow the SPONSOR the ability to measure success using the benefits review plan after the product has been adopted into BAU.
7.2 Explain how to establish scope through requirements management processes
WHAT- CAPTURE
WHY
Talk to users-Series of meetings
See what they want Hi lvl
Produces a success Criteria (Fuzzy- I want economical car)
WHAT- ANALYSE
Make sense of success criteria
Get USER STORIES
Conflicts
Overlaps
Is it achievable
Looking at solutions
looking at constraints and technologies etc
PRODUCE ACCEPTANCE CRITERIA
WHAT-JUSTIFY
Moscow
Snr Stakeholders- Rep of User group
Iterative to keep going back to justify
WHAT- BASELINE AGREEMENT
This is the scope!!
Board agrees
Done in definitions before you make it
7.3 Explain how to manage scope through configuration management process
PICSA
Planning- What do we want to put in? IE Laptops, not mouse- The more control more bureaucracy.
Identify- Identify everything about it, appoint owner
Control- Who can approve doc? Who can use laptop?
Status accounting- Version and changes that have happened. Needs to be up to date to feed back into change control!!!
Audit- Independent check- Reassurance, have you actually got it?
7.4 Explain different stages of typical change control process
REACTIVE PROCESS!!
REQUEST- from stakeholder, log. Keep for lessons learned- long project lots of changes
REVIEW- quick, easy decision, requested before still no, will take too much time. Within authority?
ASSES- Detailed examination, time consuming. Go to coal face first, SME’s project team, they know what’s capable!!
ESCELEATE- WITH RECOMMENDATION!! To SPONSOR- Makes an informed decision
UPDATE PLANS- REBASELINE on constraints, scope, risk, benefits etc
IMPLEMENT new plan
GOOD- Process in place, lessons learned, good for business if from customer £, Communication
BAD- Stakeholder relationship if it’s a no! can be seen as blocking creativity. Time consuming
