https://www.keysurvey.com/servlet/survey.VotingSurvey;VotingRoute=x.VOTING1?

i_n_f=survey349789_pg0_totpg5_rid114765963_lqid8890705%23errQue

Agile Knowledge Survey

This quiz contains 20 questions on basic knowledge of Agile methodologies and

concepts.

What is the difference between a release and an iteration?

A release consists of many iterations
An iteration contains many releases
They are the same
They are mutually exclusive

What is the timing of when eXtreme Programming teams work on features?

Sequentially
Simultaneously
In any order
Once all the requirements are complete

Which of the following Agile practices emphasizes building releasable products in

short time periods?
Computer programming process
Iterative and incremental development
Load testing
Release planning

What is a coding methodology that is sometimes confused with Agile?

Continuous integration
Automated unit testing
Cowboy coding
Test-driven development

Of the tools listed below that are related to Planning, Monitoring, and Adapting,
which is better suited to Waterfall project management rather than Agile?
Retrospectives
Stand-up meetings
Burn-down and burn-up charts

1
 Daily status reports

What is the definition of method tailoring?

A process that determines a system development approach for a specific project
situation
A process of refactoring software functions
The way in which Waterfall methodology is adapted to Agile
A custom approach for determining milestones in a test-driven development
project

What is the underlying philosophy of the Agile Manifesto?

To complete projects before they are due
To make sure that projects come in under budget
To satisfy the customer through early and continuous delivery of valuable
software
To make sure projects are aligning to Agile processes and not concern
themselves with the successful delivery of projects

As recommended by the Agile Manifesto, how should business owners and product
developers interact?
Work together during the requirements phase and no other phases
Interact with each other only at the end of the project.
Work together daily throughout the project
Interact with the team through either e-mail or voice mail, but not in person

On an Agile project, the sponsors, developers, and users should be able to maintain
a constant pace for what time period?
For one sprint
For all sprints in the release
For three sprints
Indefinitely

In an Agile project, stakeholder engagement management is defined as:

the time after the product is launched when the stakeholders actually use the
product.
establishing and maintaining mechanisms that ensure all current and future
parties are participating in the life cycle of the project.
the individual or individuals that manage the Scrum team and sets direction for
each sprint.
the group or individuals that are developing the code for each sprint.

2
In order to enhance relationships among individual team members, an Agile project
manager should build an effective team through creating an environment of trust,
learning, collaborative decision making, and:
Mastering conflict resolution.
Fostering independent thinking.
Mentoring.
Leadership.

Burn-down is defined as which of the following?

A process in which the tasks are completed as fast as possible
An analysis tool in which the server is taken off-line for the nighttime
A process that is performed when a project is not successful
A process in which one tracks the remaining effort of work for a specific sprint

Within a daily stand-up meeting, what is NOT one of the three items that a team
member should report on?
What did I do yesterday
What am I doing today
What are my blockers
What software are we completing this sprint

Within Scrum, retrospectives are processes that primarily occur at the end of a:
sprint.
day.
quarter.
release.

With respect to a sprint, what does velocity measure?

How many sprints a team can do in a release
How much time it will take to complete a sprint
What day of the week a sprint will complete
The amount of work that a team can accomplish in a given sprint

The three main roles in a Scrum process are:

Scrum Master, product owner, team.
Scrum Master, business analyst, team.
Product owner, business analyst, team.

3
 Product owner, project manager, business analyst.

What are defined as “Chicken” roles in Scrum?

Product owner
Developers
Stakeholders and developers
Stakeholders and managers

Who defines the “Definition of Done” on a Scrum team?

Client
End user
Scrum team
Stakeholders

eXtreme Programming (XP) advocates what relationship between releases and

development cycles?

Timing of Length of
Releases Development
Cycles

Option A Frequent Short

Option B Frequent Long

Option C Singular Short

Option D Singular Long

Option A
Option B
Option C
Option D

Which of the following statements accurately portrays testing in the XP

methodology?
Testing at the end of the project is the safest way to catch all bugs
Little testing can eliminate few flaws, and a lot of testing can eliminate many
more flaws
Testing should be done only when needed and only at the end of the project

4
 Testing should not be done by developers at all until the business has looked at
the complete product

Which of these Agile project management techniques are you using in the projects
that you manage? (check all that apply)
Agile Modeling
Agile Unified Process (AUP)
Dynamic Systems Dynamic Method (DSDM)
Extreme Programming (XP)
Feature Driven Development
Lean Development
Kanban
Scrum
None of the above
Other

What percentage of your projects use Agile project management techniques?

