Scoping meeting

Name a challenge you have during scoping in more than 3 words (long words combined by dash, e.g. no-one-listens)

What is your preferred approach or style in scoping?

• a. I don't know

• b. I don’t have a fixed approach, depends on the client

• c. Put client’s satisfaction first, be political

• d. Compromise for both side’s sakes, not to please the clients only, be collaborative in equal partnership

• e. Provide leadership throughout the process, be directive

How should we time the scoping meeting?

• a. We can take as much time as possible to understand every client’s needs and the reason why they request our services

• b. The faster the better to save time and money for both sides

• c. Every consultant, every client should have the same amount of scoping time

• d. Try finishing in a relatively standard given time as collectively discussed or agreed, for example timebox to 1 hour

What questions should we not ask during a scope meeting?

• a. How do you want things to be different at the end?

• b. Which aspects are IP responsible for?

• c. Who causes these challenges?

•   d. What is the expected timeframe for the support?

• e. What could stop this task from being successful? How will this be mitigated?

Rearrange these practices into Do and Don’t ​ ​

Groups:

(a) Do

,

(b) Don't

• Overpromise, overdeliver 

• Solve the problem right away

• Discuss both the why &  what (high level technical side) 

• Confirm if we understand each other in written Scope of Work template 

• Open space for other options for solution, not only the first one came to our minds 

• Let IPs talk continuously for a long period of time without guiding questions

To prepare for scoping, references of Learns documents exclude?

• a. Learns’ Wiki

• b. Tailored Technical Support process

•   c. Personal email chains for a certain request

• d. Adaptive meetings’ minutes

•   e. Books (Flawless consulting)