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

vault backup: 2025-01-08 17:44:38

Browse Source
This commit is contained in:
Claudio Fritsche
2025-01-08 17:44:38 +01:00
parent 815c5681c4
commit 36771b7e5b
3 changed files with 50 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -340,6 +340,23 @@ Use lists from book pages 65ff.
### Hitting a moving target
#### Change Control
[[Floris]] is no fan of change control, and the book explains why: he could have any changes made at any time before, with change control there is a process which needs to be followed.
> [!Quote]
> People who are used to getting their way can still get their way with systematic change control, but they'll have to do it through a process that emphasizes visible decision making and accountability.
Change control only works if all parties accept the decision of the change control board.
> [!question] Survival Check - Change Control
> - 👍🏼 The project has a change board.
> - 💣 The change board's decisions can be reversed by management, marketing, or the customer.
> - 👍🏼 The project has a written, approved Change Control Plan.
> - 💣 Project team members aren't given enough time to carry out the plan.
> - 💣 Work products aren't actually put under change control.
> - 👍🏼 Change Proposals are evaluated by all the project's concerned parties before they are resolved.
> - 👍🏼 The change board notifies the project's concerned parties of how each Change Proposal is resolved.
> - 👍🏼 The change board has the project team evaluate changes in batches so that the team is not distracted by a constant barrage of change requests.