ARUN MahendranETCL Engineer 1| CameronCoimbatore, Tamilnadu, India
Hi Everyone,
In our organisation we are Implementing Project online.
Following are the present scenario.
Changes happen so often.
No well defined project management methodologies
Stakeholder support is less
I.T or Programmers were not experts (As our concern is mechanical based and I.T team will do only system admin work)
Problems we faced with project online.
How to create project document templates and route it for approval.
creating work flows.
What are all the phases to be considered for Implementation
Key Milestones to look
P.s We dont have any defined project management methodologies before and there is no system to track people's and Individual task and project performance.
Thanks a lot in advance. Saving Changes...
Sort By:
Jamal SearlesProject Manager| Sun River Service CompanyWilson, Nc, United States
I am hoping that someone 'in the know' will answer this question soon. I am currently testing a 30 day trial of Project to measure it's usefulness for myself and stakeholders. Saving Changes...
1. Define your objectives first - why do you want to use this tool (or any PM tool for that matter). What do you want to achieve?
2. I see that you don't have a defined PM methodology. But you do need to lay out a process to achieve the objectives you outlined above. Perhaps you want to use project management to increase project execution success... so lay out the steps/process to achieve this in your organization
3. Then implement this tool to fit your process. (I think this is where Eduard's list can fit in) Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
In the scenario you stated forget about to implement a tool. Instead of a tool you are buiying a headache. I can say that because I was on both side of the desk (as a client and as a provider) and I have been involved in implementing the tool you named in my current place of work. Forget about to methodologies. Take a point of reference. If you want a method or process go to PRINCE2. If you want to take a list of best practices that you have to take into account to be more effective go to PMI´s PMBOK (or others). In your case, I would take the second way. From PMBOK identify those knowledge areas where you have more "pain" today and start to use the "thing" or "artifact" more simple that you can use. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Sorry to continue, but about your questions:
-Changes happen so often.
This is impossible to avoid. See Lehman´s Laws or Change (which comes from software but are applicable to any type of product.
-No well defined project management methodologies
See my above comment.
-Stakeholder support is less
No gain, no pain. You have to demostrate to your stakeholders that they will be more rich with the work you are doing than without it. And rich is not about money only. Perform Project Stakeholder Management and take a look at things like "Solution Selling" selling method.
-I.T or Programmers were not experts (As our concern is mechanical based and I.T team will do only system admin work)
I´m sorry, but it is the world. You, as project manager, have to transform into a coach in this type of situations. Saving Changes...
Community Champion
