Agile Software Development Coursera Quiz Answers

Get All Weeks Agile Software Development Coursera Quiz Answers

Agile Software Development Week 01 Quiz Answers

Quiz 1: Agile Values and Principles

Q1. What are some of the challenges with waterfall methods that prompted the software industry to come up with alternatives like agile? Select three.

View
Incorrect interpretations of requirements by developers go undetected for a long time. During user acceptance tests, these issues are discovered but it is very late.

Integration issues between different components of the software go undetected for a long time. During the testing phase, when all the components are integrated, these issues are discovered but it is very late in the process.
It is difficult to predict user/customer needs

Q2. What are the four values of the Agile Manifesto?

View
Responding to Change Over Following a plan

Customer Collaboration Over Contract Negotiation

People and Interaction Over Processes and Tools

Working Software over comprehensive documentation

Q3. Which Agile Value does the following principle align with:

“Build projects around motivated individuals, give them the environment and support they need, and trust them to get the job done.”

View
Individuals and Interaction Over Process and Tools

Q4. Which of the following aligns with the agile principle:

“Business people and developers work together daily throughout the project.”

View
Since agile methodologies do not recommend writing all detailed requirements upfront, it is really important to support greater collaboration between business people and developers so that they can build a shared understanding of what needs to be built.

Quiz 2: Using Agile Methods

Q1. What are some of the benefits organizations have seen from using agile methods? Select five.

View
Increased Team Morale

Improved Business / IT Alignment

Better Software Quality
Project Visibility

Increased productivity

Q2. The agile principle of “Deliver working software frequently” helps with which of the following challenges of the predictive model? Select two.

View
It helps validate user needs.

It helps detect translation issues.

Q3. What new challenges does agile bring? Select two.

View
Very uncomfortable for leaders because of the unpredictable journey

Architecture/Design/Database modeling is challenging

Quiz 3: Applying an Agile Mindset

Q1. What are some of the tactics/concepts you can use to implement an agile mindset? Choose two.

View
To keep the cost of change down, use engineering practices like automated tests, continuous integration, incremental design

Build in small bite-sized chunks. These chunks could represent both iterative and incremental approaches

Q2. If a developer says “We don’t do any discussion or upfront design” because we are agile”, is he/she truly representing what agile means

View
No, agile does not mean starting coding right away.

Q3. When applying agile, we don’t need to do any release planning.. We only plan for a week.

View
False

Quiz 4: Agile Fundamentals

Q1. Which of the following statements align with the value of “Working software over comprehensive documentation” of the Agile manifesto?

View
If documentation is absolutely essential then create it.
Value delivering software over writing documentation.

Q2. Which of the following is true about the Agile Manifesto? (select any 2)

View
The Agile Manifesto consists of 4 values and 12 principles.

The Agile Manifesto is a work in progress and we are continuing to learn.

Q3. Which one of the following statements/situations/conversations align with an agile mindset?

View
Manager: “The customer is suggesting another change in feature X which is complete according to the specification. They agree that it was built as we agreed upon but it lacks some functionality and will result in user frustration. Should we implement the change or not?”

Developer: “Yes, if it does not fulfill user needs, we should make the change.

Q4. Why is it difficult to predict user needs and requirements? (select any 3)

View
Difficult to understand user needs.

Translation issues. Requirements are misinterpreted.

Q5. Which of the following statements align with following Agile Principle:

View
“Deliver working software frequently, from a couple of weeks to a couple of months, with a preference for the shorter timescale”
We should frequently deliver software in some environment (not necessarily to production always) to gather user/client feedback

Q6. Which of the following aligns with this principle:

” Working software is the primary measure of progress.”

View
If a team has delivered 5 features out of 10 features (or stories), the team has made progress (they are more than 0% done)

Q7. In which of the following situations, would you NOT recommend using an agile process?

View
For a project where requirements are well known but the technology and solution are unknown (i.e., changes expected in the solution).

Q8. Which of the following is true for agile projects?

View
If somebody says, they use an agile methodology, they must be doing either Scrum or XP.
An agile methodology may help a team to go to market early by delivering with limited functionality.

Q9. One of the core principles of agile is to “Embrace Change”. This makes architecting and designing the system challenging since you don’t know all of the requirements upfront. Thus, you have to be prepared to make architecture and design changes. To effectively embrace change, agile teams must learn how to keep the cost of change low.

View
Keep the design simple and just build what is required. It is easier to change a simple design than to update a complicated design.

Automated Regression testing provides faster feedback which helps you detect defects quickly. This in turn, gives you confidence to make changes.
Keep the code clean and continuously improve/refactor the design as needed. Don’t delay these changes for later.

Q10. Which of the following is true for a typical agile project? (select 2)

