What do you think about this? personal opinion

Project Scope Statement Continuing with Project Utilization, the scope is built around the objectives/end goals of the project. My scope statement details the why behind the project as well as steps to navigate the project to a successful completion. I included three major categories in my scope statement: Deliverables Acceptance Criteria Project Exclusions Each category contains actionable subcategories/tasks to satisfy each major category. The goal of each task is to progress the project one step toward fulfilling the purpose of the pilot project; to re-engage customers and assist with finding value in the Assist Package. I made sure to create my scope statement similar to an action plan so each subcategory/task is a clear assignment for the team to complete; removing all vagueness or obscurities. Work Breakdown Structure | WBS I used LucidCharts to design a map of the deliverables necessary to complete the project as outlined in the scope statement. I used colors to display different levels in the workflows. The chart displays the subcategories under the deliverables category from the scope statement. From there, I was able to divide the deliverables into smaller, more manageable work packages. WBS Dictionary I included my WBS Dictionary in my Scope Management Plan. The WBS Dictionary is a document that provides detailed deliverables, activity, and scheduling information [for] each component in the WBS (PMBOK, 2017, p.162). For each of the tasks outlined in the WBS I listed the associated Level, WBS ID, Name, Description, Deliverables, Resources and Hours/Budget. Scope Management Plan The overall Scope Management Plan details how the project will be defined, validated and controlled (PMBOK, 2017). I used a template from online. The template covered all the necessary requirements listed in the PMBOK to satisfy a complete Scope Management Plan (2017, p. 134-171).

Scope Description

Lollis Backyard will undergo a pilot project to help Company T657 determine the future state of their Assist Package and develop methods for opportunities to increase monthly utilization.

The project is a result of a company initiative that has not proven to be 100% successful. Early 2021, my company created a new service offering that gave customers an option for an add-on package to a newly formed team to help optimize their current software instance. The initial goal is that customers would purchase the package for an allotted amount of hours each month to work towards enhancing workflows and software capabilities. The service offering, Assist package, is well into its first year and unfortunately is not seeing the expected feedback and utilization from customers.

This project is to determine how to re-engage customers to assess how to provide value to customers purchasing this package.

Lollis Backyard will pilot the Premier Assist package containing 36 available hours per month.

Deliverables

Weekly Meetings

With the initial rollout of the Assist Package, consultants allowed their customers to set the frequency of meetings and the tone for how they wanted to utilize and engage with the consultant assigned to the project. Adjusting this pilot project, the project manager will set the frequency of meetings to weekly for thirty minutes with Lollis Backyards project team and the assigned consultant.

The project manager will also establish a thirty minute weekly internal sync with T657s project team to gather updates and coordinate upcoming customer meetings.

Weekly Project Status Report

Project Manager will maintain a weekly project status report delivered to T657s executive project team [Project Sponsor + Team Director] to track the progression of the pilot project

Same status report will be delivered to Lollis Backyard for review

Backlog of Tasks

The project manager will help identify five backlog tasks to build the project pipeline. Each task must include notes of requirements and projected dates.

Proactive Recommendations

Formerly, consultants allowed customers to determine if and when projects would be discussed and initiated. Moving forward, the expectation is that T657 will proactively recommend items (3) to be accomplished within the instance to help with consistency of engagement.

Customer Value

Reviewing that Success Metrics have been achieved. Success Metrics will be included in the 60 day check-in to confirm Lolllis Backyard is seeing value in the project.

Increase efficiency with internal teams

Decrease ticket solution time

Increase automation

Increase CSAT scores

Training

Lollis Backyard agrees to complete necessary training to keep administrators and agents up-to-date with core product functionality. These may be delivered as on-demand videos or live webinars. All core (4) product training should be completed by project close.

Acceptance Criteria

Milestones

There are three milestones that should be reached during this project.

30 day look back period to confirm trajectory of utilization hours

60 day check-in on task completion (3)

EOY Renewal

Executive Team Review

T657s executive team will need to review the trajectory of the project over the last ninety days

Feedback Survey

Capture feedback from Lollis Backyard on the impact of the project.

Understand from T657 the benefits of the project compared to results

Documentation of Utilization Methods

The project manager should provide documentation of methods used to increase project utilization to be considered for future projects.

Project Exclusions

Pilot project does not include any on-site meetings from any T657 employee.