0 - 25%
26 - 50%
51 - 75%
76 - 100%

Have you taken any Agile training courses?

No
Yes – One course
Yes – Two courses
Yes – Three or more courses

Completed:

5
Agile Knowledge Survey

This quiz contains 20 questions on basic knowledge of Agile methodologies and

concepts.

What is the difference between a release and an iteration?

A release consists of many iterations
An iteration contains many releases
They are the same
They are mutually exclusive

What is the timing of when eXtreme Programming teams work on features?

Sequentially
Simultaneously
In any order
Once all the requirements are complete

Which of the following Agile practices emphasizes building releasable products in

short time periods?
Computer programming process
Iterative and incremental development
Load testing
Release planning

What is a coding methodology that is sometimes confused with Agile?

Continuous integration
Automated unit testing
Cowboy coding
Test-driven development

Of the tools listed below that are related to Planning, Monitoring, and Adapting,
which is better suited to Waterfall project management rather than Agile?
Retrospectives
Stand-up meetings
Burn-down and burn-up charts
Daily status reports

6
What is the definition of method tailoring?
A process that determines a system development approach for a specific project
situation
A process of refactoring software functions
The way in which Waterfall methodology is adapted to Agile
A custom approach for determining milestones in a test-driven development
project

What is the underlying philosophy of the Agile Manifesto?

To complete projects before they are due
To make sure that projects come in under budget
To satisfy the customer through early and continuous delivery of valuable
software
To make sure projects are aligning to Agile processes and not concern
themselves with the successful delivery of projects

As recommended by the Agile Manifesto, how should business owners and product
developers interact?
Work together during the requirements phase and no other phases
Interact with each other only at the end of the project.
Work together daily throughout the project
Interact with the team through either e-mail or voice mail, but not in person

On an Agile project, the sponsors, developers, and users should be able to maintain
a constant pace for what time period?
For one sprint
For all sprints in the release
For three sprints
Indefinitely

In an Agile project, stakeholder engagement management is defined as:

the time after the product is launched when the stakeholders actually use the
product.
establishing and maintaining mechanisms that ensure all current and future
parties are participating in the life cycle of the project.
the individual or individuals that manage the Scrum team and sets direction for
each sprint.
the group or individuals that are developing the code for each sprint.

7
In order to enhance relationships among individual team members, an Agile project
manager should build an effective team through creating an environment of trust,
learning, collaborative decision making, and:
Mastering conflict resolution.
Fostering independent thinking.
Mentoring.
Leadership.

Burn-down is defined as which of the following?

A process in which the tasks are completed as fast as possible
An analysis tool in which the server is taken off-line for the nighttime
A process that is performed when a project is not successful
A process in which one tracks the remaining effort of work for a specific sprint

Within a daily stand-up meeting, what is NOT one of the three items that a team
member should report on?
What did I do yesterday
What am I doing today
What are my blockers
What software are we completing this sprint

Within Scrum, retrospectives are processes that primarily occur at the end of a:
sprint.
day.
quarter.
release.

With respect to a sprint, what does velocity measure?

How many sprints a team can do in a release
How much time it will take to complete a sprint
What day of the week a sprint will complete
The amount of work that a team can accomplish in a given sprint

The three main roles in a Scrum process are:

Scrum Master, product owner, team.
Scrum Master, business analyst, team.
Product owner, business analyst, team.
Product owner, project manager, business analyst.

8
What are defined as “Chicken” roles in Scrum?
Product owner
Developers
Stakeholders and developers
Stakeholders and managers

Who defines the “Definition of Done” on a Scrum team?

Client
End user
Scrum team
Stakeholders

eXtreme Programming (XP) advocates what relationship between releases and

development cycles?

Timing of Length of
Releases Development
Cycles

Option A Frequent Short

Option B Frequent Long

Option C Singular Short

Option D Singular Long

Option A
Option B
Option C
Option D

Which of the following statements accurately portrays testing in the XP

methodology?
Testing at the end of the project is the safest way to catch all bugs
Little testing can eliminate few flaws, and a lot of testing can eliminate many
more flaws
Testing should be done only when needed and only at the end of the project
Testing should not be done by developers at all until the business has looked at
the complete product

9
Which of these Agile project management techniques are you using in the projects
that you manage? (check all that apply)
Agile Modeling
Agile Unified Process (AUP)
Dynamic Systems Dynamic Method (DSDM)
Extreme Programming (XP)
Feature Driven Development
Lean Development
Kanban
Scrum
None of the above
Other

What percentage of your projects use Agile project management techniques?

0 - 25%
26 - 50%
51 - 75%
76 - 100%