View
The team talks about the high-level software architecture/design as well as their approach for building software (the release plan) before directly jumping into coding.
If required, the team may need to plan and conduct training, etc. for users before launching the system.

Agile Software Development Week 02 Quiz Answers

Quiz 1: User Stories

Q1. What of the following are the qualities of a good user story as mentioned in the INVEST model? Choose three.

View
Independent: Dependencies among stories should be minimized
Valuable: Stories should be valuable to the user
Testable: Once the story is implemented, we should be able to test that it is done

Q2. What issues do you see in the following story?

View
This story breaks the quality of negotiable.

As a grocery buyer, I want to see different food items in different colors: red for meats, brown for grains, and green for vegetables so that i can identify food items by type.

Q3. What are the 3 Cs of user stories?

View
Confirmation

Conversation

Card

Q4. What are some of the key parts of a user story? Choose four.

View
Who is it for? What does the user want to do? Why does the user want to do that?
The estimated development time
Acceptance tests
The story title

Q5. Which of the following statements are true about “Spike” stories? Choose three.

View
It is recommended that these stories have well-defined acceptance criteria so that the team knows what is expected at the end of the exploration.
Spike stories are time-boxed.

They can be used for knowledge acquisition.

Quiz 2: Gathering User Needs

Q1. The goal of a story writing workshop is to:

View
Write as many user stories as possible under the themes identified.

Q2. What are some of the valid ways to handle non-functional requirements in agile development? Select two.

View
Create specific stories that outline the non-functional needs with clear acceptance criteria.

Add non-functional requirements to the definition of done for all stories.

Q3. Which of the following are true about story writing workshops? Select two.

View
The whole team (including the product owner, the scrum master, and the development team) participates in the story-writing workshop.
A story-writing workshop can take anywhere between a few hours to a few days.

Q4. What are some of the ways a story map can help software development? Select all that apply.

View
It helps discover user needs.

It helps plan releases and work.

It organizes and prioritizes the story backlog.

It builds a shared understanding among team members.

It helps communicate user needs with the stakeholders and get feedback.

Q5. What are some of the activities you expect to see in a story mapping exercise? Select three.

View
Find variations in the paths the user can take through the system.

Find gaps in the story map by walking through the user experience (as expressed in the activities/tasks) aloud.

Plan releases/journeys.

Q6. What are the characteristics of a good product backlog? (Select any 4)

View
Estimated

Prioritized

Detailed appropriately

Emergent

Quiz 3: Agile Estimation

Q1. Who estimates the effort to complete a product backlog item (a user story)?

View
The scrum development team after clarifying the requirement.

Q2. What is true about Agile Estimation techniques? Select two.

View
Estimates are shared.

They estimate effort and not duration.

Q3. Which of the following estimates represents concept of relative sizing? Select three.

View
Story A is 1 apple, Story B is 5 apples, and Story C is 10 apples
Story A will take half the time Story B will take. Story C will take double the time Story A will take.
Story A is bigger than Story B. Story C is smaller than Story A.

Q4. What is true about the planning poker estimation technique? Select three.

View
It helps uncover misunderstandings.

It supports the concept of shared estimates.

Everyone involved in development has to participate in estimation.

Q5. Which of the following observations are true about Card Sorting? Select two.

View
This technique benefits from using relative sizing.
It is very useful for estimating a large number of stories.

Q6. What is true about estimation using Ideal Days? Select two.

View
It has a potential issue of “My ideal days are not your ideal days”.
It is very natural for a new team member to understand.

Quiz 4: Release Planning and Tracking

Q1. Calculate the velocity range a team should use to select work for next iteration based on their past velocities (see chart below). The team uses the last 5 iterations to estimate their velocity. Use the format “from-to” to specify the answer (e.g., 0-100).

Table 1: The velocity of previous iterations

IterationStory points completed
114
218
323
417
515
621
722
820
View
Use the format “from-to” to specify the answer (e.g., 0-100).

Q2. A team was doing release planning and they decided that the next release will include all stories from Story 1 to Story 11 (see table 2 below).

View
The velocity range to be used for the release planning is 15-22.

The team works in a 2-week iteration.

It costs about $50,000 per iteration to fund the entire team

Calculate the estimated duration for the next release. Additionally, how much will this release cost?

Table 2: Prioritized Product Backlog

Story TitleEstimate (in ideal days)
Story 15
Story 25
Story 38
Story 43
Story 55
Story 65
Story 73
Story 85
Story 98
Story 108
Story 113
Story 123
Story 133
Story 145
Story 158
Story 163
Story 175
Story 185
Story 198
Story 208
View
Duration: 6-8 weeks, Cost: 150K to 200K

Q3. Select scenarios below where the team used the correct approach to handle special cases of team velocity.

