i saw my site wasn't opening at 2 am. Agency customer line is closed. Have to wait until 9 am. Customers can't access my site and are angry. Didn't i have an emergency channel?
24/7 support should be written in the contract. If not, emergency contacts (technical manager's phone) should be listed. If not in writing, business hours support is normal.
Written in contract: 'emergency support channel and response time' should be specified. If not, consider another provider.
Yes, that's exactly how it is with site crashed who to call. The biggest time-waster for us was not knowing who had the final say.
Payment schedules should be tied to project phases, not calendar dates. Correct me if I'm wrong.
Let me speak from the other side; I'm on the supplier side. Code without setup documentation isn't yours, even if you have it.
If you post the result here, it will help others too.
Timely topic. Weekly written progress reports are much more useful than asking for dates.
The real issue isn't the number, but what it's based on. If I were you, I'd go this route.
Exactly like that. anyway the answer varies greatly by industry; there is no one-size-fits-all rule.
Correct me if I'm wrong.
Thanks for writing this, that's the right way. Processes without records never improve, because you don't know what to fix.
I'm also curious if anyone does it differently.
You're right, I've been down that road too. Most time waste accumulates in tasks waiting for approval.
Payment schedules should be tied to project phases, not calendar dates.
We experienced almost the exact same thing last year. The cheapest quote is usually the least thought-out one.
I'll try it. Implementing a change request process doesn't slow things down, it speeds them up.
Most time waste accumulates in tasks waiting for approval.
I felt relieved reading this answer, so it's not just me. Implementing a change request process doesn't slow things down, it speeds them up.
Good luck with that.
Thanks a lot, Ill try it today. The cheapest quote is usually the least thought-out one.
If you get three different answers on a topic the question was asked wrong.
Could you elaborate on that? Everything goes well for the first three months; problems arise in the fourth.
Proven by experience.
I completely agree. If scope grows, either time or budget must grow. There is no third option.
Code without setup documentation isn't yours even if you have it. Just leaving this note it might be useful.