Old school coder trying to understand Agile Dev -
scrum, kanban, stories, oh my! i'm developer got started way in 90s, , i've started work @ companies have adopted agile development methodology. as i've googled around, i'm unable find really document explaining wtf agile (as terminology comes it) , how compares old school development. there sites can recommend? don't understand concept of sprint, example. picture developers madly typing @ 120wpm vs usual 80wpm. ;)
first, basics lay in agile manifesto.
a typical un-agile process waterfall model, development phases (requirements, design, implementation, testing,... ) follow each other in sequence.
this brings along high risk, becouse when developers misunderstood reqirements, not noticed until whole development basicly done, because requirements chekced in latter phase implementation.
agile development typically tries reduce risk covering phases in iterations. in scrum called sprint. contains specifiying requirements, designing, implementation , approval.
Comments
Post a Comment