In-Process Validation (glossary)

From SEBoK
Jump to: navigation, search
The practice of routinely getting user approval to guide each elaboration of the baseline. This technique keeps the user involved and committed to the incremental elaboration of the approach and the incremental verification results. (Mooz, Forsberg, and Cotterman 2003,198)


Mooz, H., K. Forsberg, H. Cotterman. 2003. Communicating Project Management. Hoboken, NJ: John Wiley and Sons.


One reason that small software development projects, using Agile development principles, work so well is that the customer is embedded into the team. Agile teams are usually limited to a maximum of 20 people (although there are instances of teams of teams that have hundreds of people involved and working well). The in-process validation concept can effectively capture the customer involvement as a very positive force on large projects.

SEBoK v. 1.9 released 17 November 2017

SEBoK Discussion

Please provide your comments and feedback on the SEBoK below. You will need to log in to DISQUS using an existing account (e.g. Yahoo, Google, Facebook, Twitter, etc.) or create a DISQUS account. Simply type your comment in the text field below and DISQUS will guide you through the login or registration steps. Feedback will be archived and used for future updates to the SEBoK. If you provided a comment that is no longer listed, that comment has been adjudicated. You can view adjudication for comments submitted prior to SEBoK v. 1.0 at SEBoK Review and Adjudication. Later comments are addressed and changes are summarized in the Letter from the Editor and Acknowledgements and Release History.

If you would like to provide edits on this article, recommend new content, or make comments on the SEBoK as a whole, please see the SEBoK Sandbox.

blog comments powered by Disqus