3 ms·

> we're not going to make the release > At what point should I start sounding the alarm? Immediately. IMMEDIATELY

• tobyhinloopen 8y ago
  This was also my thought, hah :)
• arendtio 8y ago
  Well, ring the bell NOW so you still have time to act. Make sure you bring all the facts you have that make you think that you will miss the release. Ask your team what they think how much time it will take them, given that new evidence. Then get everybody onboard (your direct manager first). Talk about the problems you have and how you can solve them. Make a plan that everybody believes in and set a new release date together. In general, modernization projects are not about timing, but about high quality. So cost are the only variable here, making it important to know how much that project is worth for your organization. Is it just nice to have or critical for the development of the next years as it cleans up a lot of technical debt? Keep that in mind as the consideration of stopping a project is always on the table when it leaves its frame.
• muzani 8y ago
  Yes, ring it loud. If you think there might not be enough time, there's almost certainly not enough time. Start setting up meetings with the project owner ASAP. People are usually more angry if not informed. If they've been informed in advance, there are a lot of options that can be taken, and it lifts a little blame off the dev team.