Cost cannot stay still while requirements will not
Diary of a Programmer Part 5
(part 1, part 2, part 3, part 4)
This is another of my let-outs. It has happened quite a number of times.
Yes, I do understand. It is NOT possible for the general typical layman to give the developer ALL the required features and requirements at one go.
(Actually, there are some clients who can, because they prepare their requirements first somehow and then they go hunting for developers. But let’s assume them out for this article.)
As for the rest of the prospective clients, how it goes is like this:
So, u will tell what you think that you want.
It’s normal that you might have missed out a thing or 2. Or 10.
It’s okay, to call me or message me to ask again (and again) about the new features that you have thought of.
Even if it’s something that just needs some clarification, it’s fine. Because I’ve been a customer before (of another industry), and sometimes I ask many questions due to lack of knowledge of that industry, and sometimes I fear if I’m overly disturbing the Service Provider (SP).
So, as a SP myself, I try to quell my prospects’ doubts as much as I can, as patiently as possible.
So, yes, all above is CAN DO.
But I CANNOT is:
If you have told me about 10 features, and I have quoted $x for that 10 features, and next day, you want another 2 features, it might be possible that there are extra costs for that, thus, I might tell you so, thus the quote might become $y.
There are some who understand. But there are some who don’t.
One person literally asked me this:
“How come every time I keep talking, you keep increasing the cost quote.”
Duh.
If you’re talking about the climate, I have no reason to touch the cost. You’re talking about new features to add-on. That means you are adding hours or days, or sometimes weeks to the timeline of work I have to do.
So, how can the quote remain the same while you keep changing your requirements, right?
We all have no problem understanding this concept in the supermarket. Literally, the more items you take, the more you expect to pay at the checkout.
Likewise, the more pricier items you take, the more you expect to pay at the checkout.
Likewise, in the development world, the more features you require (or the more complex your requirements are), the more the developer has to work on the project, be it by time or by difficulty.
So, it’s only fair that fair work is paid for fairly.
So, my request is: do adopt this fair mindset when you talk to other developers please.
About the Author
Anees Khan is a freelance web developer for the past 27 years, and is running Getcha Solutions to help companies get the latest tech for their business needs, requirements and operational workflows.
=======================
If you like my writing, now you can subscribe here
and be notified of my next one.
https://getchacom.medium.com/subscribe
If you like Medium, you can consider becoming a Member
and support writers like me.
https://getchacom.medium.com/membership
=======================
