Skip to Content

Changes for page Agile and Data

Last modified by chrisby on 2024/01/13 17:13
From version 11.5
edited by chrisby
on 2023/12/16 14:53
Change comment: There is no comment for this version
To version 11.6
edited by chrisby
on 2023/12/16 14:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -44,4 +44,4 @@
44 44  
45 45  **Personnel Increase**: An alternative to the above strategies may be to invest more human resources in the project. Ideally, neither scope nor schedule need be adjusted. Note that this will result in a short-term drop in productivity, as the new team members require the attention of the original team members (explanations, answering questions, joint familiarization with the project, etc.), which distracts them from their actual work. After this period, productivity will rise above the original productivity as desired.
46 46  
47 -**Never Sacrifice Quality**: Decreasing code quality by omitting testing or refactoring, with the intention of saving time, actually slows development and adds to technical debt. This is not an option.
47 +**Never Sacrifice Quality**: Decreasing code quality by omitting testing or refactoring, with the intention of saving time, actually slows development and adds to technical debt. This is not an option at all.