Lot of us ask this to ourselves when we are balancing relationships, balancing work and life and balancing our client expectations. It is not surprising therefore why How much to stretch is always thought of while thinking of balancing something. If you stretch too much or too less, there is a probability of improper equilibrium or aptly, imbalance. However the irony is – there is no fixed answer.
While balancing client expectations and serving client requests, software developers like us often spend late nights fixing that last piece of code, owning up every bit of it. We keep sipping coffee at 2 AM in the morning in office and yet keep looking at that screen. We sit on the chair, clasp our raised hands, bend over backwards till we can and then look up at the ceiling and ask – How much to stretch?
Ironically again, when tables turn, and the same person becomes the client and there is the vendor on the other side of the table – we demand. And when we demand, we forget that to meet our demands, the vendor would actually need to bend over backwards and that stretch is because he wants to delight us. While testing the vendor to see his flexibility and commitment to our goals is needed for sure, increase in the frequency of heightened expectations might impair the vendor altogether. Inadvertent load on server can crash systems while planned distributed load with periodic maintenance and scheduled down-time on the server can even help fine tuning the performance of the server.
What it boils down to is managing expectations at the end of the day. This in no way means that you tone down your expectations affecting delivery quality or timelines. This just means better planning and careful execution of the plan. Setting expectations at the beginning of any relationship, laying out periodic milestones for tangible measurement of progress of work, discussions about work and periodic evaluation and feedback and next set of goal sharing with the vendor surely helps ease of lot of situations.
The biggest beneficiary is the client who saves on time and costs. Stats from secondary sources show that well planned software projects get completed sooner 30% ahead of time. And planning comes with documentation of steps, methods, processes and frameworks and change management. That is the core reason why we focus on change management, prioritization of ‘Must haves’ and ‘Good to haves’ so that the effort is spent in the most optimal way. It has worked well for us and also for our clients since the last 12 years..
Both our clients and us know that we at Mindfire will bend over backwards in any situation when it is related to our delivery. And yet, we focus on planning and prioritization right when we have our first discussion and strive towards executing the plan.
Talk to us at Mindfire with your development needs. You sure would feel glad that you chose us to work for you.