What Resonated Today
- Erica Johnson
- Nov 6, 2023
- 2 min read
Today's Module was on Initiating a Successful Project and here is what resonated with me:
Scope creep is when a project’s work starts to grow beyond what was originally agreed upon during the initiation phase. Scope creep can put stress on you, your team, and your organization, and it can put your project at risk. The effects of scope creep can hinder every aspect of the project, from the schedule to the budget to the resources, and ultimately, its overall success.
Realizing that there was a name for something that always happened to projects I was managing (even without realizing I was manging it) was incredibly impactful. Having a name that explained my frustration when stakeholders, supervisors, etc would come up with last-minute ideas but then wouldn't understand when previously set timelines couldn't be met was (as corny as it may sound) life-changing. I haven't always been in a position where I felt comfortable enough to speak up and offer counter suggestions in those situations but now I feel equipped the next time that happens.
When working on a project, the goal isn’t simply to launch it, but to land it.
It's simply not enough to hand off a project to a client once it is complete. Yes we need to complete the project according to the previously set scope and parameters but what about the follow up? How do we know the project was actually successful without follow up? What are the success criteria that determine if the project worked? Did we pass all of the criteria?
Determine the success of a project by the quality of the product, the ability to fulfill the needs of your customers, and the need to meet the expectations of your stakeholders
I have experience with being on a project team that hadn't determined the success criteria for a project at any given point. Just because we successfully accomplished the goal at large - did it help anybody? Improve any processes? Anything?
Comments