The project itself represents a chain of applications that had to fit into the client’s existing IT infrastructure. While the client’s product owners had good knowledge about the core functional requirements, they didn’t know much about things like security, logging, availability, performance, etc. The biggest challenge was to fill in the requirements for the organization team of the customer because it required meetings with a lot of people from different departments. So, a lot of things had to be changed starting from the basics.
When using a “traditional” approach, the main issue is that in most cases the problems are not detected until the final testing, and the process for revision can be long and expensive. The control over the requirements can create a very inflexible approach that is not prompt for changes, and there is limited customer feedback until the final user Acceptance testing. Agile principles are all about being collaborative, flexible and adaptive. It’s built on the premise that the world now changes regularly, and that means software teams no longer have years to bring new products to market.
Encourages teams to regularly show off their work and gather feedback so they can adapt to change quickly.
Adaptability – an alternative way for companies to manage projects that involve high levels of uncertainty.
Time to market – the potential to significantly accelerate the startup phase of the new project.
Reduced costs – opportunities to reduce the cost and overheads associated with the project.
Customer satisfaction – Produce a higher-value solution that is better aligned with user needs.
Organizational agility – Build much higher levels of collaboration, trust, and shared responsibility.