Question:

PLEASE CLEARLY WRITE YOUR NAME, COMPUTING ID, AND SFU ID AT THE TOP OF THE PAGE
"
Respond in 3-6 concise sentences. You and 2 others are part of a freelance development team. Your client, a pizza restaurant, wants a website to manage their employee schedules. Briefly describe the software process model you will use to build their scheduling website. Explain why you chose that software process instead of a different process. Mention potential drawbacks of your choice where appropriate.

When you are finished, turn over your paper and wait until the quiz is complete.
"


Marking criteria:

5 criteria worth 1 point each:
1. Name/give a short description of a concrete software process model.
2. You should have at least one reason why you chose it.
3. You should have at least one reason why you didn't choose a different model.
4. You should be able to think of at least one drawback for your choice.
5. Your response should be concise and direct.

For criteria 1, basically any software process you mention by name will work: XP, scrum, agile, waterfall, and their description needs to be accurate but not necessarily complete. I'm looking for evidence you understand what the process you chose actually is.
For criteria 2, the reason you choose should make sense and be accurate to the definition of the process you chose.
For criteria 2-4, if you list multiple reasons/drawbacks, and half or more are inaccurate or otherwise bad, then you do not get the point.
For criteria 5, if their writing is vague or strays off topic, you get 0 or 0.5.


A sample response that I'd give full marks to:

"An agile process like scrum or XP would be best because it allows us to solicit feedback from the restaurant frequently, ensuring that we build the right thing. In contrast, a waterfall process could easily lead to us building the wrong thing without realizing for months. One bad thing about agile processes is having constant communication with the restaurant can be difficult."

And a wordier response that I would also give full marks to:

"We’d use an Agile (Scrum-inspired) process, delivering the scheduling site in short sprints with frequent client feedback. This lets the restaurant quickly see working features (like adding employees or generating weekly schedules) and adjust requirements as they discover what works best. Unlike Waterfall, which locks requirements upfront and risks misalignment, Agile reduces wasted effort if priorities shift. The drawback is that Agile needs the client’s regular involvement, which can be hard if they’re busy running their restaurant. Still, the flexibility and faster delivery of useful features outweigh that overhead."

A student response that I gave full marks to:

"Given the wording of this question, I assume that the pizza company (our customer) will not have specified very clear requirements for what the software must do. Thus, we need to be adaptable to rapidly-changing requirements and sowe will use an agile approach. Specifically, we will use extreme programming (XP) because we are a small team (3 people) and XP works well for dynamic requirements because of its use of test-driven development and continuous refactoring. We will complement our XP approach using CI/CD so we can merge our changes and deploy frequently to get faster feedback from the customer. As an example of why we would use XP over another agile approach, scrum is better suited for larger teams since it uses roles like the scrum master and product owner (we only have 3 people). XP's reliance on TDD can also be a drawback, since it requires writing tests, which slows the development process in the short term."