Perhaps something you could have done a lot better? Maybe it was a knowledge area that you neglected? Maybe it was a stakeholder or team member that you just didn't like and so you treated them differently than others? Any regrets, confessions, wishes? Saving Changes...
I am currently in Scrum framework. So, we try to collate inputs and improve the process after every sprint.
I received a feedback from the team telling number code conflicts identified during a sprint when multiple different teams are working on same module. So, a process was established to identify these dependencies earlier.
Thanks Sonali, was that issue discussed and resolved during the sprint retrospective? Did it work? Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
I wish to run faster than my project stakeholders when things go wrong.....(hehehehe)
...
1 reply by Sante Delle-Vergini, PhD
Dec 08, 2017 5:19 PM
Sante Delle-Vergini, PhD
...
haha nice one Sergio, we should bring our Nike's to work just in case. I had one stakeholder that was a scary individual, 6"5, 250 pounds, a black belt at Judo, always had a mean look on his face, and rarely spoke, just stared at you. No one wanted to deal with this guy. Turns out he was a really nice guy, his hobby was gardening, and when I asked him why did he look annoyed or unhappy most of the time, he said "that's me being happy, you should see me when I'm annoyed!"
Improving communication technologies especially when we have virtual stakeholders engagement.
Hi Nian, yes most of my projects have involved remote team members and this can be an issue without the right technology and communication process. Are you able to elaborate on the process/solution you employed? Saving Changes...
One mistake I did was the lack of key stakeholder engagement. I was working on multiple projects but didn't let the key stakeholders know what else I was working on. It took a while to communicate this properly, but once they understood this we were able to meet the project expectations and deadlines. Well, the lessons learned is that I need to communicate at the right time to the right audience.
Anish I have been there many times also. It seems communication is something that can easily go wrong. Saving Changes...
I remember not preparing a stakeholder for a steering committee meeting. He was caught off guard and it hurt our relationship.
Stéphane that sounds sad, it must have been something fairly bad in their view to affect your relationship. It's still the same way until now? Saving Changes...
Once you complete the project and picture is completed and you know all details, one can think that he must do certain things differently. there is always room for improvement. but this is life, you are not known everything from start and here comes your ability to think ahead and work proactively to predict and do things rightly
True Mansoor, was there something you can recall in your past projects that you really wished you had not done, or done better? Saving Changes...
- improvement of stakeholder engagement
- earlier visualization of project results to check on stakeholder expectations and to mitigate risk.
- more agility.
Stakeholder is a key one Peter, and I don't just mean the high impact/influence ones. I have neglected some stakeholders that were low on that scale, but were highly impacted by the outcome of the project, such as end users or those that benefit from a project outcome. Saving Changes...