Have you taken any Agile training courses?

No
Yes – One course
Yes – Two courses
Yes – Three or more courses

Completed:

10
Agile Knowledge Survey

For your reference, the questions, answers, and notes regarding the question are
below. Correct answers are in red and underlined in each question. The notes
regarding the question are in italics.

What is the difference between a release, and an iteration?

 A release consists of many iterations

 An iteration contains many releases
 They are the same
 They are mutually exclusive

Agile software development is based on iterative and incremental development. An

iteration is a quick time frame where smaller chunks of work are being complete. A
release is commonly known as something that contains many items that may have
been worked on for an extended period of time. Usually an iteration is contained
to one, two, or three weeks, at most.

What is the timing of when eXtreme Programming teams work on features?

 Sequentially
 Simultaneously
 In any order
 Once all the requirements are complete

Extreme programming is a software development methodology used within the

Agile umbrella. It advocates frequent releases in short development cycles. Within
each cycle, the development teams work on segments one by one, in a sequential
fashion.

Which of the following Agile practices emphasizes building releasable products in

short time periods?

 Computer programming process

 Iterative and incremental development
 Load testing
 Release planning

11
Iterative and incremental development is tied directly to sprints and the definition
of done. A Scrum team defines what the definition of done is for each item, which
is used to close out the work in each sprint. The iterative and incremental
development allows the team to work with the business to integrate the business
needs into the design more easily, as well as get feedback from the business team
earlier in the process.

Release planning, although a part of the Agile software development, is not focused
in the short-term duration, but in the longer-term durations. The difference of time
periods makes this answer a poor selection

What is a coding methodology that is sometimes confused with Agile?

 Continuous integration
 Automated unit testing
 Cowboy coding
 Test-driven development

Agile software development is new to many people and for those who have worked
in Waterfall or other methodologies may find it strange that all the requirements do
not have to be defined prior to a project starting. This observation makes it look
like the developers are just running off and coding whatever they want, which in
turn, makes it look like they are cowboy coding.

Of the tools listed below that are related to Planning, Monitoring, and Adapting,
which is better suited to Waterfall project management rather than Agile?

 Retrospectives
 Stand-up meetings
 Burn-down and burn-up charts
 Daily status reports

Burn-down and burn-up charts are used in Agile development, tracking each cycle
or iteration. They display the desired production as a path, and overlay the as-is
for each time segment. This allows the coach to identify gaps, or slow periods in

12
development. Retrospectives are utilized in Agile methodology to allow the team to
evaluate progress, and performance with the notion to fine-tune inconsistencies.
Stand-up meetings are used in Scrum Agile development to appraise daily progress
and for team members to coordinate with one another. Daily status reports are
different in that they merely give an update as to where you are, with no attention
towards preventing future mistakes, resource reallocation, and other things that
come with Agile.

What is the definition of method tailoring?

 A process that determines a system development approach for a specific

project situation
 A process of refactoring software functions
 The way in which Waterfall methodology is adapted to Agile
 A custom approach for determining milestones in a test-driven development
project

Potentially, almost all Agile methods are suitable for method tailoring. Being
situation appropriate can be considered as a distinguishing characteristic between
Agile methods and traditional software development methods, with the latter being
relatively much more rigid and prescriptive. The practical implication is that Agile
methods allow project teams to adapt working practices according to the needs of
individual projects.

What is the underlying philosophy of the Agile Manifesto?

 To complete projects before they are due

 To make sure that projects come in under budget
 To satisfy the customer through early and continuous delivery of
valuable software
 To make sure projects are aligning to Agile processes and not concern
themselves with the successful delivery of projects

Agile software development was implemented as a way to improve software

development and improve communication both within the team, as well as
externally between the development team and the stakeholders. Agile includes short
iterations to complete smaller work elements that allow the development team to
display their work product quicker and easier to the business to allow for faster
and earlier feedback. This allows both the business and the development team to
ensure they are developing the correct and appropriate solution to the customer.

13
As recommended by the Agile Manifesto, how should business owners and product
developers interact?

 Work together during the requirements phase and no other phases

 Interact with each other only at the end of the project.
 Work together daily throughout the project
 Interact with the team through either e-mail or voice mail but not in person

The Agile Manifesto was created in 2001. One of its core principles was that
business owners and developers have face–to-face communication and daily
cooperation. This would alleviate miscommunication and increase speed in
decision making and overall progress.

On an Agile project, the sponsors, developers, and users should be able to maintain
a constant pace for what time period?

 For one sprint

 For all sprints in the release
 For three sprints
 Indefinitely

