AGILE is a sofware process created in the mid-1990s
Spawned many, more defined, processes most notably "Extreme Programming."
Individuals and interactions over processes and tools.
Individuals and interactions over processes and tools.
Working software over comprehensive documentation.
Customer collaboration over contract negotiation.
Responding to change over following a plan
To understand the AGILE Method we must understand the Waterfall Method.
Waterfall Process
AGILE follows an "iterave approach".
AGILE Process
Each iteration passes through a full software development cycle: including planning, requirements analysis, design, coding, testing, and documentation.
Each iteration usually lasts 1-4 weeks.
Test before you code.
Get each iteration fully integrated and 'bug free' before moving on.
Good Time For AGILE
Low criticality
Senior developers
Requirements change very often
Small number of developers
Culture that thrives on chaos
Bad Time For AGILE
High criticality
Junior developers
Requirements don't change too often
Large number of developers
Culture that demands order
Sample Exam Questions
Question #1: What are two of five features of a project where using an AGILE would be a good idea?
Solution #1: Low criticality, Senior developers, Requirements change very often, Small number of developers, Culture that thrives on chaos
Question #2: True / False: The AGILE Process is the same as the Staged Delivery (or Iterative) Process
Solution #2: False, the key difference is that each Iteration for Staged Delivery Process is multiple requirements, whereas for the AGILE process each Iteration is only one requirement.
