AGILE FOUNDATION CERTIFICATE

SAMPLE FOUNDATION QUESTIONS WITH ANSWERS

This document is a set of sample questions, in the style of the Agile Foundation
Certificate Examination, which is a 60 question, 1 hour, multiple choice paper.
The areas specifically targeted are:

Customer and Stakeholder Involvement

Feedback and Adaptation
Handling Team Dynamics
Individual Leadership Style
Leadership Skills
Prioritisation, Planning and Delivery
Tailoring

The style is: a statement or question followed by four options. In each case
only one option is correct.
The examination covers, as generically as possible, all popular Agile
approaches. Occasionally, language and terms used will be specific to one
approach. The candidate should read widely about Agile to become familiar
with the terminology.
Correct answers are emboldened in the sample below.

340831658.doc

22 December 2016

Sample Agile Foundation Examination Questions:

1. Which of the following best describes the approach for determining the
iteration (timebox) length?
A.
B.
C.
D.

Iterations (Timeboxes) should always be 30 days

The team determines iteration (timebox) length by dividing the total
number of story points by the average velocity of the team
Iterations (Timeboxes) should always be two weeks
The team should agree on the length of the iteration (Timebox),
taking the size and complexity of the project into consideration

2. Which of the following is a characteristic of an Agile leader?

A.
B.
C.
D.

Task focused
Process oriented
Supportive
Disengaged

3. Who is responsible for prioritising the product backlog?

A.
B.
C.
D.

Product Owner
Project Manager
Lead Developer
Business Analyst

4. What are the advantages of maintaining consistent iteration (Timebox)

length throughout the project?
A.
B.
C.
D.

It helps to establish a consistent pattern of delivery

It helps the team to objectively measure progress
It provides a consistent means of measuring team velocity
All of the above

5. Tracking project issues in an Agile project is the primary responsibility of

the
A.
B.
C.
D.

Tester
Project Leader
Functional Manager
Developer

340831658.doc

22 December 2016

6. Why is it important to trust the team?

A.
High trust teams do not have to be accountable to each other
B.
High trust teams do not require a user representative
C.
The Project Manager does not then have to keep a project schedule
D.
The presence of trust is positively correlated with the team
performance
7. An effective workshop facilitator will always ...
A.
B.
C.
D.

Involve the whole project team in all project workshops

Agree the process and participants of the workshop with the
workshop owner before the workshop
Involve only those team members who will commit to doing further work
after the workshop
Act as a proxy for any invited participant who is unable to attend the
workshop on the day

8. Which of the following best represents the Agile approach to planning?

A.
Planning is not part of an Agile approach, because Agile is exploratory
B.
Planning should be done in detail at the outset of a project and not
revisited
C.
Planning should involve the whole team, not just the Project
Manager
D.
Planning should all be done by the Project Manager
9. Who should define the business value of a Feature within an Agile project?
A.
B.
C.
D.

The individual end-users

The Product Owner
The Business Analyst
The Business Sponsor

10. If a Timebox (iteration) plan needs to be reprioritised in a hurry, who should

re-prioritise?
A.
B.
C.
D.

The developers alone (they know what the customer wants)

The Product Owner (the developers would only choose the easy things as
top priority)
The Project Leader (they can give an independent, pragmatic view)
The whole team including Product Owner and developers
(together they can consider both business value and practicality)

340831658.doc

22 December 2016

11. What is the effect of having a large visible project plan on a wall?
A.
B.
C.
D.

It removes the need to create any other reports for management

It continuously communicates progress within the team and to
other stakeholders
It allows the Project Manager to allocate tasks to specific team members
It is restrictive, as it does not allow the team to innovate and change

12. How should work be allocated to the team in an Agile project?

A.
B.
C.
D.

The Team Leader (Scrum Master) should allocate specific tasks to

individuals
Tasks should be randomly allocated to team members, using Planning
Poker
Team members should self-select tasks appropriate to their skills
The most complex tasks should be allocated by the Team Leader (Scrum
Master)

13. What should the developers do if the customer representative is repeatedly

too busy to be available?
A.
B.
C.
D.

Continue the work, record the assumptions and ask the customer later for
input.
Send the customer a written warning that the end product will be
completed on time, but may not meet their needs
Allow the Business Analyst to take on the role of Proxy Customer
Representative
Draw the problem to the attention of the Scrum Master (Team
Leader)

