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

vault backup: 2025-01-07 10:32:01

Browse Source
This commit is contained in:
Claudio Fritsche
2025-01-07 10:32:02 +01:00
parent b6631c6d33
commit ad7aec7c9c
7 changed files with 152 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
.obsidian/plugins/text-extractor/cache/4e0954f8883b2596c4803de1ac062d26.json vendored Normal file
View File

@@ -0,0 +1 @@
{"path":"Attachments/Pasted image 20250107095858.png","text":"Self- Actualization (ongoing ; professional development) Self-Esteem (feeling productive, belief in project’s importance) Belongingness and Love (healthy teaf\\ dynamics) Safety Needs : (meeting personal promises for schedule and functionality) Survival Needs (project not canceled, team not fired, adequate physical working conditions, and so on) FIGURE 12 Software project need hierarchy. Needs of the project are only approxi- mately the same as the needs ofthe project's participants.","libVersion":"0.3.2","langs":"deu+eng+fra"}

1
.obsidian/plugins/text-extractor/cache/b9a13a2d9225894bcad130f7d834f0e0.json vendored Normal file
View File

@@ -0,0 +1 @@
{"path":"Attachments/image 14.jpg","text":"7 (IN À Für Smith war eine der Ursachen des Rei i Arbeitsteilung. SO beschrei 5 Keichtums die : ZUSAMMEN PRODUZIEREN SIE der 10 Arl.vei'lzergf\\.ladelnel—îgrçrie:lel:l‘l{e:ænê.r o nanufaictur, In 45 000 NADELN AM TAG — VIEL MEHR ALS ZEHN LEUTE - HERSTELLEN KONNTEN, WENN SIE JEWEILS FUR SICH .___‚ „n ' a ARBEITETEN. hf;” //7 ¥ Î ‚'—' = =)= Un 4‘ S i: S A g . . Au [ K- S| u@{ 5 /‘@ A R, e ‘ v - PN o ;. .l}l. S $ ‘ä” v —— I{.@ æ .‚ ‘‚ — ‚ ‘ a 10 Sand QC ® < B .': R .x .\\':\"\"‘(‘ ; “ \" n - - \"~ > Fs n æ p - . (: - - C - ; ZIEHT BEGRAVIGT MACHT SETZT DEN DEN DIE DEN USW. ICH KANN NICHT DRAHT DRAHT SPITZE KOPF AN MAL EINE EINZIGE . MACHEN! ‘ *Untersuchung iiber Wesen und Ursachen des Reichtums der Vôiker, auch bekannt als der Wohlstand der Nationen 23","libVersion":"0.3.2","langs":"deu+eng+fra"}

57
.obsidian/workspace.json vendored
View File

