Log In  

CI Engineering

Version 4 by John Graybeal on Dec 01, 2009 20:25. << Changes from 3 to 4 compared with Current by John Graybeal on Dec 01, 2009 20:25. (show comment) (hide comment)

Key These lines were removed. This word was removed. These lines were added. This word was added. View page history

There are 1 changes. View first change.

		The focus of the development period is on executing the iteration tasks described in the [Design Period|Design Period Activities] and developing specifications and tested software in accordance with designs.
		The development period can include design tasks if that is necessary. It should also include most of the documentation tasks needed to fully frame the development products. By the end of the development period, it is expected that the technical work and most major documentation on the task will be complete. Summary Confluence pages should be largely constructed, with only minor open issues. Many Jira task Comments will have been issued (as each work item is completed), though some may be pending. It is important that the Development Period include these documentation products, so that the [Wrap-Up Period|Wrap-Up Period Activities] may be performed on their restricted schedule.
		h2. Level of Documentation
		How much is enough documentation? The following is taken from Page 7 of the Spiral Model - LCO-LCA Deliverables document:
		_Ensure that the content of artifacts and activities is risk-driven. If this is not the case, the project will either fail to achieve
		critical success conditions or will waste effort in performing unnecessary or dysfunctional activities. The risk criterion is the best way for a project to determine "how much is enough" specifying, prototyping, reusing, testing, documenting, reviewing, etc._
		_Ensure that the content of artifacts and activities is risk-driven. If this is not the case, the project will either fail to achieve critical success conditions or will waste effort in performing unnecessary or dysfunctional activities. The risk criterion is the best way for a project to determine "how much is enough" specifying, prototyping, reusing, testing, documenting, reviewing, etc._