Skip to content
- How do we estimate the maturity of the process?
- What is the difference between the levels of the process maturity model?
- What is meant by the term “overhead” in the software process?
- How is a system prototype different from a beta version?
- How does one avoid “overbuilding” a prototype, which wastes time and border on building the software itself, or “underbuilding” a prototype, which does not leave much room for potential feedback?
- What data should be collected during the process of our software projects in order to assess the efficiency and effectiveness of said process?
- The initial and managed stages of process maturity approach to process management seem very similar. Can you provide an example that might help clarify their differences?
- What is the organization of the agile approach to software management? The stages of process maturity are provided, but those of agile are not.
- What are some examples of things you can measure to judge a process? How might you measure a process’s robustness?
- Does the process improvement cycle only really work when you have many similar projects run after each other?
- What are some changes you may need to make and how would you anticipate them?
- What are some cons to prototyping?
- What would be a in real-life situation where the prototype would be completely discarded after all of the work put into it?
- Are there any examples of small software companies using maturity focused approach?
- Suppose you bought your favorite social media app (let’s say Instagram) and now you can make changes as you want. Which of the two ways described in the textbook would you use to cope with the change and changing system requirements.
- Suppose you bought your favorite social media app (let’s say Instagram) and now you can make changes as you want. Which of the two ways described in the textbook would you use to cope with the change and changing system requirements.
- What are the phases of prototype development?
- Describe the process improvement cycle.
- For incremental delivery, is it important to specify what functions you would need for a particular increment to be fully operational? Would you need to finish all of the functions that run the program before you start delivering increments?
- Would the Wizard of Oz prototype require more thinking before presenting it to make sure the functionality you are claiming is buildable (in the time that you have)?
- What are some examples of a way software can be developed so that it can tolerate change or be inflexible and not tolerate it (are there any famous case studies out there)?
- Why do large software companies use maturity-focused approaches to software process development? Do smaller companies then prefer the agile approach to improve software processes (and why)?
- What is the difference between incremental delivery and incremental development (from the previous chapter). How are they interrelated, if at all?
- Can the two methods of system prototyping and incremental delivery be interwoven with each other when developing software?
- How much detail should it be added into a first prototype? Given the advantages and disadvantages on the book, should we use incremental delivery as an approach to develop our class projects?
