GameDev 2017 - Валерій Міненко "7 clients that you never should not work...

that you ever should not work with

Valerii MinenkoFounder & Owner at Twigames

7clients

Who am I?

10 years in IT7 years in game developmentFrom 2015 – founder of Twigames studio

Why I’m talk?

Many small projects – many different clientsIn different areasAnd different styles of gamesFrom many locationsСustomer-oriented approach, not stable (chaos-style) development process

Who are you?

FreelancerSmall studioClient!

Most frequent and most risky oneIf you don’t understand what he wants – very likely you will create something that he would not like and needBig risk to provide invalid estimates

1. He doesn’t know what he wants

Clarifying requirements is your jobCreate GDD (at least for 2 first milestones)Make client to pay for it (never happens)Pay for it yourself, then add money for it to the budget and hope that it will rideAdd additional risks to the budget for unclear features

1. He doesn’t know what he wants

Wants to spend money as less as it is possibleArgues about budgetWhen you try to add risks – he says that you should not worry, everything will be fine (it won’t be)Quality falls, project looks horrible, so neither you nor the client likes it. Client is not satisfied and thinks that it is you fail (and he is right)

2. He is greedy

2. He is greedy

Most detailed GDD and estimates everHe will understand better why you charge moneyHe would be able to cut some features if he does not have enough resources

3. He changes requirements every day

Review of GDD is always a stress (especially if you review the budget)Estimate suggests some sequence of developmentMore changes – more difficult to provide correct estimate

3. He changes requirements every day

Be ready for that (it is all about Agile)GDD always helpsDo small fixes for free (everybody likes gifts)If you have to review budget too often multiply your rate for changes

4. He is lazy (unresponsive) one

Breaks development processBreaks deadlinesDoes not give you a feedback so it cause a risk to create something wrong and useless

4. He is lazy (unresponsive) one

Regular meetingsMake him work with your teamGive him an access to the repositoryStop work and make him waitMove deadlines

5. He is too active

Distracts from the processTakes too much of your time

5. He is too active

Create a schedule for meetingDefine feedback processAdd some time between feedback and its implementation, give him time to thinkIgnore unscheduled messages

6. He is an asshole

You just hate to communicate to him

6. He is an asshole

Budget x2If does not help – budget x3

7. He is stupid

Wants impossible thingsWants to add shitty features

7. He is stupid

Stop and think – maybe “stupid” is about you?Always say sorry (works for your girlfriend, works for you client)ExplainExplainExplain one more timeJust do it!And take it easy

10 advices for you

1. Make requirements clear to everybody2. Note them somewhere3. Involve client into the process4. Have a schedule5. Talk to your client6. Give him updates as often as it is possible7. Make him gifts8. Be critical to yourself9. Say ‘sorry’10. Take it easy

10 advices for your client

1. You should work as well2. Be part of the process3. Listen to your developers4. But don’t trust them5. Play your game6. Ask if you don’t understand7. Show only half of available budget8. Change requirements if you need it9. Say ‘sorry’10. Don’t be greedy

Thank you!

Questions?

valerii@twigames.cohttps://www.facebook.com/valeriy.minenkohttps://www.linkedin.com/in/valerii-minenko