@@ -92,12 +92,12 @@
"state": {
"type": "markdown",
"state": {
"file": "0 Journal/0 Daily/2024-12-06.md",
"file": "2 Personal/Lists/Business Ideas.md",
"mode": "source",
"source": false
},
"icon": "lucide-file",
"title": "2024-12-06"
"title": "Business Ideas"
}
}
],
@@ -454,10 +454,54 @@
"periodic-notes:Open today": false
}
},
"active": "ee7f474679002df0",
"floating": {
"id": "a2e1db8e76c019cb",
"type": "floating",
"children": [
{
"id": "0db060f3927a5cce",
"type": "window",
"children": [
{
"id": "f6ff4afb4e8ba814",
"type": "tabs",
"children": [
{
"id": "c913626684654e11",
"type": "leaf",
"state": {
"type": "markdown",
"state": {
"file": "5 Media/0 Books/Software Project Survival Guide by Steve McConnell.md",
"mode": "source",
"source": false
},
"icon": "lucide-file",
"title": "Software Project Survival Guide by Steve McConnell"
}
}
]
}
],
"direction": "vertical",
"x": 720,
"y": 25,
"width": 720,
"height": 875,
"maximize": false,
"zoom": 0
}
]
},
"active": "c913626684654e11",
"lastOpenFiles": [
"2 Personal/Home Lab/NAS/Zerotier Installation.md",
"2 Personal/Lists/Business Ideas.md",
"5 Media/0 Books/Software Project Survival Guide by Steve McConnell.md",
"0 Journal/0 Daily/2024-12-06.md",
"Dashboard Canvas.canvas",
"Attachments/Pasted image 20250107095858.png",
"Temporary/Untitled 5.md",
"2 Personal/Home Lab/NAS/Zerotier Installation.md",
"Temporary/Airconditioning.md",
"0 Journal/0 Daily/2024-12-05.sync-conflict-20241205-175455-LIUMLEB.md",
"0 Journal/0 Daily/2024-12-05.sync-conflict-20241205-164917-LIUMLEB.md",
@@ -480,19 +524,14 @@
"5 Media/0 Books/The 7 Habits of Highly Effective People by Stephen Covey.md",
"3 Knowledge/Personality Tests.md",
"2 Personal/Home Lab/VPS/Gitea Setup.md",
"99 Work/My Experience/Experience at OneSec.md",
"0 Journal/0 Daily/2024-12-02.sync-conflict-20241202-182156-LIUMLEB.md",
"0 Journal/0 Daily/2024-12-02.md",
"Attachments/Pasted image 20241118160705.png",
"Attachments/Pasted image 20241118143053.png",
"Attachments/Pasted image 20241118142001.png",
"Dashboard Canvas.canvas",
"Attachments/Pasted image 20241105160637.png",
"Attachments/Pasted image 20241105160145.png",
"Attachments/Pasted image 20241105155616.png",
"Attachments/Pasted image 20241105154304.png",
"Attachments/Pasted image 20241105154101.png",
"Attachments/Pasted image 20241105153834.png",
"Attachments/Gym-Rings-UK.pdf",
"99 Work/Jobhunt/Applications",
"99 Work/0 OneSec/OneSecNotes/30 Engineering Skills/Robotics/Sensors",

5
2 Personal/Lists/Business Ideas.md
View File

@@ -29,9 +29,8 @@ Diese Liste kann auch mit `#idea/startup` oder mit `#business-idea` ergänzt wer
- Müllabfuhr
- Post
- AI website um CV fotos zu perfektionieren. Mach ein foto mit egal welchem hintergrund und du kriegst ein professionelles foto zurück --> App sagt dir wie du fotographieren solltest (auch belichtung, etc.). Bezahlung pro hochqualitäts Foto download 2.-
- cv scanner for companies with LLM (claude)
- cv scanner for companies with LLM (claude) wie floris es gemacht hatte
- checklist app: (add default checklists (e.g. software projects survival guide))
- Tinder for early startups and people who want to work there (early VPs)
___

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

@@ -0,0 +1,100 @@
---
title: Software Project Survival Guide by Steve McConnell
created_date: 2025-01-07
updated_date: 2025-01-07
aliases:
tags:
- book
type: book
book_name: Software Project Survival Guide
author: Steve McConnell
status: not_started
---
# Software Project Survival Guide by Steve McConnell
- **🏷️Tags** : #01-2025 #book
---
## Summary
> [!summary] Summary
> 3 Sentences only!
> - What are the main ideas?
> - If I implemented one idea from this book right now, which one would it be?
> - How would I describe the book to someone else?
---
## Ideas and Thoughts
> [!info]+ Inspiring Questions
> - Did you think about other concepts from other books?
> - Do the concepts fit to your past, to your memories?
> - Can you relive them and reflect them from a different angle?
- We should define exact goals that are measurable: What does the software need to do? What's its accuracy?
---
## Clippings
### Intro
- Software projects fail because of
- lack of knowledge of software project conduct
- lack of resolve --> indecisiveness, procrastination, low confidence, inconsistency
- References
- Key Practices of the Capability Maturity Model, Version 1.1 by Software Engineering Institute (SEI)
- Recommended Approach to Software Development, Revision 3 by NASA Software Engineering Laboratory (SEL)
### The Survival Mindset
- The only outcome considered a failure is total collapse
- Success: meet cost, schedule and quality goals within engineering tolerances (+- 10% of goal)
- **Survival Needs**
- Needs that need to be satisfied before anything else can work (humans: food, shelter, water, air)
- project not canceled, team not fired, adequate physical working conditions
- meeting personal promises for schedule and functionality
- Project team must be satisfied that the project can be completed *at all* before it can worry about the schedule or budget
- ![[Pasted image 20250107095858.png]]
- Individual developers might not prioritise the same needs as the software projects survival needs
#### Stakeholders
Each group involved in the project must respect the rights of the other parties. And each group's survival needs must be thoroughly satisfied such that they can focus on higher level needs. Usually this is the *Customer* and the *Project Team*:
##### Customer's Bill of Rights
1. To set objectives for the project and have them followed
2. To know how long the software project will take and how much it will cost
3. To decide which features are in and which are out of the software
4. To make reasonable changes to requirements throughout the course of the project and to know the costs of making those changes
5. To know the project's status clearly and confidently
6. To be apprised regularly of risks that could affect cost, schedule, or quality, and to be provided with options for addressing potential problems
7. To have ready access to project deliverables throughout the project
##### Project Team's Bill of Rights
1. To know the project objectives and to clarify priorities.
2. To know in detail what product I'm supposed to build and to clarify the product definition if it is unclear.
3. To have ready access to the customer, manager, marketer, or other person responsible for making decisions about the software's functionality.
4. To work each phase of the project in a technically responsible way, especially to not be forced to start coding too early in the project.
5. To approve effort and schedule estimates for any work that Team will be asked to perform. This includes the right to provide only the kinds of cost and schedule estimates that are theoretically possible at each stage of the project; to take the time needed to create meaningful estimates; and to revise estimates whenever the project's requirements change.
6. To have my project's status reported accurately to customers and upper management.
7. To work in a productive environment free from frequent interruptions and distractions, especially during critical parts of the project.
#### 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.
### 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.
There is a list of questions that will be answered with 0-3 points, 3 being fully qualified.
The questions are separated into the following categories
- Requirements
- Planning
- Project Control
- Risk Management
- Personnel
Most projects have a score <50.
| **Score Range** | **Rating** | **Description** |
| --------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 90+ | Outstanding | A project with this score is virtually guaranteed to succeed in all respects, meeting its schedule, budget, quality, and other targets. In terms of Chapter 1's project needs hierarchy, such a project is fully "self-actualized." |
| 80-89 | Excellent | A project at this level is performing much better than average. Such a project has a high probability of delivering its software close to its schedule, budget, and quality targets. |
| 60-79 | Good | A score in this range represents a better-than-average level of software development effectiveness. Such a project stands a fighting chance of meeting either its schedule or its budget target, but it probably won't meet both. |
| 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. |
---
```query
Software Project Survival Guide Steve McConnell
-file: "Software Project Survival Guide by Steve McConnell.md"
```

BIN
Attachments/Pasted image 20250107095858.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 440 KiB

0
Temporary/Untitled 5.md Normal file
View File