Agile Software Development Quiz Answer week one

                  Agile Software Development Quiz Answer

Week One

1.Agile Values and Principles

1.

Question 1

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

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.

It is difficult to predict user/customer needs

Projects cost too much

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.

Projects were very complex and big

2.

Question 2

What are the four values of the Agile Manifesto?

Customer Collaboration Over Contract Negotiation

People and Interaction Over Processes and tools

Responding to Change Over Following a plan

Working Software over comprehensive documentation

Planning Properly Over Just Executing

3.

Question 3

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."

Individuals and Interaction Over Process and Tools

Respond to Change Over Following a plan

Customer collaboration over contract negotiation

Working software over comprehensive documentation

4.

Question 4

Which of the following align with the agile principle:

"Business people and developers work together daily throughout the project.

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.

Business people and developers MUST meet face-to-face daily to clarify confusions, questions etc.

Business people also need to code together with developers to make faster progress.

Using Agile Methods

1.

Question 1

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

2 / 2 points

Project Visibility

Increased productivity

Increased project governance

Increased Team Morale

Improved Business / IT Alignment

Better Software Quality

2.

Question 2

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

1 / 1 point

It helps validate user needs.

It helps detect translation issues.

It helps prevent change

3.

Question 3

What new challenges does agile bring? Select two.

1 / 1 point

Very uncomfortable for leaders because of unpredictable journey

Architecture/Design/Database modeling is challenging

Agile eliminates all documentation hence makes it very difficult to use the software

Applying an Agile Mindset

1.

Question 1

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

2 / 2 points

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

Create lot of meetings to increase collaboration

Don't waste too much time in documenting, planning or designing. Focus your time on coding and implementation always.

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

2.

Question 2

If a developer says "we don't to do any discussion or upfront design" because we are agile", is he/she truely representing what agile means

1 / 1 point

Yes, because in agile, we start coding right away

No, agile does not mean start coding right away.

3.

Question 3

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

1 / 1 point

True

False

Agile Fundamentals

1.

Question 1

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

1 / 1 point

If documentation is absolutely essential then create it.

Value delivering software over writing documentation.

A manager tells the team: “Writing certain documentation is company policy so we must create them irrespective of its use.

An agile coach says to the team “Documentation is of no use.”

2.

Question 2

Which of the following are true about Agile Manifesto? (select any 2)

1 / 1 point

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

The Agile Manifesto consists of 4 values and 12 principles.

The Agile Manifesto specifies exact practices and processes that agile teams are expected to follow

Agile Manifesto was primarily based on theoretical knowledge

3.

Question 3

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

1 / 1 point

A software vendor says to a client: "We must define exactly what the user needs and put that in the agreement."

A manager e-mails her team: “Meeting face to face just for a 15 minute discussion is inefficient, let us all just dial-in from our desk.”

A manager providing a status update to a customer says: “We are done with requirements and design so we are 50% done.”

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."

4.

Question 4

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

1 / 1 point

There is not enough time spent on requirements. If we spend more time early, we can define requirements very accurately.

Difficult to understand user needs.

Sometime the market shifts from time when the requirements were originally defined.

Translation issues. Requirements are misinterpreted.

5.

Question 5

Which of the following statements align with following Agile Principle:

"Deliver working software frequently, from a couple of weeks to a couple of months, with a preference for the shorter timescale"

0 / 1 point

We MUST release software to actual users every couple weeks.

We should frequently deliver software in some environment (not necessarily to production always) to gather user/client feedback

We should NOT release software to a production environment on a shorter timeframe. We should ONLY release it in lower environment (e.g., a test environment).

6.

Question 6

Which of the following align with this principle:

" Working software is the primary measure of progress."

1 / 1 point

On a 10 month project, the team has been working for 5 months. Thus, the project is 50% complete.

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

If a team has written the requirements and done the design for 5 out of 10 stories, then the team has made some progress (they are more than 0% done)

7.

Question 7

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

1 / 1 point

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

For a project where change is not expected. requirements are well known, and the solution is both well known and repeatable.

For a project where the customer has an idea of what they want to build but is not sure of his/her exact needs.

For a project where the customer wants to build an e-commerce website but the development team has never done something like this before. Further, the company knows that they want to build an e-commerce website but are not sure about the functionality at this time.

8.

Question 8

Which of the following is true for agile projects?

1 / 1 point

An agile methodology may help a team to go to market early by delivering with limited functionality.

Agile methods do not require rework because the team knows exactly what they building. No refactoring of code is needed.

Scrum is the best way to implement agile.

If somebody says, they use an agile methodology, they must be doing either Scrum or XP.

9.

Question 9

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.

From the options below, select the ones that can help mitigate this challenge. (Select 3)

1 / 1 point

Try to define as many requirements as you can at the beginning of the project, and spend a good amount of time designing the system.

Automated Regression testing provides faster feedback which helps you detect defects quickly. This in turn, gives you confidence to make changes.

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

Keep the code clean and continuously improve/refactor the design as needed. Don't delay these changes for later.

10.

Question 10

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

1 / 1 point

No discussion sessions happen around what we want to build. We start with coding.

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.

The team does a detailed design before starting to code.

If required, the team may need to plan and conduct training, etc. for users before launching the system.

Release planning is never required on an agile project. We only plan for a day or for a week at the most.

 Agile Software Development Quiz Answer week two Ans.