How to deal with rapid changes in project specifications in a compressed urgent scenario?

Question

How to work with a project manager who imposes a really tight deadline, but with a day or so before the deadline leads to new features and specifications for implementation, with another tight deadline.

Worst of all, most of the new material leads to a serious rewrite of the existing code, as previously implemented business rules are no longer applicable or “win” strange corner cases that need to be considered separately.

It seems that no matter how hard we try to make the system extensible, there are always things that appear literally at the last moment and should be quickly implemented and maintained.

How can I deal with this situation? It really demoralizes, and one colleague has already left the team.

Answer 1

It is true that no matter what you do, you are a person and you make mistakes or miss things. However, regular changes to your requirements are most often the result of either weak requirements, or an unsatisfactory development process, or both.

Some design elements to come?

- , .. 1- , PMs : ", 1 - -, ! !" , PM , ( )... , , , . , ; - , , .

, , , , , .

• , - , , , - : . . , , .
• , , , . , , ; , , " ", - , , - ( , , ). ... , , , .

?

, , , , ? , . , , , , . . , , , , , . - , ( , , , ), , , , .

, , , ? -? - , ? .

, . (, ) .

Answer 2

.

2

• PM , , .
• PM . , .

PM - + , . careers.stackoverflow.com

PM , PM .

Answer 3

. , .

, .

, . .

. , Scrum.

, , , . , , , , "" , - - .

"" . , .

Answer 4

, .

, , - . , - , . , .

, , .

Answer 5

? , .

, , . , , , , .
, /. , , . , - , .

, . .

, , - .