Project Management For Development (PMD) Pro Level 1 Practice Test

In development projects, switching to an assets-based approach means starting from what the team already has—people, skills, networks, resources, and institutional capacities—and asking how those assets can be mobilized to achieve the desired change. This shifts the focus from diagnosing and detailing a problem to leveraging existing strengths, which can accelerate action and build on what’s sustainable in the community. That makes Problem Analysis the best fit to be replaced in this context because it specifically centers on identifying the problem, its causes, and gaps; when teams adopt an assets-based view, they often bypass or downplay this deficit-focused analysis in favor of mapping and deploying available assets. For example, instead of dissecting why a community lacks clean water, you’d inventory local wells, water committees, technicians, funding partners, and other assets to design a practical plan using what’s already there. Other tools—Stakeholder Analysis, Decision Analysis, and Scenario Analysis—serve different purposes (who is SAMPLEinvolved, how to evaluate options, and how outcomes might unfold under different futures) and aren’t typically replaced by an assets-based approach, though they can complement it.