Project Management

Please login or join to subscribe to this thread

I just got handed a short timeframe, highspeed, timeboxed project

linkedin twitter facebook   Governance   Work Breakdown Structures (WBS)  
avatar
Anonymous
Guys


I am looking for some advice here. I have just been handed a project which must be delivered in 12 weeks. There are some large assumptions made, scope is not set and a few issues and risks have been logged.


The good thing is it is the start of the project so I am not picking up someone else's mess. However, I don't want to have this one turn into a mess as it is very high profile


My thoughts are this


~Identify the stakeholders ASAP.


~Lock the scope and requirements in within the next 2 weeks.


~Keep the communications frequent with all stakeholders.


~Ensure the roles and responsibilities are clearly defined in the project plan document and get this signed off ASAP.


~Get a WBS done towards the end of the 2nd week.


~I already have executive buy in so I will ensure they are across the comms.


~I already have an existing governance structure in place so will just need to ensure this project fits inside that model


~I am in a matrix env so I need to get buyin from the resources that this project will be on the top of their list



I am not sure that an extreme methodology will work here and PMBOK is my preference.


Any suggestions on other methodlogies to explore or areas to watch out for when going through a high speed project like this would be appreciated.

Thanks

Sort By:
avatar
Robert Bradshaw PMP Mississauga, Ontario, Canada
Communication inside and outside the team becomes critical in "zip launches" like this. With short timelines a change from outside the team (e.g. managment)can really hurt the project. A communication strategy to prevent this type of change is needed. Communication that focuses on what is done, and, what is NEXT, prevents changes of direction.
On the same line of thought change control and speed of change becomes a fine balance. Quick changes may be needed, but only to hit the launch date.
So two suggestions, first a strategic communication plan and second a quicker change control system focused on scope and launch date.
Good luck!
avatar
Andy Jordan President| Roffensian Consulting S.A. Cherry Grove, AB, Canada
If time is of the essence the I would suggest that the best methodology is the one that the project team is most familiar / comfortable with - less education / uncertainty, etc. I would also make sure that your stakeholders agree to an overall RACI / RASCI chart that will quickly identify roles and responsibilities up front. Andy Jordan, President, Roffensian Consutling Inc., www.roffensian.com

Please login or join to reply

Content ID:
ADVERTISEMENTS

Whenever you are asked if you can do a job, tell 'em, "Certainly, I can!" Then get busy and find out how to do it.

- Theodore Roosevelt

ADVERTISEMENT

Sponsors







Vendor Events

See all Vendor Events

Newsletters

Jun 3: The Career Problem Facing New PMs
May 20: Your PM Career as a Project Life Cycle
May 13: The Big Lie After Layoffs

See all newsletters