The concept of traditional construction could not be a worse metaphor for software development. Yet, for a long time, that’s exactly how it was done. With this kind of formal architectural engineering process, the “right” set of requirements were predetermined and translated into blueprints then implemented, with the hope that enough up-front design would prevent any uncertainty down the road. But because the very nature of software requirements is in a constant flux, this process ensured failure before the first line of code written could be written.
Topics: Agile Software Development
Being competitive isn’t about being bigger anymore; it’s about being swift and adaptable. It is not the big fish which eats the small fish; it’s the fast fish which eats the slow fish. What makes these newer players different as far as adaptability and agility go?