diff --git a/.obsidian/workspace.json b/.obsidian/workspace.json index 03e3e53..ecd48a6 100644 --- a/.obsidian/workspace.json +++ b/.obsidian/workspace.json @@ -582,13 +582,13 @@ } ] }, - "active": "3b9ff0a0dcd41664", + "active": "87bd9046756151ba", "lastOpenFiles": [ - "Dashboard Canvas.canvas", "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", "Temporary/Jira Tutorial.md", - "0 Journal/Meetings/Vidit Update - 8.1.25.md", "Temporary/3D Tourenviewer.md", "0 Journal/Meetings/Hasan Update - 10.1.25.md", "Attachments/Pasted image 20250110145548.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 1bcb95d..eb3ab7a 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 @@ -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. +> [!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 - Decision making authority - project scope - - publicizing of plans and progress + - publicising of plans and progress - time accounting - once finished sign off by project manager, dev team and Q&A team, then place under change control - 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) ## Checkpoints -- reestimates of the schedule and cost +- reestimate of the schedule and cost - during preliminary requirements development - during detailed requirements development - during architectural design