Agile Development: Adapting To Ever Changing Needs

Is there a way to shave years off of the trial and error implementing Agile?
Find Out Now.

Stefan Andreasen of Kapow Technologies discusses the challenge of adapting to ever changing needs during application development. His company, using IBM’s EGL (Enterprise Generation Language), developers can react quickly to change, creating a more dynamic development process.

[Stefan Andreasen, Kapow Technologies]
In today’s business application development environment, it’s all about agility, and also interaction with the user, with the one that needs the application, because the traditional way of the — what’s called the waterfall model — you sit down, and spend months trying to figure out how we want the end result. You develop it, and you, you don’t get what every, anybody wants! So today it’s like this ping-pong between the development and line of business, and this is really what Kapow solves a lot.

It allows to very quickly to adapt to the ever changing needs in the middle of developing the application. Because nobody have enough brain power to understand that they say, “”We want this,”” and then get exactly the right thing. It’s a refinement process. They get a prototype, and say, “”That’s not exactly what I wanted,”” and they didn’t really think about it because I haven’t seen it before, so Can, could you please do this? And development does that, and then they get it, and so this iterative , process and dialogue between development and, and, and uh, and line of business is essential for building applications today.

And, and this is where we come in — and together with EGL product — it allows the developers very quickly as both change –data sources and change the application — so you get this dynamic and iterative development process to deliver the application that really fits into what line of business wants.