For me, one of the best lessons learned was earlier in my project management career. When analyzing stakeholder requirements for an infrastructure rollout, we left out one of the obscure vendors who had been contracted to maintain a small but crucial desktop app. Rolling out the desktops and app meant that we had violated their T&C so the app could not be supported anymore, even though the app still worked, and we had to buy and install all new apps. Something that could have been avoided if we had communicated with this tiny obscure vendor. Lesson: identify and communicate with ALL stakeholders. Saving Changes...
Meade RubensteinPM III| IT Project GuideSparta, Nj, United States
via Colin Powell - "Don't be afraid to challenge the pros, even in their own backyard."
Everyone on the project team is open to being questioned and if the response is to complicated to understand, that means that they don't truly understand it.
Don't believe the Sponsor when they say, "That's the budget and not a 'farthing' (or your lowest denomination coin) more!"
The Sponsor will add money and or time to a project when the PM convinces the Sponsor that the increase is in the Sponsor's best interest and that the PM has little to gain from the change. Jim
Jim, there is usually a battle of sorts between the "no more money" and the "I need more money" events. And you're right, the PM needs to be able to justify their stance. Saving Changes...
via Colin Powell - "Don't be afraid to challenge the pros, even in their own backyard."
Everyone on the project team is open to being questioned and if the response is to complicated to understand, that means that they don't truly understand it.
Nice one Meade. Saving Changes...
Anish AbrahamPrivacy Program Manager| University of WashingtonAuburn, Wa, United States
I had a tendency to avoid/ignore conflicts, but I learned that "Do not ignore conflict". We should see it as an opportunity to improve the product management practice and leadership skills.
...
1 reply by Sante Delle-Vergini, PhD
Mar 15, 2018 7:18 PM
Sante Delle-Vergini, PhD
...
Anish it's a common reaction actually. But embracing conflict (not crazy conflict) can be a good thing because it's a direct way to solve the problem, as long as everyone is a willing party.
I had a tendency to avoid/ignore conflicts, but I learned that "Do not ignore conflict". We should see it as an opportunity to improve the product management practice and leadership skills.
Anish it's a common reaction actually. But embracing conflict (not crazy conflict) can be a good thing because it's a direct way to solve the problem, as long as everyone is a willing party. Saving Changes...
1. Identify early signs of conflict or disengagement of team
2. Keep all important communication and risks in email
Good one Sonali. Saving Changes...
Dileep SankarProject Engineer| Mechon Trading and ContractingDoha, Qatar
In one of my recent projects, the following causes converted an opportunity into a threat. I've added them into my lessons learned register.
1. Improper scope identification and clarifying it.
2. Not communicating the expected schedule with the executing team, thereby providing immensely incorrect estimates for both resources as well as duration.
3. Also, discussing the lessons learned with the virtual teams and receiving their feed-backs. Saving Changes...
