CMIT 321 FINAL EXAM COMPLETE QUESTION
BANK WITH SOLUTIONS 2026
◉ Agile values (as stated in the manifesto). Answer: 1.Individuals
and interactions over processes and tools
2.Working software over comprehensive documentation
3.Customer collaboration over contract negotiation
4.Responding to change over following a plan
◉ Generic agile process. Answer: A project's features and bugs are
broken down into stories, requirements, and bugs (i.e. the project's
backlog, or overall goal, is broken into several iteration goals).
From there, there's a daily project meetup to which workers
describe the progress they've made on a particular story and/or the
bugs that they've encountered. They discuss what part of the
iteration they are on every two to four weeks until the next product
increment.
◉ Complexity of Problem Domain (Plan-driven or Agile). Answer:
Complex problem domains requiring input from many individuals
(tend to) lend themselves formal communications of Plan-driven
approaches
,Problem domains understood by a limited number of individuals
(tend to) lend themselves to the rapid communications of Agile
methods
◉ Solution Complexity (Plan-driven or Agile). Answer: Situations in
which the solution is architecturally complex may be better
addressed with more "up-front" modeling and planning
Situations with less complex architectures may be better addressed
with the adaptive modeling process of Agile methods
◉ Project Team Size/Location (Plan-driven or Agile). Answer: Large
or geographically dispersed teams may require the formal
communication structure of a Plan-driven approach
Small co-located teams may more easily utilize informal
communications style of Agile methods
◉ Organizational Culture (Plan-driven or Agile). Answer: Some
organizational cultures like Agile, others like Plan-driven
◉ What is Scrum?. Answer: Scrum is an agile method that provides a
framework for organizing agile projects, and provides (to some
extent) external visibility of what's going on in the project
, Team has visibility on everything, product is broken down, trust
between customers and devs is established, customers see on-time
delivery of increments.
◉ What is XP?. Answer: Requirements are expressed as scenarios
(known as user stories) and are implemented directly as a series of
tasks.
Designed for small/medium sized teams; emphasizes customer.
Based on 4 values: communication, simplicity, feedback and courage.
Programmers work in pairs and develop tests for each task before
writing code.
◉ What is RE?. Answer: Requirements Engineering is the process of
finding out, analyzing, documenting and checking these services and
constraints are for the needs of the consumer.
◉ What is a requirement?. Answer: A requirement is a "condition or
a capability needed by the user to solve a problem or achieve an
objective."
◉ What is Functional requirements?. Answer: Statements of services
the system should provide, how the system should react to
particular inputs, and how the system should behave in particular
situations.
BANK WITH SOLUTIONS 2026
◉ Agile values (as stated in the manifesto). Answer: 1.Individuals
and interactions over processes and tools
2.Working software over comprehensive documentation
3.Customer collaboration over contract negotiation
4.Responding to change over following a plan
◉ Generic agile process. Answer: A project's features and bugs are
broken down into stories, requirements, and bugs (i.e. the project's
backlog, or overall goal, is broken into several iteration goals).
From there, there's a daily project meetup to which workers
describe the progress they've made on a particular story and/or the
bugs that they've encountered. They discuss what part of the
iteration they are on every two to four weeks until the next product
increment.
◉ Complexity of Problem Domain (Plan-driven or Agile). Answer:
Complex problem domains requiring input from many individuals
(tend to) lend themselves formal communications of Plan-driven
approaches
,Problem domains understood by a limited number of individuals
(tend to) lend themselves to the rapid communications of Agile
methods
◉ Solution Complexity (Plan-driven or Agile). Answer: Situations in
which the solution is architecturally complex may be better
addressed with more "up-front" modeling and planning
Situations with less complex architectures may be better addressed
with the adaptive modeling process of Agile methods
◉ Project Team Size/Location (Plan-driven or Agile). Answer: Large
or geographically dispersed teams may require the formal
communication structure of a Plan-driven approach
Small co-located teams may more easily utilize informal
communications style of Agile methods
◉ Organizational Culture (Plan-driven or Agile). Answer: Some
organizational cultures like Agile, others like Plan-driven
◉ What is Scrum?. Answer: Scrum is an agile method that provides a
framework for organizing agile projects, and provides (to some
extent) external visibility of what's going on in the project
, Team has visibility on everything, product is broken down, trust
between customers and devs is established, customers see on-time
delivery of increments.
◉ What is XP?. Answer: Requirements are expressed as scenarios
(known as user stories) and are implemented directly as a series of
tasks.
Designed for small/medium sized teams; emphasizes customer.
Based on 4 values: communication, simplicity, feedback and courage.
Programmers work in pairs and develop tests for each task before
writing code.
◉ What is RE?. Answer: Requirements Engineering is the process of
finding out, analyzing, documenting and checking these services and
constraints are for the needs of the consumer.
◉ What is a requirement?. Answer: A requirement is a "condition or
a capability needed by the user to solve a problem or achieve an
objective."
◉ What is Functional requirements?. Answer: Statements of services
the system should provide, how the system should react to
particular inputs, and how the system should behave in particular
situations.
