# Projects

## What is a project?

A temporary endeavour to create an unique product, service or outcome.

Key charasteristics:

* Introduce **CHANGE** to the organisation
* **TEMPORARY**, it has a defined begining and an end.
* **CROSS-FUNCTIONAL**, cuts accross organisatinoal boundaries.
* Deals with the **UNKNOWN**.
* **UNIQUE**
* They all vary in **SIZE** and **TIME**.

## Why do organisations use projects?

* Provides strategic alignment of key activities and visibility at the appropriate levels.
* Mechanism to prioritise activities (Benefits, Regulatory, HW Refresh).
* Allows organisations to deliver change in a structured and formal manner outside of BAU.
* Effective and efficient management of organisations limited resources (people & $'s).
* Establish ownership and accountability - Process and the Benefits.
* Provide clarity, buy-in and agreement across what will be done, when who why and outcomes.

## Software Projects

History tells us we have failed (over 70%) Roughly 30% are successful, 50% are challenged (excess in time, budget or people) and only about 20% are completely successful.

### What determines success?

|        Success Factors       |                Percentage                |
| :--------------------------: | :--------------------------------------: |
|     Executive sponsorship    |                    15%                   |
|      Emotional maturity      |                    15%                   |
|       User involvement       | Optimisation - Statement of requirements |
|       Skilled resources      |                    10%                   |
|     Standard Architecture    |                    8%                    |
|         Agile Process        |                    7%                    |
|       Modest execution       |                    6%                    |
| Project Management Expertise |                    5%                    |
|   Clear Business Objectives  |                    4%                    |


---

# 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/projects.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.