If you want to buy the project management book mail
[email protected] for
more details or call any of our book shops MUMBAI-22078296/97/022-22070989,
KOLKATA-22826518/19 HYDERABAD-24756967,24756400,BANGALORE-25587923,
25584641,AHMEDABAD-26421611,BHATINA(PUNJAB)-2237387,CHENNAI-28410796,28550491,DELHI/NEWDELHI-23254990/91,23325760,26415092,24691288.If
you want to write to the author directly email at
[email protected]
Home
Below figure “Agile and Traditional SDLC” points out some
of the main differences. If you have worked practically on both these you can
point out more differences.
- Lengthy requirement documents are now simple and short
user stories.
- Estimation unit man days and man hours are now ideal
days and ideal hours respectively.
- In traditional approach we freeze the requirement and
complete the full design and then start coding. But in Agile we do designing
task wise. So just before the developer starts a task he does design.
- In traditional SDLC we used always hear this voice
‘After signoff nothing can be changed’, in Agile we work for the customer,
so we do accept changes.
- Unit test plans are written after coding or during
coding in traditional SDLC. In Agile we write unit test plans before writing
the code.
![](SDLC_files/image002.jpg)
Figure: -
Agile and Traditional SDLC