Daniel KruegerAgile Coach & Scrum Master| General Dynamics Mission SystemsMinneapolis, MN, United States
I'm reading this book, "Identifying and Managing Project Risk", by Tom Kendrick. This book is a few years old, but I'm wondering if this is still true. If it is, how do you have this conversation with a client that won't accept this? Saving Changes...
I believe it is still relevant. As a project manager our Job is to highlight the Risk. If Client being the most important stakeholder not ready to accept it then raise it with the Project sponsor. If Project sponsor also does not accept it then they cannot hold you responsible for Project failure/delay because of it. You can keep it out of scope of the Project and have client agree on it. They cannot do both at the same time.
Hope it helps. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
The first thing I do in this case is saying to my client: what does mean good, fast, cheap for you? All are subjective matters. Saving Changes...
I try to use storytelling or the power of analogy to map situations which a difficult stakeholder is comfortable with to the project context. For this, it does require developing some understanding of the stakeholder - what do they do for fun for example.
Kiron Saving Changes...
Al TaylorI.T. Contractor| IndependentWaterloo, Ontario, Canada
hey Daniel.....not sure I understand the question. There is a 'generation-old' mantra that suggests that u can get two out of three but not all three. .....Are u asking how u have that conversation with the client?
If that is in fact the question I am wondering if Agile has rendered that discussion moot...what do others think?....Al
...
1 reply by Sergio Luis Conte
Oct 29, 2018 10:41 AM
Sergio Luis Conte
...
I am helping organizations in Agile implementation from 1995 up to date (by the way Agile is not about software or IT and did not start with the Manifesto). Each time a organization hired me I spend time explaining that Agile is not deliver faster, Agile is not cut costs, Agile is not change everyghing when we want without impacts, etc, etc. If I do not do that, I am DOA (dead on arrive) due to the misunderstanding outside there.
Yes, in other words: quality/scope, schedule, budget. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Oct 27, 2018 9:14 PM
Replying to Al Taylor
...
hey Daniel.....not sure I understand the question. There is a 'generation-old' mantra that suggests that u can get two out of three but not all three. .....Are u asking how u have that conversation with the client?
If that is in fact the question I am wondering if Agile has rendered that discussion moot...what do others think?....Al
I am helping organizations in Agile implementation from 1995 up to date (by the way Agile is not about software or IT and did not start with the Manifesto). Each time a organization hired me I spend time explaining that Agile is not deliver faster, Agile is not cut costs, Agile is not change everyghing when we want without impacts, etc, etc. If I do not do that, I am DOA (dead on arrive) due to the misunderstanding outside there. Saving Changes...
You can absolutely have all 3! It's usually a sign that you didn't have an aggressive plan with no risk however. It's when you start pushing the boundaries and take on risk, that you find that cost, schedule, scope, and quality start to compete against each other. For projects that don't involve any risk, the question becomes what value is the PM providing to the project other than just making charts? Saving Changes...
