vault backup: 2025-01-08 14:42:38
This commit is contained in:
2
.obsidian/workspace.json
vendored
2
.obsidian/workspace.json
vendored
@@ -543,10 +543,10 @@
|
|||||||
"active": "c913626684654e11",
|
"active": "c913626684654e11",
|
||||||
"lastOpenFiles": [
|
"lastOpenFiles": [
|
||||||
"0 Journal/Meetings/Vidit Update - 8.1.24.md",
|
"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",
|
"Attachments/Pasted image 20250108110043.png",
|
||||||
"Temporary/Vidit Update - 8.1.24.md",
|
"Temporary/Vidit Update - 8.1.24.md",
|
||||||
"2 Personal/Lists/Business Ideas.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 20250107121222.png",
|
||||||
"Attachments/Pasted image 20250107120429.png",
|
"Attachments/Pasted image 20250107120429.png",
|
||||||
"Attachments/Pasted image 20250107114628.png",
|
"Attachments/Pasted image 20250107114628.png",
|
||||||
|
|||||||
@@ -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
|
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.
|
3. Forces project manager to do upstream work in the first 10-20% --> setting the project up for success.
|
||||||
#### Risk Management
|
#### 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
|
#### 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
|
#### 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
|
#### Peopleware
|
||||||
|
|
||||||
#### User Involvement
|
#### User Involvement
|
||||||
|
|||||||
Reference in New Issue
Block a user