Waterfall

Agile movement was so successful over the course of past 15 years that there exists now young programmers who never worked in a waterfall fashion and have therefore no idea how explicit requirements, design, implementation, verification, and maintenance phases look like in practice. When they see something remotely similar to a planning activity, they immediately yell "waterfall" as if this would be a curse word of some sorts. Even if we omit the phases of requirements gathering and design, they happen nonetheless but in opaque manner in the heads of programmers without any participation from the rest of the company. Including the rest of the company in the product planning instantly increase the size of an iteration from days to weeks as the rest of the company has its own goals to meet and cannot dedicate all their time to product development. What looks like a short iteration in the eyes of sales or customer support, feels like eternity to programmers who got used to deliver their wares in hours or days instead of months and years as was the case in days before agile software development movement. To bring software development back in sync with the pace of the wider organization, we might need to slow down a bit and maybe even consider slow programming movement.