Difference between revisions of "In-Process Validation (glossary)"
m (Text replacement - "'''SEBoK v. 2.2, released 15 May 2020'''" to "'''SEBoK v. 2.3, released 30 October 2020'''") |
m (Text replacement - "<center>'''SEBoK v. 2.3, released 30 October 2020'''</center>" to "<center>'''SEBoK v. 2.4, released 19 May 2021'''</center>") |
||
| Line 8: | Line 8: | ||
[[Category:Glossary of Terms]] | [[Category:Glossary of Terms]] | ||
| − | <center>'''SEBoK v. 2. | + | <center>'''SEBoK v. 2.4, released 19 May 2021'''</center> |
Revision as of 00:31, 18 May 2021
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)
Sources
Mooz, H., K. Forsberg, H. Cotterman. 2003. Communicating Project Management. Hoboken, NJ: John Wiley and Sons.
Discussion
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.