Question: An Agile project team from Infosys, has an interactive and in depth discussion onthe challenges faced in adopting evolving design in Sprints. In this meeting,

An Agile project team from Infosys, has an interactive and in depth discussion onthe challenges faced in adopting evolving design in Sprints. In this meeting, the client's design architect is not in favor of adopting Agile design practice. He asks an intriguing question to the Team, "Isn't evolving design costlier than upfront design?" How should the team address this query? As solution design cost will be incurred in every Sprint in Agile approach as compared to the one-time initial allocation cost for design in traditional waterfall, Team should agree with client's design architect and adopt waterfall approach Team should explain to the client's design architect that incremental design gives an opportunity to detect design defects early, improve the design and also start delivering working features early Team should agree with the client's design architect since requirements are frozen and signed off at the beginning of the project in the waterfall and hence the design does not change in future Team should respond by supporting the fact that evolving design provides an opportunity to refactor anomalies in design iteratively, thus saving rework cost in the later stages
Step by Step Solution
There are 3 Steps involved in it
Get step-by-step solutions from verified subject matter experts