14. Which one of the following is a key feature of documentation that you
would expect to find in an Agile project?
A.
B.
C.
D.

System documentation created at the end of each increment, at the start

of the deployment
User Stories held in a spreadsheet or specialist database, where full
details of user conversations are recorded for future purposes, like
handover to maintenance or support
User Story cards containing only enough detail for planning and
development, which will need to be supplemented by further
face-to-face conversations
No written documentation, as all good communication is face-to-face

15. When handling team dynamics, the Agile Leader should

A
B.
C.

Empower the team members, within appropriate limits

Encourage an environment of competition and personal advantage
Give clear directives to the team about what they should do and how

340831658.doc

22 December 2016

D.
Expect team members to be proactive and each work to their own
priorities and objectives

340831658.doc

22 December 2016

16. Which one of the following statements is correct regarding acceptance of

any deliverables on an Agile Project?
A.
B.
C.
D.

The team should allow only senior managers to sign off deliverables
The team should get acceptance of project deliverables from the
appropriate stakeholders at least at the end of every timebox /
iteration
The team should get acceptance of project deliverables from the users
during a UAT phase at the end of the project
Acceptance of any particular deliverable on the project is gained from all
stakeholders at the same time.

17. Which one of the following statements is correct regarding quality of

deliverables from an Agile Project?
A.
B.
C.
D.

The products produced by an Agile project should be cheaper than those

produced by any other approach, but quality will suffer
The products will be more expensive than by any other approach but will
be top quality
The products will be fit for purpose, but may not do what the customer
wanted
The products will be of appropriate quality, as guided by the
customer representative involved throughout the development
process

18. What is the Agile approach to doing design early in a project?

A.
B.
C.
D.

A big design up front is always a good idea

Just enough design up front gives a good foundation to start
from and helps to mitigate risk, without wasting unnecessarily
time
No design up front is the best approach as most of the fun of a project is
in discovery of the unexpected
Design has no place in an Agile project

19. An Agile approach advocates which of the following approaches?

A.
B.
C.
D.

Get something quick and dirty delivered, to save time

Get something simple released as quickly as possible
Get something business-valuable delivered as quickly as
possible, consistent with the right level of quality
Get something delivered once it has been fully documented and the
documentation has been signed off as complete

20. Which of these best describes the Agile approach to team-working?

A.
B.
C.

The team should plan to work a small amount of overtime regularly

throughout the project
The team should expect to work longer hours towards the end of the
sprint (Timebox), in order to deliver all that was committed to
The team should strive for a sustainable pace and a normal
working week

340831658.doc

22 December 2016

D.

The team will burn out if they have to work overtime for more than two
sprints (Timeboxes, iterations) in a row

21. Which one of the following statements about workshops is true for Agile
projects?
A.
B.
C.
D.

All project stakeholders should attend requirements workshops

Retrospectives are only run at the end of a project
It is best if the Project Manager facilitates the projects workshops
An independent facilitator will manage the structure of a
facilitated workshop but not input to the content

22. Which one of the following is an important feature of the daily stand-up /
wash up / Scrum meeting?
A.

Everyone is expected to stand for the whole time, to keep the meeting
short
The meeting must be kept short and well structured
The meeting should ensure that it is clear to all which team members are
not performing
No-one is allowed to leave the stand-up meeting until all problems raised
have been solved

B.
C.
D.

23. Who should attend the stand-up meetings?

A.
B.
C.
D.

Sponsor and Executive Management only

Project Manager and Technical Leads only
Project Leader and Customer Representatives only
The entire team

24. One of the development stages you would expect to see a team go through
is:
A.
B.
C.
D.

Storming
Warming
Cloning
Yawning

25. When estimating is done for a project, the developers should:

A.
B.
C.
D.

Be fully involved in the estimating process

Be in total control of the estimating process
Be consulted after the Team Leader (Scrum Master) has made the
estimates for the teams work
Not make estimates unless velocity is already known

26. During an iteration (sprint) (Timebox) the developers should be:

A.

Able to contact the customer to clarify aspects of the work

340831658.doc

22 December 2016

B.
C.
D.

Completely uninterrupted by the customer

In twice-daily contact with the customer
Able to work without needing to disturb the customer

27. The end result of an Agile development is:

