PURDUE CS 307 FINAL PAPER 2026 COMPLETE
QUESTIONS AND ANSWERS
◉ Product owner. Answer: Defines the features of the product
Decides on release date and content
Prioritizes features
Adjusts features and priority every iteration, as needed
Accepts or rejects work results
◉ Scrum master. Answer: Represents management to the project
Responsible for ensuring adherence to scrum practices
Removes impediments
Ensures that the team is fully functional
Shields team from external interference
◉ Development team. Answer: Members are assumed cross-
functional
No sub-teams (testing, etc)
◉ Scrum events. Answer: Sprint
Sprint planning
,Daily scrum
Sprint review
Sprint retrospective
◉ Sprint. Answer: Usually one month or less
"Done," usable, and potentially releasable product increment is
created
Quality attributes do not change
Scope may be clarified/re-negotiated
◉ Sprint planning. Answer: Work to be performed in upcoming
sprint is planned
Suggested eight hours for a one month sprint
◉ Sprint backlog. Answer: Selected product backlog items, along
with The Plan
Organized by team
Estimate time to complete each item
Assign tasks to individual members
◉ Daily scrum. Answer: Fifteen minutes for team to "synchronize"
and plan for the next 24 hours
What has been done, what will be, roadblocks
,Held same time, same place
◉ Sprint review meeting. Answer: Development team presents
accomplishments
Form of a demo of new features or progress
Informal
◉ Sprint retrospective. Answer: Opportunity to reflect and plan for
improvements during the next sprint
◉ Sprint artifacts/documents. Answer: Project charter
Product backlog
Sprint backlog
Burn down chart
◉ Project charter. Answer: Problem statement: short and succinct
(one or two sentences)
Project objectives: what the project will achieve
Stakeholders: persons who will be actively involved with the project
Project sponsor, types of users, etc.
Deliverables: major results or services that will be produced
, ◉ Product backlog. Answer: Ordered list of everything that might be
needed in the product
Product owner is responsible for the backlog
Never complete
Lists all features, functions, requirements, enhancements, and fixes
that need to be made
"As a, I want, so that"
◉ Burndown chart. Answer: Graphical representation of work left to
do vs. time left in which to do it
◉ Domain analysis. Answer: Process by which software engineer
learns about the domain to better understand the problem
◉ Types of requirements. Answer: Real: functional and performance
Constraints: non-functional
Possible: non-measurable, subjective, political
Probably not: expectations, wishes, desires
◉ Steps to gathering and analyzing requirements. Answer:
Observation
Interviewing
Prototype
QUESTIONS AND ANSWERS
◉ Product owner. Answer: Defines the features of the product
Decides on release date and content
Prioritizes features
Adjusts features and priority every iteration, as needed
Accepts or rejects work results
◉ Scrum master. Answer: Represents management to the project
Responsible for ensuring adherence to scrum practices
Removes impediments
Ensures that the team is fully functional
Shields team from external interference
◉ Development team. Answer: Members are assumed cross-
functional
No sub-teams (testing, etc)
◉ Scrum events. Answer: Sprint
Sprint planning
,Daily scrum
Sprint review
Sprint retrospective
◉ Sprint. Answer: Usually one month or less
"Done," usable, and potentially releasable product increment is
created
Quality attributes do not change
Scope may be clarified/re-negotiated
◉ Sprint planning. Answer: Work to be performed in upcoming
sprint is planned
Suggested eight hours for a one month sprint
◉ Sprint backlog. Answer: Selected product backlog items, along
with The Plan
Organized by team
Estimate time to complete each item
Assign tasks to individual members
◉ Daily scrum. Answer: Fifteen minutes for team to "synchronize"
and plan for the next 24 hours
What has been done, what will be, roadblocks
,Held same time, same place
◉ Sprint review meeting. Answer: Development team presents
accomplishments
Form of a demo of new features or progress
Informal
◉ Sprint retrospective. Answer: Opportunity to reflect and plan for
improvements during the next sprint
◉ Sprint artifacts/documents. Answer: Project charter
Product backlog
Sprint backlog
Burn down chart
◉ Project charter. Answer: Problem statement: short and succinct
(one or two sentences)
Project objectives: what the project will achieve
Stakeholders: persons who will be actively involved with the project
Project sponsor, types of users, etc.
Deliverables: major results or services that will be produced
, ◉ Product backlog. Answer: Ordered list of everything that might be
needed in the product
Product owner is responsible for the backlog
Never complete
Lists all features, functions, requirements, enhancements, and fixes
that need to be made
"As a, I want, so that"
◉ Burndown chart. Answer: Graphical representation of work left to
do vs. time left in which to do it
◉ Domain analysis. Answer: Process by which software engineer
learns about the domain to better understand the problem
◉ Types of requirements. Answer: Real: functional and performance
Constraints: non-functional
Possible: non-measurable, subjective, political
Probably not: expectations, wishes, desires
◉ Steps to gathering and analyzing requirements. Answer:
Observation
Interviewing
Prototype
