vault backup: 2025-01-08 16:44:38

.obsidian/plugins/text-extractor/cache/2f0141b61eb6fb93b6a8cf93ef1bb0ba.json

@@ -0,0 +1 @@
+{"path":"Attachments/Pasted image 20250108160308.png","text":"Requirements Release 15.0% _ — Development 12.0% Stage3 (80 DY 27% (0 A o Stage 1 | 217% Ç É> Stage 2 ‘ Each stage includes detailed . 21.7% design, construction, and äâæm _ testing, which overlap as shown in Figure 5-3. FIGURE 55 Activity distribution by percent of schedule consumed, assuming a project is divided into three stages. (Numbers do not add to WO percent due to rounding error.) Compare thisfigure to Figure 5-4: schedule and effort on a software project are not dis- tributed in exactly the same way.","libVersion":"0.3.2","langs":"deu+eng+fra"}

.obsidian/plugins/text-extractor/cache/f0a5703ebb4c7e867960770d865d7c3b.json

@@ -0,0 +1 @@
+{"path":"Attachments/Pasted image 20250108155841.png","text":"SN NN NN U O NNN NN NN NNN : SS —— NI NN } N E “ \\ S EN TS ESL ANNANNN Planning Checkpoint Time — Review FIGURE 53 Typical activity overlap. Early activities of requirements development and architecture do not overlap as much as later activities ofdetailed design, coding, integration, and testing. Bar thickness indicates the relative staffing levels throughout the phases of a project.","libVersion":"0.3.2","langs":"deu+eng+fra"}

.obsidian/plugins/text-extractor/cache/fb932d807609b861da2a23233f286554.json

@@ -0,0 +1 @@
+{"path":"Attachments/Pasted image 20250108160138.png","text":"Requirements Release 10% Development 6% chiteclm‘eß% sysem Tesing @ DS \\ pusin 0% YL ; 21100 Consirùcfion 40% FIGURE 5-4 Activity distribution by percent of effort consumed.","libVersion":"0.3.2","langs":"deu+eng+fra"}

.obsidian/workspace.json

@@ -542,6 +542,9 @@
   },
   "active": "c913626684654e11",
   "lastOpenFiles": [
+    "Attachments/Pasted image 20250108160308.png",
+    "Attachments/Pasted image 20250108160138.png",
+    "Attachments/Pasted image 20250108155841.png",
     "0 Journal/Meetings/Vidit Update - 8.1.24.md",
     "5 Media/0 Books/Software Project Survival Guide by Steve McConnell.md",
     "Attachments/Pasted image 20250108151953.png",
@@ -576,8 +579,6 @@
     "5 Media/0 Books/Surrounded by Idiots by Thomas Erikson.md",
     "5 Media/0 Books/ by .md",
     "5 Media/0 Books/Surrounded by Idiots by Thomas Erikson.sync-conflict-20241025-131108-LIUMLEB.md",
-    "Attachments/Pasted image 20241118160705.png",
-    "Attachments/Pasted image 20241118143053.png",
     "Attachments/Gym-Rings-UK.pdf",
     "99 Work/Jobhunt/Applications",
     "99 Work/0 OneSec/OneSecNotes/30 Engineering Skills/Robotics/Sensors",

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

@@ -294,7 +294,7 @@ Different phases of a project have different characteristics. They need to overl
 ![[Pasted image 20250108151953.png]]
 
 #### Project Flow
-Staged delivery!
+**Staged delivery!**
 We want to ship staged versions of the software continuously in order to deliver something that works and improve upon it (ideally with more user feedback).
 Each stage is released after detailed design, coding, debugging and thorough testing.
 ##### Benefits of Staged Delivery
@@ -307,7 +307,42 @@ Each stage is released after detailed design, coding, debugging and thorough tes
 4. Status-reporting overhead is reduced:
    Shipped and working software is a more accurate status report than a paper report.
 5. Makes More Options Available: you have releasable software at all times, meaning if you want to release something is is much less work than if you don't
-6. Reduces possibility of estimation error
+6. Reduces possibility of estimation error: each delivery is a syncronizing event because you can compare the estimates with what is delivered and improve your estimation skills.
+7. Balances Flexibility and Efficiency: It avoids a situation like [[analysis paralysis]], because you can ship a small stage efficiently.
+##### Cost of Staged Delivery
+- You need to retest software at every stage
+- You need to execute merging and other version control tasks 
+- You need to manage different versions
+- You need to plan the staged deliveries
+
+Some of those costs are just exposed earlier in the process and would remain hidden (but still exist) otherwise.
+
+#### Project Phases
+The phases described above slightly overlap, which is inevitable and desirable.
+![[Pasted image 20250108155841.png]]
+
+
+##### Distribution of Effort
+![[Pasted image 20250108160138.png]]
+
+![[Pasted image 20250108160308.png]]
+
+Note that e.g. requirements development requires 12% of the time, but only 6% of the effort, because it is less tangible and requires deeper contemplation such that it is done at a slower pace. This also means that it doesn't produce a lot of code.
+
+##### Milestones and Deliverables
+Use lists from book pages 65ff.
+
+
+> [!question] Survival Check - Successful Project at a Glance
+> - 👍🏼 Project uses a staged delivery approach
+> - 👍🏼 Upper management, customer or both track progress by code growth curve
+> - 👍🏼 Upper management, customer or both track progress by keeping tabs on major milestones and deliverables
+
+### Hitting a moving target
+#### Change Control
+
+
+
 ---
 ```query
 Software Project Survival Guide Steve McConnell