Project Management

Please login or join to subscribe to this thread

Starting in the middle

linkedin twitter facebook   Information Technology   Organizational Project Management   Work Breakdown Structures (WBS)  
avatar
Lara Doll Project Manager, CAPM Fort Worth, Tx, United States
Hi everyone,

I am a new PM, coming from a marketing manager position. The COO assigned me as project manager for a project that's already in full swing. In fact, we are already to the point of procuring a vendor for software.

My problem is that I am starting in the middle of this and having to play with a cart that's way ahead of the horse, so to speak. For example, while we have selected a vendor and are working on the contract with them, the sponsor (the COO) has requested a budget for the project.

What is the best way to organize the project at this point? How can I get some order to this big mess? Any advice would greatly be appreciated!
Sort By:
< 1 2 >
avatar
Elaine DiMasi Project Manager specializing in High Tech Instrumentation| Lawrence Berkeley National Laboratory Oakland, Ca, United States
In this situation I'd almost be afraid of spending much time up front adding *too much* formality, since you may have been assigned to do a fast rescue rather than to "correct" the former handlers. Once you "find out what everybody knows," maybe formalize *that* into a consensus document. Once the people who handed their mess to you agree that you've got a fair representation of the situation, then show that the knowledge and process gaps can be address with the additional PM-lore aspects of charter, risk register, and so on. Above all, mapping the territory around the critical path! Good luck!
avatar
Deepesh Rammoorthy ICT Project Manager ( PMP®AgilePM®Certified ScrumMaster® (CSM®))| Australian Red Cross Blood Service Tarneit, Vic, Australia
Some tips :-

Understand on a high level what that software product does .If your department is the primary user then it's best to get the product training from the vendor.

Understand what business problem the software product is solving, who is going to be affected by the implementation of this product and who will be the end users. What are the current pain points of your users and how is the new product going to alleviate the pain points? This will be your business case and stakeholder register.

Have a workshop with the key end users and the vendors to demonstrate the product and get their buy-in for the key features of the product. Get the users to agree on what functionality they will use and this will be your User Requirements/Functional statement and Product Scope Statement.

Follow the Minimum Viable Product approach and lock-down the User requirements to what the tool can offer .

It is too late to collect User Requirements and Configure or customize the product accordingly since you are already signing a contract with the vendor and that ship has sailed.

Contact a legal representative like a Corporate Lawyer and ask them to go over the vendor contract so that your company does not get caught out in ambiguous clauses.

Since you are procuring the software, make sure there is going to be a clear support Plan for future support - Is there required to be an internal administrator?super user? Trainer? or are you solely relying on the vendor to provide the support. Have clear direction on how Service levels will be defined for the Software

Make sure you have a clear implementation plan to get this software on-board. The plan should include 1) People 2) Processes 3) System
Is it going to disrupt existing business processes? if yes, can it be planned for after hours? Do you have a migration plan in place in case you need to key in old data into the system?

Discuss and document your training plan with vendors and end users.

If there isn't a User Requirements Specification for the software, try to get an As-Built or As-Configured documentation from the vendor to understand how you are going to use the software.
avatar
Warren Nash PM/PMO Position & SAP Architect| Freelance Pudong, Shanghai, China, Mainland
Talk to the team and stakeholders, get a feeling for the project. Also get these people comfortable with who you are, and this will help them quickly to develop trust in you.

Focus back on what has been done and what is still open or has not been done correctly. From this you will have your own "todo list". From there it's about "putting the puzzle pieces in the right place".
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

"It takes a lot of courage to show your dreams to someone else."

- Erma Bombeck

ADVERTISEMENT

Sponsors