What Questions to ask for knowing your Project Sponsor?

In addition to Matthew's and Rami's, I would ask to know about rather sponsor's role such as:

1. How do you intervene when the conflicts or problems occur beyond the realm of project level?
2. What nature of project reports and level of details do you want me to send you?
3. What are the hindrances currently you are dealing with for this project?
4. How to align the project goals with organizational strategic goals?
5. Who are negative stakeholders when the business case has been approved?
6. What are other jobs to be normally executed day to day than for this project?
7. How to deal with the issues when they should be communicated with senior management or requesting organization?

There might be more questions than the lists above.

Let us know when you finish.

Do you consider the project sponsor to be the client? I often have dual sponsors, one internal sponsor and one client sponsor.

The questions won't necessarily be the same to each sponsor.

Hello Markus,

You are correct, we should not expect a complete list of requirements or deliverables from the first meeting. Often, however, I am provided with some high level requirements and, additionally, one or more deliverables required by a contract with a customer. What I was attempting to convey is that if I receive any requirements or deliverables from the sponsor I review them as part of that initial meeting. Call it an initial review to identify anything that is infeasible - e.g., you want me to lead a project to produce a passenger aircraft capable of reaching mach 6 using turbofan engines; or you want me to lead a project to design an internal combustion engine made with metal that has a thermodynamic efficiency of 75%.

"What do you perceive the main functions and features to be?" - Yes, I like this question. I would still ask "What do you want it to do?" because that question is about overall functionality. With your question we start delving a bit into the details - which is good. I want to understand the overall desired capability, however, in case it becomes infeasible to deliver a product/service with all of the main functions and features within the time or budget constraints. Understanding the overall desired capability allows me to look for alternative solutions.

As an example, suppose your overall desired capability was for the project to design a passenger car capable of traveling 25 km per liter. If you give me a requirement to use a non-turbocharged diesel-powered engine it will be difficult for the project to succeed unless I can make changes to other things to reduce the weight of the vehicle, improve its aerodynamic efficiency, etc. Those changes, however, might require changing one or more of the main functions and/or features. If I don't understand the overall desired capability then the project is heading towards failure because all I know is I can't deliver the main functions or features within the constraints.

"What are the absolute minimum ("do or die") functions/features that are required?" - Call it a personal quirk, but I don't like asking what is the absolute minimum required. To me that question implies striving for mediocrity instead of excellence. I prefer asking "What functions/features must be included?" If something must be included it is part of the minimally acceptable baseline, but I've avoided asking what is the minimum.

"What are your thoughts on its physical appearance?" - Absolutely.

Also: "Is there anything you do not want the product/service to do?" Maybe the product/service is intended to complement one or more products/services the company already produces. If stakeholders tell me during the Collect Requirements process they want functionality provided by the other products/services, I know to exclude those requirements. Or maybe there is a legal limit to what the product/service can do.

Markus. Great initiative.
I hope your product will help the PM to set up the necessary business intimacy with his/her sponsor. Most of the questions I usually ask to my sponsor during my first meeting are covered by your article and by the comments from the community.
But I also address other key points for me regarding the other stakeholders: who are the main people to take care of, what are there potential concerns with the project, do they fully support this project or do they show some resistance, ...

It is definively important to me my sponsor gives all necessary information and awareness about the perception, mindset, level of acceptance and involvment from the other stakeholders. This before I ask theese other stakeholders for a first meeting.

Markus, excellent initiative, looking forward for the result.

One question I like to ask and that work for both internal and external sponsor is an open question.

What would make the project a success for you?

The answer could be surprising, and give your direction for further questions.

The external sponsor success could be too be able to make opening of a concert season in the new facilities or have a landmark building .

For the internal sponsor in a similar kind of answer could be to have a project that can be a flagship to open a new market.

Those answer will provide direction for more questions.
Regards,

In addition to Matthew's and Rami's, I would ask to know about rather sponsor's role such as:

1. How do you intervene when the conflicts or problems occur beyond the realm of project level?
2. What nature of project reports and level of details do you want me to send you?
3. What are the hindrances currently you are dealing with for this project?
4. How to align the project goals with organizational strategic goals?
5. Who are negative stakeholders when the business case has been approved?
6. What are other jobs to be normally executed day to day than for this project?
7. How to deal with the issues when they should be communicated with senior management or requesting organization?

There might be more questions than the lists above.

Let us know when you finish.

Hello Sungjoon,

thanks again for mentioning those questions, i have included them meanwhile in some way.

But i don't get behind this one:

"6. What are other jobs to be normally executed day to day than for this project? "

May be it is because i am not native English but could you please explain a bit more specific what this is about?
Thanks in advance!

Regards,

Markus

Markus. Great initiative.
I hope your product will help the PM to set up the necessary business intimacy with his/her sponsor. Most of the questions I usually ask to my sponsor during my first meeting are covered by your article and by the comments from the community.
But I also address other key points for me regarding the other stakeholders: who are the main people to take care of, what are there potential concerns with the project, do they fully support this project or do they show some resistance, ...

It is definively important to me my sponsor gives all necessary information and awareness about the perception, mindset, level of acceptance and involvment from the other stakeholders. This before I ask theese other stakeholders for a first meeting.