View
To forecast velocity for the first iteration,
1) the team builds a deeper understanding of a few stories from the backlog
2) From the understood stories, they select stories they feel they can get done in one sprint.
3) The sum of the estimates of the selected stories is the team’s forecasted velocity.

Q4. Which of the following methods can help you track a release? (select any 2)

View
A cumulative flow diagram for a release

A release burn-up chart

Quiz 5: Requirements and Planning

Q1. What is true about user stories in Agile Software Development? (Select any 3)

View
User stories are used to plan, design, describe, build, and validate your product.
Stories can be written at different levels, refined, and split into smaller stories as you move from vague ideas to implemented software.
User stories are tokens for conversations.

Q2. What are some of the benefits of writing acceptance tests for a story? (select 4)

View
They help build a common understanding between team members.
They make sure the story is easy to develop.
They can potentially help you split stories if required.
They help the product owner (who is writing the story) think through the user’s needs.

Q3. What is wrong with the following story? (Select any 2)

“As a product owner, I want a list of highly-rated restaurants on the brochure.”

View
It doesn’t specify the value of the story (the “why” is missing).

The user who benefits from this story is missing (the “who” is missing).

Q4. What is wrong with the following user story? (Select any 2)

View
No valid user is identified.

The story is very big.

The story is not valuable.

Q5. How is gathering user needs/requirements different on an agile project? (select any 3)

View
At any given time, the level of detail may be different for different parts of the software.

The agile way supports progressive refinement—defining the right level of detail at the right time.

Agile encourages conversations as a key method for building a shared understanding.

Q6. What are some of the activities that happen during a User Story Writing Workshop? (Select any 4)

View
To generate stories, one of the options is to start from the top down or bottom up.

Everybody silently writes user stories around a theme

User role analysis and defining personas

Sometimes, you keep it free-form for people to write stories and later group them by theme.

Q7. Which of the following is true about the Story Mapping technique? (select 3)

View
The horizontal axis (moving from left to right) in a story map represents time.

The vertical axis (moving from top to bottom) in a story map represents rough priority.

One story map can only have one user. It is not recommended to have multiple users on the same story map.
It is a user-centric approach where we map out the system from a user’s perspective.

Q8. Due to an unpredictable market event, the Product Owner (PO) asked the team to complete the next release in 6 weeks. Assuming the backlog in Table 2 is up to date and prioritized from highest to lowest, the Product Owner wants you to estimate what can be done in next 6 weeks. Describe 1) what can be done, 2) what might be done, and 3) what will not be done.

The velocity range to be used for the release planning is 15-22.

The team works in 2 week iteration.

Table 2: Prioritized Product Backlog

Story TitleEstimate (in ideal days)
Story 15
Story 25
Story 38
Story 43
Story 55
Story 65
Story 73
Story 85
Story 98
Story 108
Story 113
Story 123
Story 133
Story 145
Story 158
Story 163
Story 175
Story 185
Story 198
Story 208
View
Most likely: Story 1 to Story 8; Might Be Done: Story 9 to Story 13; Not likely: Rest of the stories

Q9. What is true about planning with an agile mindset? (Select any 2)

View
Plan just enough, just in time.

Use Adaptive Planning.

Q10. What do we mean by Velocity in agile terms?

View
It is calculated at the team level and represents how much work a team can get done in an iteration.

Agile Software Development Week 03 Quiz Answers

Quiz 1: Scrum Overview

Q1. Which of the following are official rituals/meetings/practices in scrum? Select four.

View
Sprint Review Meeting

Sprint Retrospective Meeting

Sprint Planning Meeting

Daily Scrum Meeting

Q2. What are the three roles in Scrum?

View
The Team
Scrum Master
Product Owner

Q3. Who prioritizes the work in Scrum?

View
Product Owner

Q4. What artifacts are defined as part of Scrum framework? Select two.

View
Product Backlog

Sprint Backlog

Quiz 2: Sprint Planning and Tracking

Q1. In Scrum, when is the sprint backlog created?

View
During the sprint planning meeting

Q2. In Scrum, how is the Product Backlog arranged?

View
Most important items at the top, least important items at the bottom.

Q3. In which artifact is the customer requirements stored?

View
In the Product Backlog

Q4. What is usually plotted on the x-axis of the Sprint Burndown Chart?

View
Days of the sprint

Q5. What is a Sprint Burndown Chart?

View
A chart showing the trend of work remaining across time in a sprint.

Q6. Your team is planning out the next sprint. You’ve chosen to fill the sprint by taking stories in priority order from the product backlog and stopping when you reach the first story that won’t fit in the sprint.

Based on following details, which stories should the team commit to for a sprint?

Table 1: Prioritized story with estimated story points and total estimate in hrs of tasks for that story.

StoryStory PointsTotal of Tasks Estimates
Story 1516 hrs
Story 2816 hrs
Story 3524 hrs
Story 4316 hrs
Story 51332 hrs
Story 6826 hrs
Story 758 hrs
Story 8815 hrs
Story 9512 hrs

