Discussion Questions

Ch 2.3-2.4

  1. The issues with incremental delivery were pretty well outlined in the text, but what are the downsides or restrictions that are associated with prototyping?

  2. Does software improvement help undo the degradation associated with incremental development?

  3. Is there a difference between customer testing and prototyping/incremental delivery?

  4. What are some examples of overhead in the software process?
  5. Do stakeholders generally take part in the process analysis component of the software improvement process?

  6. How do you decide which prototypes to release to stakeholders for testing? Is there a model for that decision?

  7. In terms of flexibility of making changes, is prototyping more flexible or is incremental development?

  8. How is prototyping different from testing in the software validation process?

  9. What are some examples of ‘process data’ that are used to measure software process improvements?

  10. With regards to the projects we have in this class, which type of coping and change should we lean towards? In such cases, is there necessarily a right/wrong option?

  11. What is the distinction between process improvement and iterative delivery? This confusion arises from the definition given in the key points section where it says: “Process improvement is the process of improving existing software processes to improve software quality, lower development costs, or reduce development time. It is a cyclic process involving process measurement, analysis, and change.”

  12. What does it mean for a process to mature and how is this different from software improving as it evolves?

  13. What is the structure of printed progress reports? Are they always different and must be read by everyone or are they organized by statistics and distributed to the developers concerned with specific data?

  14. How does a programmer deal with a client who does not have a comprehensive idea of what they want from their software?

  15. When using the prototype model, how does a programmer decide which aspects of the final project they want to leave out in order to develop a prototype as quickly as possible?

  16. Could the agile approach work in a large company setting, or does this setting inherently require the structure of the process maturity approach?

  17. Is incremental delivery harder to pull off with larger, corporate clients, whose bureaucratic structures could slow down the feedback cycle?
  18. Does process maturity primarily refer to the planning and design of a process?

  19. For the prototyping process, would a developers always trust that the customer's most important requirement is the actual main requirement needed for the system?

  20. What does it mean to "re-measure attributes" after every increment?

  21. In real-life projects such as the ones we will be involved in, what kind of delivery schedule or process should we be thinking about / what do you recommend?
Edit | Attach | Watch | Print version | History: r6 < r5 < r4 < r3 < r2 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r6 - 2018-01-22 - JimSkon
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback