Please enable JavaScript.
Coggle requires JavaScript to display documents.
3.3 (7) (Agile Development (Characteristics (• Replanning the project at…
3.3 (7)
Agile Development
-
Characteristics
• The use of small, time-boxed sub projects or iterations. In this instance, each iteration forms the basis for planning the next iteration. #
• Replanning the project at the end of each iteration (referred to as a “sprint” in Scrum),
including
reprioritizing requirements,
-
-
• Compared to traditional methods, Relatively greater reliance
ON TACIT KNOWLEDGE —the knowledge in people’s heads—as opposed to external knowledge that is captured in project documentation
-
• At least some of the agile methods stipulate pair-wise programming (two persons code the same part of the system) as a means of sharing knowledge and as a quality check.
• A change in the role of the project manager, from one primarily concerned with planning the project, allocating tasks and monitoring progress to that of a facilitator and advocate.
-
Advantage
• Only plans for the next iteration in detail, rather than planning subsequent development phases.
• Uses an adaptive approach to requirements and DOES NOT EMPHASIZE MANAGING A REQUIREMENT BASELINE .
• Focuses on quickly proving an architecture by building actual functionality versus formally defining,
early on, software and data architecture in increasingly more detailed models and descriptions.
• Assumes limits to defect testing but ATTEMPTS TO VALIDATE THE FUNCTIONS THROUGH A FREQUENT BUILD-TEST LIFE CYCLE and
-
• Does not emphasize defined and repeatable processes, but instead performs and adapts its development based on frequent inspections.