Scope Management – Feedback Required

Home Forums APM PMQ Study Group Scope Management – Feedback Required

This topic contains 2 replies, has 2 voices, and was last updated by  Brian Holt 1 year, 11 months ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #14597

    Brian Holt
    Participant

    Explain two reasons why the scope of a project may need to
    be changed (20 Marks) ?

    User has changed their mind during UAT

    As a result of changes to legislation
    During the user acceptance
    testing users may identify additional requirements which were not originally
    identified or captured during the definition stage of a project. For example
    users working on mobile equipment will be moving to a new site (but this site
    does not currently have WIFI hotspots installed). This would involve an
    assessment of timescales to deploy new equipment and an assessment of costs to
    deploy new WI FI hotspots or considering alternatives such as 4g.
    As a result to changes to
    legislation a project may be forced to introduce change. For instance when the
    Data Protection Act came into force our IT system development project needed to
    be extended to take into account the new principles including not keeping the
    data for longer than is necessary. We therefore needed to provide new
    functionality on record retention for certain categories of records held within
    the system.
    Explain 3 ways in which change control can reduce and manage
    scope creep on a project (30 Marks) ?
    Existance of a change contro process
    Introduce change freeze to safeguard delivery
    Provides scrutiny to change and justification for re baseline
    As the change control process is documented within the PMP and
    agreed at the definition stage. The existence of a change control process can
    reduce the number of changes that are requested. Users are often dissuaded from
    making requests knowing that a formal process exists and that a business
    justification will be required before consideration. This reduces the
    possibility of scope creep from occurring.
    At later stages of the development and as the project nears
    its implementation date, a change freeze may be introduced to prevent any
    further changes which could impact on the quality, timescales and costs for
    delivery. If the project has a business critical drop dead date the change
    freeze acts a barrier to prevent any more changes from causing uncertainty in
    the ability to deliver. In software configuration management tools allow
    branching to protect the pre go live code.
    All changes need to be approved through the change control
    process. Initial assessment weeds out duplicate requests and changes previously
    considered and rejected. Changes which go through the full assessment have been
    fully approved in terms of their justification and impact to the baselined PMP.
    Changes which are approved facilitate a new baseline and the change control
    provides a justified reasoning as to why the baseline has moved.

    #14598

    Paul Naybour
    Moderator

    Brian Parallel is a premium provider of APMP training and we provide support to this study group for our customer who are taking either a face-to-face, distance learning or virtual APMP. It not really meant for to support candidates from other training providers, you should really be getting your support from your training provider. Having said that your answers are well structured and contain sufficient detail to get the marks. Maybe you will recommend Parallel Project Training to your friends and colleges. Good luck with your course next week.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.