Amazon Interview Question Senior Software Development Engineers
Country: United States
Interview Type: In-Person
- Use agile, so that the delay is not under your responsibility instead it will be resolved in scrum of scrums level
- Check grunt chart and adjust the critical path possibly
- Push non critical items to the next release
- Try to borrow some additional resources from peer team with portable skills
If the process is flexible try to adjust the schedule internally i.e. optimise the time by cutting the turn around times with testing team, database approval team, devops reviews etc
- Make the people to come on Saturday and stay late, usually Indians love this however you can’t repeat this often
- Once accomplished report the incident and archive with good details of root cause analysis. Usually the cause will be poor estimation, external dependencies, process flaws distraction & interruption.
We can do the task as much as we can and then deliver the product to client telling him that the next part will be done after getting tested(i.e Incremental Approach of testing).
I agree with you on the part that "do as much as you can" but in my opinion even after knowing the fact that you wont be able to deliver the product requirements on time and telling him at the last moment would make the client more skeptical that you can even deliver the product in the extended time frame or not. It is better to make him aware of the situation as soon as you know about it. Of course he would not be happy but somebody made a mistake in estimating the product's time requirement and that person's team or company would have to bear the losses.
I don't know much about "Incremental approach of testing" but from what I read on the internet, it doesn't really alleviate the problem asked in the question. It rather helps you identify bugs in an earlier stage of the product life cycle so that you don't have to deal with them at a later stage when they become costlier (in terms of time and money) to fix.
I even read somewhere that this makes the entire process more time taking (A disadvantage is that it can be time-consuming since stubs and drivers have to be developed and used in the test.)
First thing is first, tell your manager/ client we might be late in delivery
- meetvasu15 October 29, 2013Next possible steps:
1. consult your Gantt chart - make modifications,
2. try and scope out small / "nice to have" features (at least deliver the major functionality).
3. Do you have a project buffer, can we use it now?
also as "Anonymous " said redo critical path analysis, what went wrong? fix it!