🧪 Agile Scrum MCQ Quiz Hub

1. Which of the following best describes the approach for determining the iteration (timebox) length?
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?
Task focused
Process oriented
Supportive
Disinterested

3. Who is responsible for prioritizing the product backlog?
Product Owner
Project Manager
Lead Developer
Tester

4. What are the advantages of maintaining consistent iteration (timebox) lengths throughout the project?
They help to establish a consistent pattern of delivery
They help the team to objectively measure progress
They provide 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…
Tester
Project Leader
Functional Manager
Developer

6. Why is it important to trust the team?
High trust teams do not have to be accountable to each other
High trust teams do not require a user representative
The Project Manager does not have to keep a project schedule
The presence of trust is positively correlated with the team performance

7. What is the best approach for running an effective workshop?
Presentation
Oratory
Facilitation
Lecture

8. Which of the following best represents the Agile approach to planning?
Planning is a waste of time and should not be done
Planning should be done in detail at the outset and then not revisited
Planning is an iterative job and involves the whole team
Planning should all be done by the Project Manager

9. Who should be the main judge of the business value?
The customer representative
The project leader
The facilitator
All of the above

10. If a timebox (iteration) plan needs to be reprioritised in a hurry, who should re-prioritise?
The developers alone (they know what the customer wants by now)
The customer alone (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 customer and developers (together they can consider both business value and practicality) © Copyright DSDM Consortium 2009. All rights reserved.

11. What is the effect of having large visible project plan on a wall?
It is a fire risk and a health hazard
It communicates progress to the team and other stakeholders
It is dangerous, as management will misinterpret what the team is doing
It is useless, as it does not allow the team to innovate

12. How should work be allocated to the team in an Agile project?
The Project Leader should give tasks to individuals to create challenges for them
Tasks should be randomly allocated using Planning Poker
Team members should self-select tasks
The biggest tasks should be done by the Project Leader themselves

13. What should the team do if the customer representative is too busy to be available?
Carry on with the work without customer input. It will probably be faster without customer interference anyway
Send the customer an email warning that the end product will be completed on time, but will not meet their needs
Allow a developer to take on the role of customer representative
Draw the problem to the attention of the Project Leader and ultimately the Project Sponsor

14. Which one of the following is a key feature that you would expect to find in an Agile project?
A large number of written progress reports
No project documentation, as all communication is tacit information
Good face-to-face communication, supplemented by lean but sufficient documentation
All documentation done in previous projects would be replicated for the Agile project.

15. When handling team dynamics, the Agile Leader should …
A Work to build trust between the team members
Encourage an environment of competition and personal advantage
Stand for no nonsense and show who is the boss
Expect team members to sort out all of their own problems, and not come to the Project Leader for help with anything

16. Which one of the following statements is correct regarding acceptance of any deliverables on an Agile Project?
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 statement is correct regarding quality of deliverables from an Agile Project?
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 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 unnecessarily wasting time
No design up front is the best approach as most of the fun of a project is discovery of the unexpected
Design has no place in an Agile project

19. An Agile approach advocates which of the following approaches?
Get something quick and dirty thrown together to save time
Get something simple up and working 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 signed off as complete and unchangeable

20. Which of these best describes the Agile approach to team-working?
The team can work all night, every night if enough pizza is provided
The team should be expected to work overtime towards the end of the project
The team should strive for a sustainable pace and a normal working week
The team will “burn out” if they have to work overtime for more than two timeboxes (iterations) in a row

21. Which one of the following statements is true for Agile projects?
All project stakeholders should attend every requirements workshop
Retrospectives are only run at the end of a project
It is best if project manager facilitates the project’s workshops
A facilitator will manage the structure of a facilitated workshop

22. Which one of the following is an important feature of the stand-up / wash up meeting?
Everyone must stand for the whole time
The meeting must be short and well structured
The Project Manager must ensure 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

23. Who should attend the stand-up meetings?
Sponsor and Executive Management only
Project Manager and Technical Leads only
Project Leader and Customer Representatives only
The entire team

24. One of the stages you would expect to see a team go through is:
Storming
Warming
Calming
Yawning

25. When estimating is done for the project, the solution developers should be:
Involved in the process
In total control of the process
Told what the estimates should be
Not making estimates at all

26. During an Iteration (Sprint) the developers should be:
Able to contact the customer to clarify aspects of the work
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 product of a professional quality which fits the business need
A product of almost as good a quality to a Waterfall development
Rather poor quality but at least it is quick
A technically perfect re-factored solution

28. An Agile customer …
Must have a good understanding of Agile techniques
Will always receive worse systems than their non-Agile counterparts
Will typically get business value delivered early
Will need to work out at the gym regularly

29. An Agile team …
Is self-organizing, so needs no specific skills
Collaborates and supports team members
Ensures that weak members of the team are thrown out of the team
Ensures blame is allocated fairly

30. The Agile process …
Encourages the team to meet regularly
Has no meetings
Has lengthy reporting requirements
Has no reporting requirements

31. The Agile leader …
Should hand out tasks to the team each day
Should expect the team to be involved in work-allocation
Should give detailed work-plans to the team each day
Should micro-manage the work of the team, if they are inexperienced

32. What is a Kan Ban?
A list of activities that can be banned by the team
The set of Won’t Haves for a project
A visible chart of work for the team
A ban on fizzy drinks within the team

33. What is meant by “Yesterday’s Weather” in an Agile project?
Teams work less well when it rains
Keeping metrics of earlier work to help with future estimates
Retrospectives should include less important topics such as the weather
Estimating is as futile as predicting the weather

34. In Agile projects, we plan to “learn as we go” because…
It is more fun for the developers
Many projects are evolutionary, and a better solution emerges this way
It is boring to try to analyse everything at the beginning of a project
It gives a good reason for late delivery

35. The recommended approach to design in an Agile project is:
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 risk that an Agile leader takes in empowering the team?
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 team’s work, but still has the responsibility
The Agile leader cannot share the glory of team success

37. The Agile approach to documentation is:
Do no documentation – it is a waste of time
Do plenty of documentation, to prove you have done a good job
Do the necessary documentation to support the use of the product
Do more documentation than usual, because Agile is risky

38. The Agile way is:
To produce working product early and incrementally
To produce working product after documentation has been signed off
To produce simple prototypes early, but no finished product until the end of the project
To produce products without any technical integrity

39. The customer in an Agile project …
Has no control over the prioritization of delivered features
Has total control over the prioritization of features
Collaborates with the developers over prioritization of features, but the developers have the final decision
Collaborates with the developers over prioritization of features, but the business has the final decision

40. In the popular prioritization technique called “MoSCoW”, the “M” stands for:
May have
Major
Must Have
Mandatory

41. The working culture of an Agile team is …
Collective
Collaborative
Connective
Contemplative

42. The leadership style of an Agile Leader is …
Fascinating
Fabulous
Facilitative
Fantastic

43. An Agile approach values …
Process over people
People over process
Plans over process
Plans over people

44. Which of the following are attributes of an Agile team?
Trust and courage
Infinite patience
Cynicism
Hope and charity

45. A sustainable pace means …
If the team work long hours regularly they will get used to it, and be able to sustain it
A 40 hour week is for the weak
The team should establish a velocity which can be sustained with normal working hours
Working long hours is the only way to deliver early

46. A burn-down chart shows …
The declining energy level of the team
The progress of the work and features completed
The number of hours worked after dark
The rate of reduction of budget for a project

47. The reason for holding regular retrospectives is:
It allows the team to take a welcome break from work
It gives management information to use in team members’ performance reviews
It allows learning which can be used to improve team performance during the project
It prevents deviation from the process which the team has been following

48. Once a project is underway, the approach to planning is:
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

49. An Agile project …
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:
Occasional early deliveries, if the business is prepared to accept lower quality
A regular pattern of delivery of developer-focused products
A regular pattern of delivery of business-valued increments
An irregular and unpredictable delivery of products