Table 2: Capacity of Team members for given sprint

Name# days availableHours / dayCapacity (hrs) You compute this
John34-5
Matt52-3
Sally54-5
Ram52-3
View
Story 1, Story 2, and Story 3

Quiz 3: Sprint Review, Retrospective and Execution

Q1. During sprint execution, when are new tasks added to the sprint?

View
As soon as possible after they are identified, unless they reflect a scope change in the sprint goals.

Q2. Who should attend the sprint retrospective?

View
All team members.

Q3. How long should the Daily Standup be?

View
Short fixed duration (most commonly 15 min).

Q4. Which of the following are discussed in a sprint retrospective? Select three.

View
What’s working?

What’s not working?

New action items / What can we do better?

.

Quiz 4: Scrum

Q1. Which of the following is true about Scrum?

View
Burn-down and Burn-up charts help the team track the progress of the current sprint.

Q2. Which of the following is TRUE about Scrum? (Select two)

View
Scrum is an adaptive model.

Scrum has fixed, time-boxed development cycles called sprints.

Q3. You are a developer on a scrum team. Your scrum master invited you to attend a sprint planning meeting. Which of the following activities would you expect in that meeting?

View
The developers/testers ask questions to understand the stories.

The team will select the stories to work on for the next iteration (sprint).

Either during the meeting or afterward, developers create tasks to further solidify what work needs to be done and make final a work commitment for the sprint.

The product owner (or equivalent) shares the top priority stories for the sprint.

Q4. You need to calculate a team member’s capacity for an iteration. Which of the following activities should be EXCLUDED from the committed capacity of the team member?

View
Paid time off (PTO)

Organizational Meetings

Q5. What should happen in the sprint review meeting?

View
A potentially shippable product increment is demonstrated live.

Q6. The CEO asks a team member to do some work outside the goals of the current sprint in progress. What should the team member do?

View
Inform the product owner so he can work with the CEO and if it is still necessary to get this work done in the current sprint, it should be discussed with in the team.

Q7. When is a sprint complete?

View
When all committed product backlog items meet their definition of done.

Q8. Which of the following are the goals of the daily stand-up meeting?

View
Share status information.
Identify impediments.

Q9. Which of the following is true about Sprint Reviews?

View
Individual team members should be encouraged to demo the work they did.

The Sprint Review should be done every week even if your sprint duration is 3 weeks or longer.

Q10. Which of the following statements are true about the Sprint Retrospective? (select all that apply)

View
Team members should avoid blaming (finger pointing) other team members in the retrospective.

Quiz 5: XP

Q1. Which of the following is the right sequence when developing software using the XP practice of Test First Programming?

View
Make sure the test fails

Write enough code so the test passes

Refactor as necessary

Q2. Which XP practice prescribes that “the code [always be] written by two programmers at one machine”?

View
Pair Programming

Q3. Which of the following are primary practices prescribed by XP?

View
Whole Team
Continuous Integration
Pair Programming

Q4. One of the practices of XP is “Whole Team”. Which of the following statements align with its meaning?

View
All the skills necessary to deliver the software product should be present on the team.
The whole team should be working together to meet the team’s commitment

Q5. If an XP team cannot provide an estimate for a story, what should they do to gain a better understanding of the story?

View
Create a spike story—a new story under which the team will do some research or other work to gain a better understanding of the original story.

Q6. According to XP’s principles, what should you do when a story’s acceptance test fails?

View
As a team, update the acceptance test so the test passes.

Q7. What activities occur as part of XP’s “Weekly Planning” practice?

View
Reviewing the previous week’s progress.
Selecting the next week’s work.

Q8. According to the concept of “Whole Team”, which of the following statements are true?

View
All of the skills the team needs to be successful should be in the team.

If the team finds out that they need a particular skill in the team, they can add a person with that skill to the team.

Q9. An XP team is getting feedback more frequently than they can handle. What should they do?

View
Slow down the frequency of feedback.

Q10. Which of the following statements are true about the XP value of “Simplicity”?

View
Select the simplest design that could work.

Get All Course Quiz Answers of Software Development Lifecycle Specialization

Software Development Processes and Methodologies Quiz Answers

Agile Software Development Coursera Quiz Answers

Lean Software Development Coursera Quiz Answers

Team Networking Funda
Team Networking Funda

We are Team Networking Funda, a group of passionate authors and networking enthusiasts committed to sharing our expertise and experiences in networking and team building. With backgrounds in Data Science, Information Technology, Health, and Business Marketing, we bring diverse perspectives and insights to help you navigate the challenges and opportunities of professional networking and teamwork.

Leave a Reply

Your email address will not be published. Required fields are marked *