vault backup: 2025-01-09 16:13:26

.obsidian/workspace.json

@@ -568,19 +568,19 @@
         "x": 1119,
         "y": 25,
         "width": 1120,
-        "height": 831,
+        "height": 1454,
         "maximize": false,
         "zoom": 0
       }
     ]
   },
-  "active": "73cc7fa99c62cf7a",
+  "active": "c913626684654e11",
   "lastOpenFiles": [
     "Temporary/Untitled.md",
     "5 Media/0 Books/Software Project Survival Guide by Steve McConnell.md",
+    "0 Journal/Meetings/OneSec Cofounder Verhandlung.md",
     "Temporary/Un.md",
     "0 Journal/Meetings/Vidit Update - 8.1.24.md",
-    "0 Journal/Meetings/OneSec Cofounder Verhandlung.md",
     "Temporary/Jira Tutorial.md",
     "Attachments/Pasted image 20250108160308.png",
     "Attachments/Pasted image 20250108160138.png",

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

@@ -365,8 +365,64 @@ Change control only works if all parties accept the decision of the change contr
 - manage risks
 - map out strategies for using personnel
 
-This all goes into a **software development plan**
+This all goes into a **software development plan**.
 
+#### Project Vision
+Effective teams have a common vision and thus a clear understanding of the objective. Having a common vision aligns team members to work effectively together and avoiding time-wasting side trips. 
+- Vision builds trust among team members because they know they work towards the same goal
+- An effective vision can have a motivating effect --> therefore it needs to be elevating
+- It needs to be achievable within the specified time frame
+
+The vision should not promise too much (e.g. short schedule, low cost and rich functionality) since developers are realists and feel fooled with impossible goals.
+##### Deciding What to leave out
+Statements like creating the world's best of something include too much and therefore not provide much guidance to the development team. A good, exclusive vision statement helps the project team achieve the goal of software minimalism, which is essential for keeping project risk to a manageable level.
+##### Committing to the vision
+Formalize through a written vision statement and have it signed by every team member. Then put it under change control! It is the top most guidance element for the team and should be remembered often.
+#### Executive Sponsorship
+Make sure that the decision making comes from a single, clear authority (can be a board). Else decisions from different people do not align with each other and interfere and therefore slow down the entire project.
+
+#### Project Scope Targets
+This is the envisioned schedule, budget, staffing and feature set to get started with. When development starts and you realize that desired features are not in line with schedule and buget you adjust one or the other.
+
+
+> [!Quote] 
+> The best organizations plan to reestimate regularly throughout a project and periodically adjust their project plans based on the reestimation.
+
+Put reestimation points in your plan (just as NASA does, see page 90):
+
+| Estimation Point                             | Upper Limit | Lower Limit |
+|----------------------------------------------|-------------|-------------|
+| End of requirements definition and specification | x2.0        | x0.50       |
+| End of requirements analysis                 | x1.75       | x0.57       |
+| End of preliminary design                    | x1.4        | x0.71       |
+| End of detailed design                       | x1.25       | x0.80       |
+| End of implementation                        | x1.10       | x0.91       |
+| End of system testing                        | x1.05       | x0.95       |
+#### Publicizing Plans and Progress
+Involve the team in the planning phase, because the people who actually do the work often consider all details. If a plan cannot be followed because of wrong planning, it will not be followed and thus the team runs out-of-control.
+- [ ] Get the plans reviewed and approved by the developers
+
+The team needs effective coordination of activities from the project manager, such that efforts are not wasted. Therefore its smart to get the plan approved by the team before the bulk of the work gets started.
+##### Progress Indicators
+Once the project started we have the following indicators to show how well we follow the plan. This creates project visibility.
+- List of tasks completed
+- Defect statistics
+- Top 10 Risks List
+- Percent of schedule used
+- percent of resources used
+- project management's status reports to upper management
+
+- [ ] Create a project intranet homepage (confluence page) with links to planning, tracking, technical work products and project deliverables. Essentially make a dashboard (see page 93)
+
+#### Risk Management
+
+
+
+---
+## Steps towards the Software release
+1. Define requirements
+2. Create initial project estimate (budget, schedule, staffing, desired feature set). 
+3. 
 
 
 ---