Intro to Software Engineering Quiz 1 Questions and
Correct Answers | Latest Update
Agility software process Ans: - Effective response to change
- Effective communication among all stakeholders
- Drawing the customer onto the team
- Organizing a team that's in control of work performed
© 2026 Assignment
- Rapid, incremental delivery of software
A well designed _____ process "flattens" the ____ of ______ curve Ans:
Guru01 - Stuvia
Agile and Cost of change
Expert
Agile Process Ans: - Change driven model
- Driven by customer descriptions of what is required
- Customer feedback -> frequent
- Plans are short-lived
- Develops software iteratively
- "Software Increments" -> executable prototypes
- Project adapts to changes
Agility Principles Ans: - Customer satisfaction -> value through fast and
well developed software
- Req. with change and welcome changes
- Deliver software increments freq.
- Agile team -> motivated individuals w/ face to face communication
, 2 for specific request mail
- Team encourages technical excellence, good design, simplicity, and
avoids unnecessary work
Scrum Framework Ans: - ____ principles are consistent with the agile
manifesto
- Uses sprints
- Self-organizing interdisciplinary team consisting of a product owner, a
Scrum master, and a small (three to six people) development team
© 2026 Assignment
- Artifacts -> product backlog, sprint backlog, code increment
Scrum - Backlog Refinement Meeting Ans: Developers work with
Guru01 - Stuvia
stakeholders to create product backlog.
Expert
Scrum - Sprint Planning Meeting Ans: Backlog partitioned into "sprints"
derived from backlog and next sprint defined
Scrum - Daily Scrum Meeting Ans: Team members synchronize their
activities and plan work day (15 minutes max).
Scrum - Sprint Review Ans: Prototype "demos" are delivered to the
stakeholders for approval or rejection.
Scrum - Sprint Retrospective Ans: After sprint is complete, team
considers what went well and what needs improvement.
Scrum Pros Ans: - Product owner sets priorities.
- Team owns decision making.
- Documentation is lightweight.
- Supports frequent updating.
Scrum Cons Ans: - Difficult to control cost of changes
- May not be suitable for large teams