| Topic : Managing Stakeholder conflicts for IT projects |
|
|
Project Management ++
|
|
Activity:
531 views;
last activity : 07 06 2010 20:18:09 +0000
|
|
|
|
1
Create effective team, establish effective communications and be a leader
2
Communication,Scope mgmt & Risk & issue management
3
Planning control cycles
4
Do not get involved into technical issues
5
Various Aspects for Successful Project Management
6
9 points for Successful implementations
7
he should not under-estimate testing
8
Follow PMI/ ITIL / P3M3 Guidelines by the word
9
Multi step process
10
Be on top and anticipate
11
Proactive management of bottlenecks and surprises
12
Depends
13
#
Understand Business Strategy
14
P.R.E.D.I.C.T- I.T
15
He must be empowered by GM to say NO (sometimes)
16
People Process Technology
17
9 points for Successful implementations
18
Healty project initiation, stringent monitoring and control
19
Communication,Scope mgmt & Risk & issue management
20
Impelement Large IT project worh 100MN USD at Saudi Arabia Airlines
21
By hiring a Business Analyst
22
Ensure proper reporting
23
Proactive management of bottlenecks and surprises
24
Flexibilty, Team Work, Communication, Timeliness and clear understanding of the Ultimate Goal
|
||||||||||||||||||||||
|
|
All of the above ideas are right, but if you failed to create the effective team of people who ready to work, think and collaborate in the process of solving the problems, and let them work together by leading them and providing the moderated level of free thinking (I mean watching the process goes in the right direction to the established goal), you will never reach what you want to reach. Finally, the strategy and ideas are good, but they will not be realized until there are people around you who will be ready to work on this strategy and solve problems. No one wins alone. |
5
|
I also support these guys.With a good team and by effectively planning each phases of the Project the project could be completed in a more effetive manner.Various types of testings like System,Unit Testing must also be performed.
Mr.Oleg i completely agree with you. A focussed and hard working team is an essential to successfully implement any project.There should be proper and effective communication between all of the team members and all of them should be clear of what they need to do.Moreover there can be ultimate strategies that you may have developed but if you don't have the capable work-force to implement it then its of no use. So an effective team is necessary for the implementation of the project.
|
|
To sumup the ideas put forth, we need to concentrate on communication(Internal stakeholder & consistent communication with External stakeholder), proper governance on Change mgmt and early forecast & resolution of risk and control on Issues. |
3
|
|
|
Well he should be able to plan control cycles to check budget and time frame which was agreed.Keep it control cycle simple but ensure all changes are captured and reported to management. From beginning to end he have to document the control cycle with the management and customer |
3
|
Well I agree with Mithilesh that Planning control cycles is very important for IT project manager & project also.
It is best to think of planning control as a cycle, not a straight-through process.
Once you have devised a plan you should evaluate whether it is likely to succeed. This evaluation may be cost or number based, or may use other analytical tools. This analysis may show that your plan may cause unwanted consequences, may cost too much, or may simply not work.
In this case you should cycle back to an earlier stage. Alternatively you may have to abandon the plan altogether - the outcome of the planning process may be that it is best to do nothing!
I agree with Mithlesh - Control cycles are important.
- First thing first, Project Manager and team should work towards delivering what is documented in the WBS, only the scope of work, nothing extra.
- Follow the processes that you have decided (standard or tailor-cut) for your project.
- Project Manager should document all the approved (through CCB) change requests and modify the scope baselines accordingly.
- Conduct phase end reviews for time, budget, and scope. Use EVM to monitor time and budget.
- Always present correct status of the project to the Management and Customer, this will help them take decisions in case of any deviations.
|
|
IT PM tend to get too much involved into technical details and solution finding on very detailled level....That is not his job. In most cases a PM who gets involved too much in to technical details, he loses overview on the other important parts of the project (timeframe, resources, training, testing.....) |
2
|
Mr.Robert i agree with you that a project manager cannot isolate himself from the technical issues related to the project.He has to get involved in almost every single thing although there may be other persons too who are responsible for it but still as a leader of the project he should not get away with even a single thing.
It's a fine line we must walk...being too involved in the technical aspects is time consuming and somewhat unnecessary. But at some level we need to be aware enough to ensure the SME's are giving us accurate information and accurate estimates.
|
|
-Clarity on Requirements/objectives to achieve of the project and performing team is in sync with what needs be achieved to meet business needs of the project. -By building highly productive and cohesive teams. Keep them focused and motivated - Proactive monitoring and control over various metrics(time,cost,quality,scope) of the project on a regular basis. - Timely corrective measures to pull the project back on track. - Creating adequate communication channels amongst various stakeholder to keep the momentum going to achieve project goals.
|
1
|
|
|
Hi All Most of us have covered all the points very well. Based on my experience of over a decade in project management, I follow a simple framework. Apart from Team management, client management and stakeholder expectations, following are few basics needs to be in place. And we need to define the right metrics and events for alert and notification, so we are going on a correct track. Planning and execution needs to go hand in hand for a good project manager. He must be in proactive mode and not reactive mode. Step #1: Conduct Feasibility Analysis Step #2: Analyze and Determine Requirements Step #3: Consider Industry Best Practices Step #4: Design Step #5: Measuring and Tracking Progress Step #6: Development Step #7: Addressing Automation Step #8: Testing Step #9: Gradual Implementation Practices Regards Mihir Kumar Jhaveri, PMP, CSCM Senior Manager
|
1
|
|
|
IT Project Manager should not under estimate testing,let it be unit, system,
integration, performance, user acceptance or any other testing.
Test each and every unit for the defects and correct it. |
1
|
|
|
These are processes defined and refined over a long period of time by respected and experienced professionals. There is no need to re-invent the wheel. Once we start living these processes in our daily life, we should be able to deliver each and every project successfully. |
1
|
|
|
Implementing project successfull is a multi step process (from Analysing to delivery and supporting in prod). The key lies to make sure that all the steps are well documented and followed. Creating a project plan, identifying the right resources, time frame for each phase of project and monitering the project paln at every stage and step. Time to time, make sure that you visit your risk associated with each stage of the project. Communication should be on top of every thing. Over communication is always better than under communication. There is no end of this. In nut shell the things you should keep in mind is that the project overall depends on following Communication Scope analysis (Make sure to get it documented and sign off from busniess) Right resource (Major challenge) Monitor the progress at each phase/stage/step test plan and perform testing (Give enough time for testing) Risk analysis Back up (plan and resource)
|
1
|
|
|
A IT project is ultimately considered successful if it is delivered & performs at least to the clients expectations if not more. - Excellent Planning for optimal time & resources utilization. - Enough risk management even from consultation/study phase to reduce the post release changes and reduces time to market. - for Best quality - meticulous testing. The Key would be AVOID SURPRISES. I personally prefer to spend more time in UAT, that’s when users get to see the whole concept in action and most of the time come up with valuable enhancements/changes that are beneficial to the acceptance / success of the project. May not be the greatest but just thoughts going loud. End of the day every one should get what they want.. Project manager.. job well done..!!! |
1
|
|
|
Nice plan, brilliant dedicated team, enthusiastic disciplined client are all part of good recipe for successful project. Still it will throw up surprises and bottleneck on deliverables will appear from no where. That’s the magic and reality. So like a matured sailor, project manager need to steer this ship by taking adequate steps of risk management proactively to address surprises and overcome bottlenecks and thereby manage to reach the final mark successfully. |
1
|
|
|
See, if you want to go for any project, one must behave like a down to earth person by mind...........only. go, get and Learning. Lean to wish a problem two solutions always. wishes, Rajay Tyagi
|
1
|
|
|
Because of need for agility of organization, PM now does not have the luxury of being in seclusion and work on a project for few months at a given time. The IT PM needs to understand the customer’s business strategy and challenge any project scope that is not in alignment with that strategy. IT PM should be in tune with changing marketing/business strategy to make sure that the project is still relevant to the customers. The project management processes need to be agile to enable fast changing customer priorities. The PM needs the influencing and negotiation skills for forced prioritization to solve the major business problems in a short development cycle. |
0
|
|
|
In most cases an IT PM is seen from GM as top down executor, but he has no equal power to decide in case a political discussion is not ending. |
0
|
|
|
We can implement the any IT project succesfully when we consider People,Process and Technology. When it people it a Project team, Functional team,Mgmt team, customers , Process is that Coomunicaitons,Risk Mangemnt, Tracking the timelines and activities, testing . to implement project succesfull we need to depend on technology that has to be availble to the team always......... by using this fundamentals you can successfully go thorugh all the phases of the project ......IPECC |
0
|
|
|
Hi All Most of us have covered all the points very well. Based on my experience of over a decade in project management, I follow a simple framework. Apart from Team management, client management and stakeholder expectations, following are few basics needs to be in place. And we need to define the right metrics and events for alert and notification, so we are going on a correct track. Planning and execution needs to go hand in hand for a good project manager. He must be in proactive mode and not reactive mode. Step #1: Conduct Feasibility Analysis Step #2: Analyze and Determine Requirements Step #3: Consider Industry Best Practices Step #4: Design Step #5: Measuring and Tracking Progress Step #6: Development Step #7: Addressing Automation Step #8: Testing Step #9: Gradual Implementation Practices Regards Mihir Kumar Jhaveri, PMP, CSCM Senior Manager
|
0
|
|
|
1. Usually IT projects are underesimated right from the proposal stage :-) 2. This we can beat by ensuring a good work breakdown from requirements followed by a realistic effort estimation and then a realistic schedule 3. Once the project begins, it very important to have a very stringent monitoring and control methodology 4. Weekly project status meetings should be both internal (among the project team members) and external (with team and customer also). Reports need to be generated and distributed, schedule has to be updated to reflect current status. Never skip a status meeting, entire team should speak, share, healthy conflicts need to happen and need to be resolved by the PM. Probably healthy monitoringand control methods are most important as this actually is the execution phase and most work is happening here. This ensures a PM is aware of and in control of the actual ground situation 5. Having a tab on the team morale is another important factor, regular team meeting sensitize the PM.
|
0
|
|
|
<p>To sumup the ideas put forth, we need to concentrate on communication(Internal stakeholder & consistent communication with External stakeholder), proper governance on Change mgmt and early forecast & resolution of risk and control on Issues.</p> |
0
|
|
|
The key to have sucess for any large IT Project are the following The Project Planing : Make sure that project activites are captured in the project plan to the last granular level. Interdenpendecy Management :Interdepencies have to be managed effectively Change Management : Most of the IT project suceed or fail because of this. Controlled changed management always helps Roles and Responsibilities : Teams working in the project should aware of clear roles and responsibilities. RCSI can used as the tool to define R&Rs Issues and Risks Management : Issues and Risks if managed properly and conveyed to top managed on time helps in the success of the project |
0
|
|
|
Project Manager should hire a good business analyst. Business Analyst should be able to have an access to the actual end user of the intended system so that he is able to capture important requirement, details.
|
0
|
|
|
He/she should make sure that all the stake holders, staff reports what is happening to you(project manager)in the timely fashion so that you won't be surprise if you hear a good or bad news.
|
0
|
|
|
Nice plan, brilliant dedicated team, enthusiastic disciplined client are all part of good recipe for successful project. Still it will throw up surprises and bottleneck on deliverables will appear from no where. That’s the magic and reality. So like a matured sailor, project manager need to steer this ship by taking adequate steps of risk management proactively to address surprises and overcome bottlenecks and thereby manage to reach the final mark successfully. |
0
|
Flexibilty, Team Work, Communication, Timeliness and clear understanding of the Ultimate Goal
|
|
Its all about delivering a Tangible End product as required in proper time (avoiding freebies) with a team that communicates properly among itself and external stakeholders |
0
|
|
|
|
|
|
|
The change management process is key to the successful outcome of a project. The process ensures that each change introduced is properly defined, considered and approved before implementation. But sometimes the change doesn't take place and resistance... |
Well I don't believe that people could predict future, and now a days there are television programs which makes us believe in what they have predicted for the future or believe to happen in the near future. |
nice data man.. |

