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

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

@@ -649,6 +649,28 @@ Not every stage necessarily needs to be shipped to the customer. Maybe only the
 > - 👍🏼 The project's Software Development Plan is up-to-date and is being followed.
 
 ### Beginning of Stage Planning
+For each stage a detailed plan is needed. The project team creates an individual stage plans. Each stage includes planning, design, construction, testing and preparation for release. The idea behind the stages is to convert a big risky project into a stage of smaller more manageable projects.
+
+#### Stage planning overview
+- requirements updates
+- detailed design
+- construction
+- test case creation
+- user documentation updates
+- technical reviews
+- defect corrections
+- technical coordination
+- risk management
+- project tracking
+- integration and release
+- end-of-stage wrap up
+
+Miniature Milestones are a great way to add visibility to the development process. They should be defined in a way where they can be either *done* or *not done*.
+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.
+
+
+
+
 
 
 ---
@@ -673,6 +695,7 @@ Not every stage necessarily needs to be shipped to the customer. Maybe only the
 	- review checklists for different parts
 - Software architecture plan (less than 100 pages, diagram heavy)
 - Staged Delivery Plan
+- Individual stage plans --> add to the software development plan once its finished
 ## Tool list
 - Anonymous risk-reporting channel
 - time tracking (helps for future estimating practices)