Changes for page Agile and Data

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -42,6 +42,6 @@
42	42	* **Schedule Adaption**: It's sometimes possible to push back the deadline to give developers more time to implement all the stories, although this is often not an acceptable option for management.
43	43	* **Scope Adaption**: Stakeholders prioritize features with the highest return on investment (ROI) and remove features with lower ROI from the project scope to meet the original deadline.
44	44
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.
	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. **Brook's Law** is an inference from this fact, which states that adding personnel to a late project will delay it even further due to the initial drop in productivity.
46	46
47	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.