DQ1

A Project Scope is the end result of one’s project and is basically the product that is to be delivered to one’s customers. The purpose of the Project Scope is to be as clear as possible in regards to what the client is receiving. When project scopes are clearly defined, it aids in the success of a project. Items on the project scope checklist include the project objectives, deliverables, milestones, technical requirements, limits and exclusions, and reviews with the customer. Challenges can occur when assessing the scope of the project include having false expectations in regards to setting limits and exclusions which can lead to wasting resources and time on false issues. Having false expectations can also lead to incorrect milestone schedules, which may result in mis-information to the both employees and customers.

Scope creep is the idea that project scopes may expand over time, which would occur by changing requirements, specifications, and priorities (Larson & Gray, 2018). To ensure that it does not occur on a project, one should be sure that the writing scope statement is clearly written. If changes in the project scope need to be made, then there should be a sound control change process to take note of all the changes that are to occur. The change control process includes keeping a log that notes the change, the effect of such a change, and those responsible for implementing or rejecting the anticipated change (Larson & Gray, 2018).

I will share a personal example that took place in my small business. I run a small business with a great friend of mine creating food art lunches for busy moms, and one issue we had was with planning and having specific guidelines as to when our orders would be completed. Our small business has very well-established roles, where my co-partner person takes orders and I am responsible for delivering our meals. However, we needed to establish our timeline and milestones. Without this establishment, we were not as efficient as we could have been. Furhtermore, we did not consult with the customer on their satisfaction with the product; however, we have now added a rating scale to know if our customers are truly happy.

Reference:

Larson, E. & Gray, C. (2018). Project Management the Managerial Process (7th Edition). New York, NY: McGraw Hill Education.

DQ2

From the way I understand it, the WBS or work breakdown structure of a project allows for people to be able to efficiently and effectively line out the details of a project. The WBS allows for tracking and keeping scheduling details, and timelines in order, which would make it more accessible for analyzing the progress of the project. If i understand it correctly, it appears that this is a giant, more organized "to do list". I don't know if anyone else is like I am, but I always make myself a check list, it keeps me organized and gives me a sense of accomplishment as I mark things off of the list?

some of the major organizational that should and can be evaluated would be that it breaks down levels of work, generates the performance levels as the steps are completed, There are clear start and end dates, and time frames that need to be met, goals are easily evaluated based on time this way. There is financial steps or budgets that are incorporated, keeping the project within the means. These are all sensitive topics when trying to execute a timeline, budget and specific project goal. For example if an organization was given $1500 and 3 weeks to complete a project for a specific client, the WBS would help organize the team in jobs and tasks assigned to each person, the WBS will allow for it to be categorized and organized in steps of priority from start to finish.