Changes for page Agile and Data

Summary

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

Details

Page properties

Content

...	...	@@ -37,10 +37,11 @@
37	37
38	38	### How to Handle Delays?
39	39
40		-If the Agile data produced indicates that there will be a delay, there are a number of ways to deal with the problem:
	40	+**Scope vs Schedule**: In many classic projects, the scope and the schedule are fixed. However, since the effort and requirements of software projects are almost impossible to accurately determine, it is unreasonable to demand the same fixation of scope and schedule. Therefore, either the scope must be flexible and the schedule fixed, or vice versa. This relationship explains the strategies for dealing with the problem when the generated agile data indicates that there will be a delay:
41	41
42	42	* **Schedule Adaption**: It's sometimes possible to postpone the deadline, although this is often not an acceptable option for management.
43		-* **Personnel Increase**: 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.
44	44	* **Scope Adaption**: Stakeholders prioritize features with the highest return of investment (RoI) and remove features with lower RoI from the project scope.
45	45
46		-Decreasing code quality by omitting testing or refactoring is not an option, as it actually slows development and adds to technical debt.
	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	+
	47	+Decreasing code quality by omitting testing or refactoring is not an option, as it actually slows development and adds to technical debt. This is not an option at all.