obsidian/Main
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

vault backup: 2025-01-07 11:32:02

Browse Source
This commit is contained in:
Claudio Fritsche
2025-01-07 11:32:02 +01:00
parent ad7aec7c9c
commit 14441bc1de
1 changed files with 19 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
5 Media/0 Books/Software Project Survival Guide by Steve McConnell.md
View File

@@ -69,7 +69,14 @@ Each group involved in the project must respect the rights of the other parties.
7. To work in a productive environment free from frequent interruptions and distractions, especially during critical parts of the project. 7. To work in a productive environment free from frequent interruptions and distractions, especially during critical parts of the project.
#### Survival Check #### Survival Check
This tool is a quick check to verify that the essential characteristics for the survival are met. In the book a 👍🏼 or a 💣 is used. This tool is a quick check to verify that the essential characteristics for the survival are met. In the book a 👍🏼 or a 💣 is used. We will use a box just like below for every chapter.
> [!question] Survival Check - Survival Training
> - 👍🏼 Project team's survival needs are being met
> - 👍🏼 The customer and the project team agree to respect each other's software project rights
> - 💣 The agreement in principle is not followed in practice
### Software Project Survival Test ### Software Project Survival Test
The idea of the survival test is to check the chances of survival of a project in different stages and to act upon the neglected areas if needed. The idea of the survival test is to check the chances of survival of a project in different stages and to act upon the neglected areas if needed.
@@ -78,8 +85,14 @@ The questions are separated into the following categories
- Requirements - Requirements
- Planning - Planning
- Project Control - Project Control
- Can progress be tracked and viewed by team members?
- defect tracking, source control, project management software
- Risk Management - Risk Management
- up to date list of risks to the project
- Personnel - Personnel
- Do we have all technical expertise?
- Are there enough team members and are they committed?
-
Most projects have a score <50. Most projects have a score <50.
@@ -91,7 +104,12 @@ Most projects have a score <50.
| 40-59 | Fair | This score is typical. A project with this score will likely experience high stress and shaky team dynamics, and the software will ultimately be delivered with less functionality than desired at greater cost and with a longer schedule. This kind of project stands to experience the greatest benefit from applying the plan described in this book. | | 40-59 | Fair | This score is typical. A project with this score will likely experience high stress and shaky team dynamics, and the software will ultimately be delivered with less functionality than desired at greater cost and with a longer schedule. This kind of project stands to experience the greatest benefit from applying the plan described in this book. |
| < 40 | At Risk | A project with this score has significant weaknesses in the major areas of requirements, planning, project control, risk management, and personnel. The primary concern of a project in this category should be whether it will finish at all. | | < 40 | At Risk | A project with this score has significant weaknesses in the major areas of requirements, planning, project control, risk management, and personnel. The primary concern of a project in this category should be whether it will finish at all. |
> [!question] Survival Check - Survival Test
> - 👍🏼 Project scores at least 60 on the Survival Test
> - 👍🏼 The project scores less than 60, but corrective actions are planned to improve its score.
> - 💣 The project team doesn't follow through on the planned corrective actions.
### Survival Concepts
--- ---
```query ```query