Just as describing a methodology through its process introduces problems of interpretation, so does describing it with its work products. In a small methodology such as Clear, the number and formality of intermediate work products is reduced quite significantly. The team lives from their personal communication, notes on the whiteboards or posters around the room, and demos or deliveries to the user base.
Nonetheless, a description of the work products is necessary. People just starting with Crystal Clear need to see what counts as an “acceptable” set of work products. Executives and sponsors need to see what they are entitled to ask for. Teachers need a set of work products to have students practice on. Teams that are doing too little in the way of planning and documentation need to see what is worth preparing in even a light agile methodology. People working to understand a methodology will want to examine the work products as part of the overall methodology package.
How many work products are needed in software development - AC
Link: How many work products are needed in software development - AC