# Project Screening

## Basic idea

The portfolio-level decision of *which* projects to do at all. Organisations need a formal, structured process to select, prioritise, oversee, and hold projects accountable — otherwise resources go to whoever shouts loudest.

## Key facts

* Screening criteria typically combine strategic fit, ROI, risk, resource availability.
* Done at portfolio level, not by individual project teams.
* Output: prioritised list of approved / deferred / rejected projects.

“If you don’t know where your going any road will take you there”. Any Road by George Harrison –The Beatles

* The place to start is at the beginning!
* Organisations need a formal, structured approach to:
  * Select
  * Prioritise
  * Have oversight
  * Drive accountability

![Project Screening](/files/uw2wC5S7yCzIwxg6EBCc)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://isubasinghe.gitbook.io/isithas-wiki/software_engineering/management/process_and_management/project_screening.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.