The project is delayed three months/has lots of dependencies/based on old technology. Do you find this appealing/challenging for you? Have you worked in the similar situation?
I want to understand is this executed in Scrum or traditional waterfall? If it is done using Scrum, and if Product Owner had Release burn up or burndown based approach, he/she would have envisaged much earlier than 3 months delay. Because at the end of every Sprint Product Owner can easily find whether the remaining scope can be done in remaining number of Sprints as per the release plan or not. This is possible using average, best and worst velocity calculations. You can also refer brook’s law based justification here (refer to Brook’s law in Google if you do not know). Scrum does not guarantee success but it helps you to understand where you stand and make right decisions such as scope vs time vs cost decisions.
**Hit the link to send your queries to us about this question, our experts will reach out to you at the earliest!