The result of implementing feedback in the development process is delivering a high quality product. Feedback helps to identify issues, improve features, and align the product with user needs and expectations, ultimately leading to a better final product.
What is a result of implementing feedback in the development process?(1 point)
Responses
product failure
product failure
slowing down the product development process
slowing down the product development process
delivering high quality product
delivering high quality product
misinterpretation of project scope
11 answers
What are the characteristics of a close-knit team?(1 point)
Responses
Teams use many collaborative tools, discuss personal issues during work time, and share proprietary secrets with outside friends.
Teams use many collaborative tools, discuss personal issues during work time, and share proprietary secrets with outside friends.
Team leadership micromanages the team and provides vague task assignments to team members.
Team leadership micromanages the team and provides vague task assignments to team members.
Each team member feels a sense of belonging, freely interacts with each other, and can share ideas as well as ask questions.
Each team member feels a sense of belonging, freely interacts with each other, and can share ideas as well as ask questions.
Team members are unproductive, disagreeable, and feel a sense of pressure to maintain the status quo.
Responses
Teams use many collaborative tools, discuss personal issues during work time, and share proprietary secrets with outside friends.
Teams use many collaborative tools, discuss personal issues during work time, and share proprietary secrets with outside friends.
Team leadership micromanages the team and provides vague task assignments to team members.
Team leadership micromanages the team and provides vague task assignments to team members.
Each team member feels a sense of belonging, freely interacts with each other, and can share ideas as well as ask questions.
Each team member feels a sense of belonging, freely interacts with each other, and can share ideas as well as ask questions.
Team members are unproductive, disagreeable, and feel a sense of pressure to maintain the status quo.
The characteristics of a close-knit team are that each team member feels a sense of belonging, freely interacts with each other, and can share ideas as well as ask questions. This fosters collaboration, trust, and open communication within the team.
In pair programming, what are the responsibilities of the driver and the navigator?(1 point)
Responses
The driver reviews the code, and the navigator designs the code based on client feedback.
The driver reviews the code, and the navigator designs the code based on client feedback.
The driver assigns parts of the projects, and the navigator designs the code.
The driver assigns parts of the projects, and the navigator designs the code.
The driver writes the code, and the navigator reviews and comments on lines that need corrections as they occur.
The driver writes the code, and the navigator reviews and comments on lines that need corrections as they occur.
The navigator writes the code, and the driver comments on the lines that need corrections when they are done.
The navigator writes the code, and the driver comments on the lines that need corrections when they are done.
Responses
The driver reviews the code, and the navigator designs the code based on client feedback.
The driver reviews the code, and the navigator designs the code based on client feedback.
The driver assigns parts of the projects, and the navigator designs the code.
The driver assigns parts of the projects, and the navigator designs the code.
The driver writes the code, and the navigator reviews and comments on lines that need corrections as they occur.
The driver writes the code, and the navigator reviews and comments on lines that need corrections as they occur.
The navigator writes the code, and the driver comments on the lines that need corrections when they are done.
The navigator writes the code, and the driver comments on the lines that need corrections when they are done.
In pair programming, the responsibilities are that the driver writes the code, and the navigator reviews and comments on lines that need corrections as they occur. This collaborative approach helps ensure high code quality and facilitates knowledge sharing between team members.
Suppose a team creates a shared spreadsheet that lists all pending tasks. Each team member picks a task and moves it to a separate worksheet in the file. When that task is completed, its owner moves it to a third worksheet. The team checks in regularly to ensure work is distributed evenly and no task is held up waiting on another. Which methodology is this team using?(1 point)
Responses
extreme programming
extreme programming
scrum
scrum
waterfall
waterfall
Kanban
Responses
extreme programming
extreme programming
scrum
scrum
waterfall
waterfall
Kanban
The methodology this team is using is Kanban. Kanban focuses on visualizing work, limiting work in progress, and optimizing flow, which is evident in the use of a shared spreadsheet to manage tasks and track their progress across different stages.
What is a typical development cycle using a Version Control System (VCS)?(1 point)
Responses
Start a new branch, commit every functional version of the new feature as it is developed, send a pull request to the team and merge new features into the project.
Start a new branch, commit every functional version of the new feature as it is developed, send a pull request to the team and merge new features into the project.
Send a pull request to the team, pull a new branch, commit every functional version of the new feature as it is developed and merge new features into the project.
Send a pull request to the team, pull a new branch, commit every functional version of the new feature as it is developed and merge new features into the project.
Start a new branch, merge every functional version of the new feature as it is developed, send a pull request to the team and commit new features into the project.
Start a new branch, merge every functional version of the new feature as it is developed, send a pull request to the team and commit new features into the project.
Build a repository, upload files, publicize the project, evaluate proposed changes and merge approved changes into the project.
Responses
Start a new branch, commit every functional version of the new feature as it is developed, send a pull request to the team and merge new features into the project.
Start a new branch, commit every functional version of the new feature as it is developed, send a pull request to the team and merge new features into the project.
Send a pull request to the team, pull a new branch, commit every functional version of the new feature as it is developed and merge new features into the project.
Send a pull request to the team, pull a new branch, commit every functional version of the new feature as it is developed and merge new features into the project.
Start a new branch, merge every functional version of the new feature as it is developed, send a pull request to the team and commit new features into the project.
Start a new branch, merge every functional version of the new feature as it is developed, send a pull request to the team and commit new features into the project.
Build a repository, upload files, publicize the project, evaluate proposed changes and merge approved changes into the project.
The typical development cycle using a Version Control System (VCS) is to start a new branch, commit every functional version of the new feature as it is developed, send a pull request to the team, and merge new features into the project. This process allows for organized development and collaboration among team members.
Can legacy systems be reliable?(1 point)
Responses
Yes, legacy systems generally have a reputation for being reliable.
Yes, legacy systems generally have a reputation for being reliable.
No, legacy systems are buggy and of no use.
No, legacy systems are buggy and of no use.
Yes, legacy systems are old-fashioned which makes them reliable.
Yes, legacy systems are old-fashioned which makes them reliable.
No, legacy systems are not supported, so they are not reliable.
No, legacy systems are not supported, so they are not reliable.
Responses
Yes, legacy systems generally have a reputation for being reliable.
Yes, legacy systems generally have a reputation for being reliable.
No, legacy systems are buggy and of no use.
No, legacy systems are buggy and of no use.
Yes, legacy systems are old-fashioned which makes them reliable.
Yes, legacy systems are old-fashioned which makes them reliable.
No, legacy systems are not supported, so they are not reliable.
No, legacy systems are not supported, so they are not reliable.
Yes, legacy systems generally have a reputation for being reliable. While they may face challenges such as lack of support or difficulties integrating with modern technologies, many legacy systems have operated successfully for a long time and are trusted to perform critical tasks.
1 answer