A.
A product of a professional quality which fits the business need
B.
A product of almost as good a quality as a Waterfall development
C.
A product which is barely sufficient for its purpose and deliberately not
maintainable
D.
A technically-perfect, re-factored solution
28. An Agile customer
A.
Must have a thorough understanding of Agile techniques, for Agile to
work
B.
Will always receive lower-quality products than their non-Agile
counterparts
C.
Will typically get business value delivered early and often
D.
Will need to understand the technical aspects of development, to
contribute effectively
29. An Agile team
A.
B.
C.
D.

Is self-organising, with each member having the same technical skills

Collaborates and supports its team members
Ensures that weak members of the team are allocated the simpler tasks
Ensures blame is allocated fairly

30. The Agile process

A.
B.
C.
D.

Encourages the team to meet regularly

Has no meetings
Has lengthy reporting requirements
Has no reporting requirements

31. The Agile Leader

A.
Should allocate tasks to the team members each day at the stand-up
meeting
B.
Should involve the team in their own work-allocation
C.
Should give detailed work-plans to the team each day
D.
Should direct the work of the team, if they are inexperienced
32. What is Kan Ban?
A.

A list of activities banned by the team, in relation to Team Norms

340831658.doc

22 December 2016

B.
C.
D.

The set of Can Have stories for a project

A visible chart of work to do, work in progress and work done
A graph of tasks partially-completed by the team

33. What is meant by Yesterdays Weather in an Agile project?

A.
Teams work less well when it rains
B.
Keeping metrics of earlier work to help with future estimates
C.
Retrospectives should include less important topics, such as the weather,
as ice-breakers
D.
Estimating is as futile as predicting the weather
34. In Agile projects, we plan to learn as we go because
A.
It creates a better relationship between the developers and customer
representatives
B.
Many projects are evolutionary, and a better solution emerges
this way
C.
It is time-consuming to analyse everything at the beginning of a project
D.
It prevents late delivery of the project
35. The recommended approach to design in an Agile project is:
A.
B.
C.
D.

No design up front
Big design up front
Just enough design up front
Use a previous design it will be good enough

36. What is the personal risk that an Agile Leader takes in empowering the
team?
A.
B.
C.
D.

The Agile Leader might lose their job, as the team is doing all the work
If the team fails, the Agile leader will not get a performance bonus
The Agile Leader has less direct control over the teams work,
but still has the responsibility for their outcomes
The Agile Leader cannot share the glory of team success

37. The Agile approach to documentation is:

A.
B.
C.
and
D.

Do no documentation because it is a waste of time

Do sufficient documentation to prove you have done a good job
Do the necessary documentation to support the development
use of the product
Do more documentation than usual, because Agile is risky

340831658.doc

22 December 2016

38. The Agile way is:

A.
To produce working product of the right quality, early and
incrementally
B.
To produce working product after documentation has been signed off
C.
To produce simple prototypes early, but no finished product until the end
of the project
D.
To produce products without technical integrity, but re-engineer later

340831658.doc

10

22 December 2016

39. The customer in an Agile project .

A.
B.
C.
D.

Has no control over the prioritisation of delivered features

Has total control over the prioritisation of features
Collaborates with the developers over prioritisation of features, but the
developers have the final decision
Collaborates with the developers over prioritisation of features,
but the business has the final decision

40. In the popular prioritisation technique called MoSCoW, the M stands for
...
A.
B.
C.
D.

May have
Major
Must Have
Mandatory

41. The working culture of an Agile team is

A.
B.
C.
D.

Collective
Collaborative
Connective
Contemplative

42. The leadership style of an Agile Leader is

A.
B.
C.
D.

Directive
Assertive
Facilitative
Feature-based

43. The Agile Manifesto states the following values:

A.
People are more important than contracts
B.
Working software should have priority over comprehensive
documentation
C.
Plans should have priority over ability to respond
D.
Contracts should be negotiated which allow control over the people
44. Which of the following are attributes of an Agile team?
A.
B.
C.
D.

Courage to change and adapt

Trust of fellow team members to do the work
Responsiveness to change
All of these

45. A sustainable pace means

340831658.doc

11

22 December 2016

A.
B.
do
C.
D.

If the team members work long hours regularly they will get used to it,
and be able to sustain it
A 40 hour week is only for the weaker members of the team. Others can
more.
The team should establish a velocity which can be sustained
within normal working hours
Working long hours is the only way to deliver on time

46. A burn-down chart shows

