C1 M3- Overview of Waterfall and Agile Flashcards
What are the two most popular project management methodologies?
Waterfall and Agile.
When was the Waterfall methodology created, and what does it refer to?
Waterfall was created in the 1970s and refers to the sequential ordering of phases, where each phase is completed one at a time in a linear fashion.
In which fields was the Waterfall methodology first used?
It was first used in physical engineering disciplines like manufacturing and construction, later extending to software engineering.
What are the phases of a Waterfall project life cycle?
The phases are Initiating, Planning, Executing (managing and completing tasks), and Closing.
When is the Waterfall methodology best suited for a project?
Waterfall is best for projects where:
- The phases are clearly defined.
- Tasks must be completed in a specific order.
- Changes are very expensive to implement once the project starts.
What does the term “Agile” mean in project management?
Agile refers to the ability to move quickly and easily, emphasizing flexibility, adaptability, and iterative processes.
When did the concepts of Agile emerge, and when was it officially named?
Agile concepts emerged in the 1990s and were officially named Agile in 2001.
How do the phases of Agile projects differ from Waterfall projects?
Agile phases overlap, and tasks are completed iteratively, unlike Waterfall, where phases are completed sequentially.
What are sprints in Agile methodology?
Sprints are short chunks of time (usually 1-4 weeks) where a team focuses on completing specific tasks.
What is Scrum, and how is it related to Agile?
Scrum is a form of Agile that organizes work into sprints to focus on delivering specific tasks iteratively.
When is Agile methodology best suited for a project?
- The client has a general idea but no concrete details about the end result.
- High levels of uncertainty or risk are involved.
- Regular feedback and adjustments are required.
How does Agile reduce wasted effort compared to Waterfall?
Agile allows for early feedback, iterative adjustments, and flexibility to adapt to changes, reducing wasted time and resources.
