Chapter 4 - Selection of an Appropriate Project Approach
Short Questions with Answers
Q1. What are the two main types of project approaches?
The two major approaches are Plan-Driven and Agile (Change-Driven). Plan-driven methods like
Waterfall follow a fixed, sequential process and are best for projects with stable requirements. Agile
is a flexible approach that emphasizes collaboration, iterative development, and adapting to change.
It is ideal when requirements are unclear or may evolve during the project.
Q2. What is the key difference between Agile and Plan-Driven?
The key difference is flexibility. Plan-Driven is linear and rigid, requiring full planning and
documentation before development begins. In contrast, Agile is iterative and allows changes at any
time. Agile involves continuous user feedback, while Plan-Driven often involves the user mostly at
the beginning and end.
Q3. Name any three factors that influence the selection of a project approach.
The choice between Agile and Plan-Driven depends on several factors, such as:
1. Requirement Stability: Stable favors Plan-Driven, changing favors Agile.
2. Team Experience: Agile needs skilled and self-organizing teams.
3. Customer Involvement: Agile needs frequent feedback; Plan-Driven does not.
Q4. What is the Waterfall model?
The Waterfall model is a traditional, Plan-Driven software development method where each phase
(requirements, design, coding, testing) must be completed before the next starts. It is suitable when
project requirements are clearly defined and unlikely to change. This model provides clear structure
and documentation.
Q5. Define the Agile approach.
Agile is a modern approach that delivers working software in short cycles called sprints. It focuses
on customer collaboration, adaptability, and frequent delivery. Agile is best for projects where
requirements may change, and it relies on teamwork, communication, and quick feedback loops.
Q6. What is a hybrid approach in project management?
A hybrid approach combines the strengths of both Agile and Plan-Driven models. It is used when a
project needs the flexibility of Agile but also requires the structure and documentation of Plan-Driven
methods. For example, planning may follow a structured format, while development is done in Agile
sprints.
Q7. List two Agile frameworks.
Two widely used Agile frameworks are:
1. Scrum: Based on sprints, with roles like Product Owner and Scrum Master.
2. Extreme Programming (XP): Focuses on continuous integration, test-driven development, and
frequent releases.
Q8. What is iterative development?
Iterative development is a method where the software is developed and refined in repeated cycles.
After each iteration, feedback is gathered, and the product is improved. This approach is core to
Agile and helps ensure that user needs are met as the project progresses.
Q9. What is incremental delivery in Agile?
Incremental delivery means releasing parts of the software in small, functional chunks. Each
increment adds value to the user and allows early feedback. This allows teams to deliver working
software sooner and adapt the next stages based on user response.
Q10. Why might Agile not suit every project?
Agile is not ideal for projects that have strict regulatory requirements, minimal customer involvement,
or fixed budgets and timelines. It also may not work well if the team lacks experience or the
organization prefers traditional, hierarchical processes.
Q11. How does customer involvement differ in Agile vs. Plan-Driven?
In Agile, customers are involved continuously through feedback, sprint reviews, and testing. In
Plan-Driven, customer involvement is mostly at the beginning (requirements) and the end (final
delivery), which can delay the discovery of issues or changes.
Q12. How does team expertise affect project approach selection?
Agile requires a skilled, collaborative, and self-managing team because there is less documentation
and more decision-making. In contrast, Plan-Driven can be managed with clearly defined roles,
making it better for teams with less experience or structure.
Q13. What is the V-model in software development?
The V-model is a variation of the Waterfall model where development and testing activities run in
parallel. Each development stage has a corresponding test stage. It is best suited for systems that
require high reliability and well-documented testing.
Q14. Why is documentation less in Agile?
Agile prioritizes working software over comprehensive documentation. The goal is to reduce
unnecessary paperwork and focus on delivering features. Only essential documentation is
maintained to support communication and project goals.
Q15. List two advantages of Plan-Driven methods.
1. Clear Structure: Everything is planned in advance, making it predictable.
2. Strong Documentation: Helps in legal, regulated, or large-scale projects that need detailed
records and approvals.
