Bureaucrats, darkmatter, Administrators
1,459
edits
WikiCED manual: Difference between revisions
Jump to navigation
Jump to search
→Change processes and development
| Line 159: | Line 159: | ||
In the past, a development process referred to as "waterfall" was often used in software development. A long specification process was supposed to lead to a shorter, more informed development process. However, with specialists doing specification no one could understand, many projects went overtime and budget (or failed outright). | In the past, a development process referred to as "waterfall" was often used in software development. A long specification process was supposed to lead to a shorter, more informed development process. However, with specialists doing specification no one could understand, many projects went overtime and budget (or failed outright). | ||
Development process today has shifted more towards a process referred to as [wp:Agile software development]. Initially, basic examples and prototypes are used to describe the project, and multiple cycles of development, called "iterations," that ideally involved all involved persons, are used to make sure everyone sees the product, and has a chance to comment on it, before another revision cycle. This also allows constant revision of a product. | Development process today has shifted more towards a process referred to as [[wp:Agile software development]]. Initially, basic examples and prototypes are used to describe the project, and multiple cycles of development, called "iterations," that ideally involved all involved persons, are used to make sure everyone sees the product, and has a chance to comment on it, before another revision cycle. This also allows constant revision of a product. | ||
CED literature describes similar processes based on Knowing, Doing and Reviewing (Torjman, 2007). | CED literature describes similar processes based on Knowing, Doing and Reviewing (Torjman, 2007). | ||