We have a site that launched and is feature-complete, we've done all that the client has asked for and fixed a few bugs post-launch. However, I noticed that our site's home page is using 100 SQL queries, and there's no caching. I took half a day to add caching and did it in a branch.Now I'm wondering how I can convince the project manager and other team members and gain support for a post-launch deployment of this optimization.What reasons can I give that it won't harm the project to do this? Or do I just wait until the next project launches to make these sorts of improvements?More details:I can't very well tell future employers that I implemented caching and saw an increase in performance without actually deploying it and capturing the improvement (through google analytics or Page Speed or some other method), or can I?This is an agency environment, none of our projects use any caching or any other performance optimizationThe site has 50k visitorsThe site is only live with full functionality for 1 month, around the end of May it will be replaced with a static page (marketing campaign site)local testing reducing page load from ~3 seconds to ~700ms
how to convince team and project manager that post-launch deployments are okay for new features
agile;management;project;deployment;release
While what you have done is sure to be a good thing, the project manager has to worry about a number of things:testing - what if you break something. Either something in the home page, or some other unintended consequence? The system needs to be retested. Depending on how far your company goes, this could be a large cost.Scheduling user downtime. May be trivial, may be costly.The PM may worry about any political reasons to do this outside a normal release. Telling the customer so soon after release that you want to do an update purely for performance issues that have NOT been raised by users may decrease confidence in the system. Maybe he would prefer this was rolled into a normal release cycle.Additionally, if no-one has reported performance as an issue, then why should the project waste money fixing an issue that to them, does not exist?