A.
The energy level and velocity of the team
B.
The remaining work (effort, points) to complete before the
iteration (Timebox) end
C.
The number of hours worked by each team member during the iteration
(Timebox)
D.
The rate of spending of the budget for a project
47. The reason for holding regular Retrospectives is:
A.
It allows the team to take a necessary break from work
B.
It gives management information to use in team members performance
reviews
C.
It allows learning which can be used to improve team
performance during the project
D.
It prevents deviation from the process which the team has been following
48. Once a project is underway, the approach to planning is:
A.
B.
C.
D.

Plans should never be changed

It is normal to need to plan and re-plan as the project progresses
Plans should only be changed with full approval of all stakeholders
Plans are not required as Agile is incremental

49. An Agile project

A.
B.
C.
D.

Should have no control over its progress

Should be able to demonstrate control of its progress
Is always out of control
Is controlled by the velocity of the most junior team member

50. An Agile project should have ...

A.
Occasional early deliveries, if the business is prepared to accept lower
quality
B.
A regular pattern of delivery of developer-focused products
C.
A regular pattern of delivery of business-valued increments
D.
An irregular and unpredictable delivery of products
340831658.doc

12

22 December 2016

340831658.doc

13

22 December 2016

51. When an Agile team is successful

A.
It should be encouraged to celebrate success only when the project is
over
B.
It should be encouraged to celebrate even small successes
immediately
C.
It should not celebrate success, as this wastes project budget
D.
It should not celebrate success, as this makes less successful teams feel
bad
52. In order to communicate well, the Agile project should ...
A.
B.
C.
D.

Keep team-size large, to avoid stakeholders feeling left out

Break the project into small, mixed-skill, self-organising teams
Operate with one team of less than 10 people
Operate with separate customer, developer and test teams

53. If a new requirement emerges once an Agile project is running, it should

be:
A.
B.
C.
D.

Automatically included in the work of the project

Automatically excluded and left until a later project or increment
Assessed for importance and, if sufficiently important to the
business, included in the project, displacing less important
requirements
Put on the backlog for consideration by the wider group of stakeholders
after the project has been completed

54 . You have been engaged as the Technical Coordinator in a product

development team. The customer (Product Owner) and Team Leader
(Scrum Master) are happy because the team always delivers business value
on time. However, you worry that the technical debt is increasing. What
would be your primary goal to ensure the right quality?
A.
B.
C.
D.

Ensure testers define their entry criteria for quality, which they impose on
the development team
Nothing. Prescribed roles such as technical coordinators are not part of an
Agile team
Make sure that the maintainability quality attribute is addressed
On time delivery and happy end users are the only quality measures in
Agile development

55. How could maintainability of the developing product be improved in a

development team?
A.
B.
C.

Apply standard design patterns

All of these
Make refactoring a common practice

340831658.doc

14

22 December 2016

D.

Ensure unit testing is included in the done criteria

340831658.doc

15

22 December 2016

56. Agile methods are described as adaptive because

A.

Agile teams have the empowerment to frequently respond to

change and to learn on a project by changing the plan
The rate of development progress on an Agile project is constantly
tracked to allow adaptation
Project Managers are not needed in Agile methods because teams are
self-organising
Workshops held at the beginning and the end of every iteration (Timebox)
allow the team to adapt the product specification

B.
C.
D.

57. What do all Agile approaches have in common?

A.
B.
C.
D.

A prescribed, fixed iteration (Timebox) length

Iterative development and incremental delivery
A strict focus on on-time delivery
A large set of clearly defined roles

58. What is one difference in responsibility between a Project Manager and a

Scrum Master (Team Leader) in an Agile project?
A.
B.
C.
D.
case.

None. It's basically the same. Scrum Master (or Team Leader) is just a
better term than Project Manager in an Agile project
The Project Manager creates the detailed delivery plans while the Team
Leader monitors execution within the team
Project Manager communicates with project governance
authorities when necessary
The Project Manager monitors the realisation of benefits in the business

59. How could you benefit from having an End User Representative in your
development team?
A.

End users should NOT be in the development team. Requirements are

always communicated to the developers by the Product Owner, who is
part of the customer team

B.

The End User Representative will be solely responsible for acceptance

tests within the team

C.

The End User Representative assures that user stories are documented
properly

D.

The End User Representative will be able to clearly tell the

developers what will work for an end user

60. The responsibilities of a Product Owner will include

A.

Business processes diagramming

340831658.doc

16

22 December 2016

B.
C.
D.

Prioritising requirements
Managing the project budget
All of these

340831658.doc

17

22 December 2016