i wanted an independent consultant to do a code review at the end of the project. Agency said: reviews are expensive.
The agency should do the review before handover. Findings should be fixed. Send a written request: the agency will conduct an internal review before delivery.
note: I wrote this based on my own experience, it might not apply to everyone.
Theres a trap here let me mention it. Mistakes made on the pre-handover technical review side are usually reversible but expensive.
When you try to change everything at once, nothing settles. Thats all sorry if I went on too long.
Yes, that's exactly how it is with pre-handover technical review. Ask who prepared the quote and who will actually do the work.
Good luck with that.
Doki · Interface design · 2023
absolutely. honestly if I were to add anything: Don't hesitate to ask; those who don't ask always pay more.
Correct in theory, but it doesn't work that way in practice. The cheapest quote is usually the least thought-out one.
Code without setup documentation isn't yours, even if you have it.
i have no experience with pre-handover technical review so Im asking. people defend habits not processes. resistance comes from there.
if you get three differeent answers on a topic the question was asked wrong. good luck with that.
Doki · Infrastructure migration · 2025
Let me clarify the technical side. If scope grows, either time or budget must grow. There is no third option.
Let me summarize what's been said so far. If acceptance criteria aren't written, when the work is done is open to debate.
If acceptance criteria aren't written, when the work is done is open to debate.
There's a common mistake people make when doing this. Start with a small trial; don't commit to everything at once.
Just leaving this note, it might be useful.
There's one point I'm curious about. Access credentials should be opened in the company's name, not personal accounts.
The harder it is to reverse a decision, the slower you should make it. I'm also curious if anyone does it differently.
The opposite happened to me, that's why I'm writing. Implementing a change request process doesn't slow things down, it speeds them up.
That's all, sorry if I went on too long.
I went through the same thing two years ago. Trying to do this alone is the most expensive way.
When making a decision, first look at what data you have on hand. If I were you, I'd go this route.
I felt relieved reading this answer, so it's not just me. Every "we'll look at it later" in a meeting means unbilled work.
Hope this helps.
Three different views emerged, they all complement each other. Most time waste accumulates in tasks waiting for approval.
Processes without records never improve, because you don't know what to fix.