(1) Each Iteration produces a potentially shippable Fix Pack.

(2) The goal is shippable, production quality code - Performance engineering helps in ensuring that the system is designed, built and validated against the required 'Quality of Service' requirements.

(3) You then build a final, shippable bitstream which gets burned onto your platform flash, or whatever method your design uses to configure the FPGA.

(4) Each Iteration outputs a potentially shippable working piece of the product.

(5) It would relieve a lot of stress from the hand-wringing gun-shy customer worried about getting it right because the story needs to be "shippable."

(6) Saying "shippable" to people in the customer role means implies they'd better get the requirements right because that's the way Agile development works.

(7) Design – like architecture and testing – is simply work that needs to be done to construct a potentially shippable increment of product.

(8) The iteration plan defines what should be delivered within the iteration, and the result is a demo-able or shippable build.

(9) It takes the Web service name and packages it to a shippable file.

(10) Iterations in OpenUP keep the team focused on delivering incremental customer value every few weeks by delivering a fully tested demo-able or shippable build (product increment).

(11) There's no need to iterate on something done - really shippable done.