Developer changed, new developer doesn't understand the environment — project will be delayed

Following. Trying to do this alone is the most expensive way.

Weekly written progress reports are much more useful than asking for dates.

This thread is archived.

I feel the same way. Code without setup documentation isn't yours, even if you have it.

If I were you, I'd go this route.

We need to make a distinction here. The answer varies greatly by industry; there is no one-size-fits-all rule.

Of course it varies if your situation is different.

We need to make a distinction here. Mistakes made on the developer changed project stalled side are usually reversible but expensive.

Trying to do this alone is the most expensive way. If I were you, I'd go this route.

We experienced almost the exact same thing last year. btw if scope grows either time or budget must grow. There is no third option.

In legacy systems, the most expensive thing is unknown dependencies. I mean of course, it varies if your situation is different.

Let's separate the concepts, they're getting mixed up. Hasty decisions become decisions you have to fix six months later.

Good luck with that.

Could you elaborate on that? Any unwritten clause becomes a point of disagreement later, as both sides remember it differently.

When we decide without measuring, we always end up in the same place. Proven by experience.

The answer above hits the nail on the head. Just because everyone does it doesn't mean it's right.

This is my opinion, I'm not claiming it's absolute truth.

Three different views emerged they all complement each other. Weekly written progress reports are much more useful than asking for dates.

Implementing a change request process doesn't slow things down, it speeds them up. Of course, it varies if your situation is different.

timey topic.

I'm writing this so you don't make the same mistake. Weekly written progress reports are much more useful than asking for dates.

People defend habits, not processes. Resistance comes from there. Hope this helps.

Exactly like that. Don't hesitate to ask; those who don't ask always pay more.

this is exactly what we experienced but btw implementing a chnge request process doesnt slow things down it speeds them up.

this is my opinion, I'm not claiming it's absolute truth.

Following. If you get three different answers on a topic, the question was asked wrong.

Payment schedules should be tied to project phases, not calendar dates. This is my opinion, I'm not claiming it's absolute truth.

if youre going this route, sort this out first then anyway taking notes for two weeks yields better results than a six-month estimate.

I don't think this advice fits everyone. Ask who prepared the quote and who will actually do the work.

Correct me if I'm wrong.

saved and like the real issue isn't the number, but what it's baseed on.

every "we'll look at it later" in a meeting means unbilled work but of course it varies if your situation is different.