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

vault backup: 2025-01-13 14:35:19

Browse Source
This commit is contained in:
Claudio Fritsche
2025-01-13 14:35:20 +01:00
parent 915947f4cc
commit 37522297c4
2 changed files with 13 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
.obsidian/workspace.json vendored
View File

@@ -582,13 +582,13 @@
} }
] ]
}, },
"active": "3b9ff0a0dcd41664", "active": "87bd9046756151ba",
"lastOpenFiles": [ "lastOpenFiles": [
"Dashboard Canvas.canvas",
"5 Media/0 Books/Software Project Survival Guide by Steve McConnell.md", "5 Media/0 Books/Software Project Survival Guide by Steve McConnell.md",
"0 Journal/Meetings/Vidit Update - 8.1.25.md",
"Dashboard Canvas.canvas",
"2 Personal/Alkademiker/Projekte/Tischbeine Motorisiert.md", "2 Personal/Alkademiker/Projekte/Tischbeine Motorisiert.md",
"Temporary/Jira Tutorial.md", "Temporary/Jira Tutorial.md",
"0 Journal/Meetings/Vidit Update - 8.1.25.md",
"Temporary/3D Tourenviewer.md", "Temporary/3D Tourenviewer.md",
"0 Journal/Meetings/Hasan Update - 10.1.25.md", "0 Journal/Meetings/Hasan Update - 10.1.25.md",
"Attachments/Pasted image 20250110145548.png", "Attachments/Pasted image 20250110145548.png",

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

@@ -669,7 +669,15 @@ Miniature Milestones are a great way to add visibility to the development proces
When only long-term milestones are used, the developers can easily lose a day here or a week there— people spend time on detours that seem interesting or productive in some vague sense but that fail to move the project forward. When only long-term milestones are used, the developers can easily lose a day here or a week there— people spend time on detours that seem interesting or productive in some vague sense but that fail to move the project forward.
> [!question] Survival Check - Stage Planning
> - 👍🏼 Planning is conducted at the beginning of each stage to prepare for that stage's activities.
> - 👍🏼 Stage planning includes requirements review, detailed design, coding and code reviews, test case creation, user documentation updates, in-stage defect correction, technical coordination, integration and release, risk management, project tracking, and other important activities.
> - 👍🏼 The project team creates a set of miniature milestones to aid in tracking progress throughout the stage.
> - 💣 The list of miniature milestones does not include all activities.
> - 💣 The project is not actually tracked against the list of miniature milestones.
> - 👍🏼 The project manager adopts a hands-on approach to the project.
### Detailed Design
@@ -687,7 +695,7 @@ When only long-term milestones are used, the developers can easily lose a day he
- Risk officer and other roles: personnell strategies - Risk officer and other roles: personnell strategies
- Decision making authority - Decision making authority
- project scope - project scope
- publicizing of plans and progress - publicising of plans and progress
- time accounting - time accounting
- once finished sign off by project manager, dev team and Q&A team, then place under change control - once finished sign off by project manager, dev team and Q&A team, then place under change control
- Quality Assurance Plan - Quality Assurance Plan
@@ -704,7 +712,7 @@ When only long-term milestones are used, the developers can easily lose a day he
- Review Top 10 Risks every 2 Weeks (see page 97) - Review Top 10 Risks every 2 Weeks (see page 97)
## Checkpoints ## Checkpoints
- reestimates of the schedule and cost - reestimate of the schedule and cost
- during preliminary requirements development - during preliminary requirements development
- during detailed requirements development - during detailed requirements development
- during architectural design - during architectural design