The team maintains a constant pace throughout the project, no matter how many
Scrums there are or the length of each Scrum. The clear, open communication paths
lead to identifying problems or can show where new project segment can begin
development.

In an Agile project, stakeholder engagement management is defined as:

 the time after the product is launched when the stakeholders actually use the
product.
 establishing and maintaining mechanisms that ensure all current and
future parties are participating in the life cycle of the project.
 the individual or individuals that manage the Scrum team and sets direction
for each sprint.
 the group or individuals that are developing the code for each sprint.

Answer A is incorrect because Agile software development is all about being

transparent and integrated the stakeholders earlier in the process to allow for
adjustments or change of direction. Answers C and D define both a role within the

14
Agile / Scrum process. Answer B has to be correct because it is the only answer
other than A that is defining the process in which something is defined, not the role.

In order to enhance relationships among individual team members, an Agile project

manager should build an effective team through creating an environment of trust,
learning, collaborative decision making, and:

 Mastering conflict resolution.

 Fostering independent thinking.
 Mentoring.
 Leadership.

An Agile project manager must assist the team with any problem or resolution, if
needed. The project manager can resolve a problem from becoming a roadblock, or
by hearing and addressing the conflict. While leadership, mentoring, and
independent thinking are good qualities to possess in an Agile framework, a team-
member cannot afford to work outside the team Agile environment during an
iteration.

Burn-down is defined as which of the following?

 A process in which the tasks are completed as fast as possible

 An analysis tool in which the server is taken off-line for the nighttime
 A process that is performed when a project is not successful
 A process in which one tracks the remaining effort of work for a
specific sprint

The sprint burn-down chart is a publicly displayed chart showing remaining work
in the sprint backlog. Updated every day, it gives a simple view of the sprint
progress. It also provides quick visualizations for reference.

Within a daily stand-up meeting, what is NOT one of the three items that a team
member should report on?

 What did I do yesterday

 What am I doing today
 What are my blockers
 What software are we completing this sprint

15
The other three answers are exactly what the team member should be reporting.
What software we are completing can be discussed at the start of the next Scrum
cycle.

Within Scrum, retrospectives are processes that primarily occur at the end of a:

 sprint.
 day.
 quarter.
 release.

Retrospectives can occur at the end of any part of the software development
process. They can occur at the end of the day, the end of the quarter, or the end of
the release. The end of the quarter is probably a little unreasonable because not all
releases and sprints fall at the end of the quarter, but there is no reason why it
cannot occur then. However, within Scrum, retrospectives are most widely known
to occur at the end of each sprint. This way, if there are any changes required they
can happen sooner rather than later.

With respect to a sprint, what does velocity measure?

 How many sprints a team can do in a release

 How much time it will take to complete a sprint
 The day of the week a sprint will complete
 The amount of work that a team can accomplish in a given sprint

The other answers are important towards Scrum planning, yet measuring how
much work the team can get done in a sprint is the velocity.

The three main roles in a Scrum process are:

 Scrum Master, product owner, team.

 Scrum Master, business analyst, team.
 Product owner, business analyst, team.
 Product owner, project manager, business analyst.

A business analyst and a project manager are both part of the team and although
they are very important roles, they are not identified as key roles to the Scrum
process. Scrum Master, product owner, and the team are the three main roles, or

16
“Pig” roles on a Scrum team

What are defined as “Chicken” roles in Scrum?

 Product owner
 Developers
 Stakeholders and developers
 Stakeholders and managers

“Chicken” roles are those not a part of the actual Scrum process. They are those
for who the software is being built.

Who defines the “Definition of Done” on a Scrum team?

 Client
 End user
 Scrum team
 Stakeholders

The Scrum team controls when a Scrum is done. The DoD (Definition of Done)
writing code, coding comments, unit testing, integration testing, release notes, and
design documents all are controlled by the team, doing the work.

eXtreme Programming (XP) advocates what relationship between releases and

development cycles?

Timing of Releases Length of Development Cycles

Option A Frequent Short

Option B Frequent Long

Option C Singular Short

Option D Singular Long

17
XP is a methodology under Agile. This methodology explicitly encourages moving
faster and in shorter durations.

Which of the following statements accurately portrays testing in the XP

methodology?

 Testing at the end of the project is the safest way to catch all bugs
 Little testing can eliminate few flaws, and a lot of testing can eliminate
many more flaws
 Testing should be done only when needed and only at the end of the project
 Testing should not be done by developers at all until the business has looked
at the complete product

eXtreme Programming methodology emphasizes test-driven development that

includes numerous, thorough tests, often.

Completed:

18