From 7a052d5446dfaaa94e8ce1d042508a9f080f125f Mon Sep 17 00:00:00 2001 From: Claudio Fritsche Date: Wed, 8 Jan 2025 14:42:38 +0100 Subject: [PATCH] vault backup: 2025-01-08 14:42:38 --- .obsidian/workspace.json | 2 +- ...oject Survival Guide by Steve McConnell.md | 22 ++++++++++++++++++- 2 files changed, 22 insertions(+), 2 deletions(-) diff --git a/.obsidian/workspace.json b/.obsidian/workspace.json index 1089a64..cebf755 100644 --- a/.obsidian/workspace.json +++ b/.obsidian/workspace.json @@ -543,10 +543,10 @@ "active": "c913626684654e11", "lastOpenFiles": [ "0 Journal/Meetings/Vidit Update - 8.1.24.md", + "5 Media/0 Books/Software Project Survival Guide by Steve McConnell.md", "Attachments/Pasted image 20250108110043.png", "Temporary/Vidit Update - 8.1.24.md", "2 Personal/Lists/Business Ideas.md", - "5 Media/0 Books/Software Project Survival Guide by Steve McConnell.md", "Attachments/Pasted image 20250107121222.png", "Attachments/Pasted image 20250107120429.png", "Attachments/Pasted image 20250107114628.png", diff --git a/5 Media/0 Books/Software Project Survival Guide by Steve McConnell.md b/5 Media/0 Books/Software Project Survival Guide by Steve McConnell.md index c663cfc..c04cda1 100644 --- a/5 Media/0 Books/Software Project Survival Guide by Steve McConnell.md +++ b/5 Media/0 Books/Software Project Survival Guide by Steve McConnell.md @@ -213,11 +213,31 @@ Benefits of splitting development into these two funding phases: 2. More reliable funding for the bulk of the project, because it can be better estimated 3. Forces project manager to do upstream work in the first 10-20% --> setting the project up for success. #### Risk Management +You can hope for the best but should prepare for the worst --> risk management. +Typical risks: +- failure to plan +- failure to follow the plan that has been created +- failure to revise the plan when project circumstances change + +Software development is a high-risk activity, which is why it is essential to perform risk managment. + +> [!Quote] By Tom Gilb +> If you don't actively attack the risks on a software project, they will actively attack you. #### Project Control - +Without project control every project is *out of control*, which is definitely something we do not want. We do not want to control the people, but rather the project itself: +- Choose a software lifecycle model (e.g. staged delivery) to provide a framework +- requirements change management --> only update what is necessary +- Design and coding standards, to have consistency +- write detailed plan of project to align developer's work with goals and to minimize conflicts in between developers #### Project Visibility +The visibility is the ability to determine a project's true status, which will give answers to questions like: +- Is the project on track to achieve goals? +- Are we within 10% of budget and schedule or only within 50%? +Activities that help achieve visibility: +- Vision Statement +- Hold a planning checkpoint review after 10% of the project #### Peopleware #### User Involvement