Please respond to both POST1: and POST2: in at least 200 words. I have also included the original post for your reference when responding to both POST1 and 2.

Original post:

Describe the function and importance of scope control in managingprojects and name the tools and techniques that the textbook and PMBOK® Guide, 6^thedition identify as the tools and techniques used for scope control.Select one of these tools and provide an example to describe how youwould use this tool in a typical project in your field of practice.

POST1:

Scope Control

Scope control in managing projects is a very important process sinceit is used to accomplish a project while still sustaining the projectrequirements and meeting the overall project goals. According to theProject Management Institute (2017), control scope is the process ofmonitoring the status of the project and product scope and managingchanges to the scope baseline; the key benefit of this process is thatthe scope baseline is maintained throughout the project. When scopecontrol is not being managed efficiently is when scope creep can occur.Scope creep is defined as uncontrolled expansion to product or projectscope without adjustments to time, cost, and resources (ProjectManagement Institute, 2017). To make certain project scope changes arecontrolled effectively, there are processes and tools and techniquesthat can be utilized such as data analysis, work performanceinformation, change requests, project management plan updates andproject document updates.

Change Requests Process

According to PMI (2017), the change control is the process ofreviewing all change requests; approving changes and managing changes todeliverables and to communicate the decisions. Projects that have anextremely tight schedule and can easily go over budget is when thechange control process is even more relevant and should be used.However, if a change is made then a formal change request process shouldbe utilized to ensure the full understanding of the impact of thechange is understood by all parties. Once approved, updated costs,schedule and baseline should be established and communicated.

Project Change Management Process Steps (Billows ,2019):

Step 1: As the project manager, you receive a changeorder request. The first step is always to see if the situation can beresolved with corrective action that would not change the project planor any of its components.

Step 2: If corrective action fails or is not anoption, you analyze the change order request. You document each of theitems listed above and make your recommendation for approval orrejection of the request. You should complete the analysis in a timelymanner and include quantification of the impact of the change on theproject scope, budget, duration, etc. as detailed above.

Step 3: You forward your analysis of the change orderrequest to the project sponsor with your recommendation for approval orrejection of the request.

Step 4: The sponsor decides whether to approve or reject the change order request and the consequences. You document the result.

Step 5: If the sponsor approves the change request,you implement it by changing the project budget, schedule and scope asnecessary. Then you alter the team member assignments to reflect thechanges. You follow these same steps for all change order requests.

Step 6: You should archive the change order requestand all supporting documentation. This information is invaluable forhandling future requests.

Change Request Example:

If I were a project manager and had to update the project baselinemultiple times then I would follow the project change managementprocess. Following this process means that changes that do occur to thebaseline project plan are thoroughly explored and are needed to producethe agreed project constraint and deliverables. According to Billows(2019), you should never allow stakeholders to make changes to teammembers’ assignments, the specifications of deliverables, or to add newdeliverables or tasks without going through the change managementprocess. By following this requirement is also preventing scope creep.A project manager’s job is to not prevent changes to the project.However, as an alternative the project managers try their best to comeup with more reasonable ways of performance that leads to improvement ona project. In addition, adding extra requests on a project can raisethe project’s time and budget constraint, which means the projectmanager will either need to prolong the deadline and assign extrapersonnel to work on the project. In the long run, keeping an eye onscope changes allows you to communicate any changes more quickly andmake any necessary corrections in advance so that your project does notget off course.

-Venus

References:

Billows, D. (2019). Project Change Management. Retrieved from: https://4pm.com/2019/08/02/change-requests-4pm-com…

Project Management Institute (PMI). (2017). A guide to the project management body of knowledge (PMBOK® Guide) (6th ed.). Newton Square, PA: PMI Publications.

POST2:

Scopecontrol and the function of it is one of the key factors to a project,and can be the difference between success of the project and the failureof a project. The lack of scope control is one of the most common andmain causes to the failure of a project. Chuck Millhollan (2008) statesthat “the four top causes for project failure are: Poor or incompleterequirements, Scope creep, A lack of a structured project managementmethodology, and the Lack of change control.” So what is Scope Control?The PMBOK (2017) guide defines scope control as “the process ofmonitoring the status of the project and product scope and managingchanges to the scope baseline. The key benefit of this process is thatit allows the scope baseline to be maintained throughout the project.”Some change throughout a project is inevitable, and some changes aregoing to have to happen regardless of how solid the scope is. Being ableto control the change and potential scope creep, however, is theimportant task, and can potentially decide the overall success of theproject.

There are tools to aid project managers with taking on change, andbeing able to make the best of it, and come out ahead of any morethroughout the projects life cycle. Martinelli and Milosevich (2016)identified four tools and techniques that assist project managers andthe task of scope control and they are project scope control system,project change request, project change log, and project scope controldecision checklist. The Project Scope Control Decision Checklist is onearguably one of the more important techniques as it discusses and givesvisual representation by listing out if the project and the change beingrequested is worth considering. Along with that, it covers multipleareas of the project as it identifies the responsibility for the change,the impact of change on the project schedule or budget, and the neededresources or approvals necessary to implement the change (Martinelli,2016).

I have used a project scope control decision checklist, but in a moresimple manner, while planning construction projects in the Army. Theway that it is handled is a less formal manner, but is consistent withthe checklist that is shown in the PMBOK. As more of a risk assessment,it covers the questions of potential strengthening of a project, thepros and the cons of the change, the timeliness if implemented,alternatives, and overall risks to personnel, equipment and job siteinfrastructure.

Martinelli, R. J., & Milosevich, D. Z. (2016). Project managementtoolbox: Tools and techniques for the practicing project manager (2nded.). Hoboken, NJ: John Wiley and Sons.

Millhollan, C. (2008). Scope change control: control your projects or your projects will control you! Paper presented at PMI® Global Congress 2008—North America, Denver, CO. Newtown Square, PA: Project Management Institute.

Project Management Institute (PMI). (2016). Construction extension tothe PMBOK® Guide. Newtown Square, PA: Project Management Institute.