It's a project management joke.
I suspect the map system is an example of
scope creep (or as SOku says, specifically
feature creep) - It wasn't initially budget for, but some keen developers convinced the money people that it could be done, sold them on the excitement it generates here in our discussions, maybe one of them sold a kidney to fund the extra development time (or perhaps we lost some other features to fund the extra development time) now we're seeing the impact of that - unreliable timelines and resources being pulled in different directions.
Scope creep is when your project starts to move beyond it's initially negotiated parameters or goals. This could be caused by client demands or through changing project requirements or by extra keen developers. Scope creep often means budget blowout, so is to be avoided - unless you're wanting to fleece your client... then you can use it as an opportunity for negotiated
contract variation. I.e. Give us some more $$ so we can finish your project.