Agile Scrum/Agile Scrum Mcq Question Set 2 Sample Test,Sample questions

 The Agile approach to documentation is:

1.Do no documentation – it is a waste of time

2.Do plenty of documentation, to prove you have done a good job

3.Do the necessary documentation to support the use of the product

4.Do more documentation than usual, because Agile is risky

 The Agile process …

1. Encourages the team to meet regularly

2.Has no meetings

3. Has lengthy reporting requirements

4.Has no reporting requirements

 The Agile way is:

1.To produce working product early and incrementally

2.To produce working product after documentation has been signed off

3.To produce simple prototypes early, but no finished product until the end of the project

4. To produce products without any technical integrity

 Which of the following best describes the approach for determining the iteration (timebox) length?

1. Iterations (timeboxes) should always be 30 days

2.The team determines iteration (timebox) length by dividing the total number of story points by the average velocity of the team

3.Iterations (timeboxes) should always be two weeks

4.The team should agree on the length of the iteration (timebox) taking the size and complexity of the project into consideration

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

1. Task focused

2.Process oriented

3. Supportive


 Which one of the following statements is true for Agile projects?

1.All project stakeholders should attend every requirements workshop

2.Retrospectives are only run at the end of a project

3.It is best if project manager facilitates the project’s workshops

4.A facilitator will manage the structure of a facilitated workshop

A burn-down chart shows …

1. The declining energy level of the team

2.The progress of the work and features completed

3. The number of hours worked after dark

4.The rate of reduction of budget for a project

A sustainable pace means …

1. If the team work long hours regularly they will get used to it, and be able to sustain it

2. A 40 hour week is for the weak

3.The team should establish a velocity which can be sustained with normal working hours

4.Working long hours is the only way to deliver early

An Agile approach advocates which of the following approaches?

1.Get something quick and dirty thrown together to save time

2.Get something simple up and working as quickly as possible

3. Get something business-valuable delivered as quickly as possible, consistent with the right level of quality

4.Get something delivered once it has been fully documented and the documentation signed off as complete and unchangeable

An Agile approach values …

1.Process over people

2.People over process

3.Plans over process

4. Plans over people

An Agile customer …

1.Must have a good understanding of Agile techniques

2.Will always receive worse systems than their non-Agile counterparts

3.Will typically get business value delivered early

4.Will need to work out at the gym regularly

An Agile project …

1.Should have no control over its progress

2.Should be able to demonstrate control of its progress

3.Is always out of control

4.Is controlled by the velocity of the most junior team member

An Agile project should have:

1.Occasional early deliveries, if the business is prepared to accept lower quality

2.A regular pattern of delivery of developer-focused products

3. A regular pattern of delivery of business-valued increments

4. An irregular and unpredictable delivery of products

An Agile team …

1.Is self-organizing, so needs no specific skills

2.Collaborates and supports team members

3.Ensures that weak members of the team are thrown out of the team

4.Ensures blame is allocated fairly

During an Iteration (Sprint) the developers should be:

1.Able to contact the customer to clarify aspects of the work

2.Completely uninterrupted by the customer

3.In twice-daily contact with the customer

4.Able to work without needing to disturb the customer

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

1. The Project Leader should give tasks to individuals to create challenges for them

2.Tasks should be randomly allocated using Planning Poker

3.Team members should self-select tasks

4.The biggest tasks should be done by the Project Leader themselves

If a timebox (iteration) plan needs to be reprioritised in a hurry, who should re-prioritise?

1.The developers alone (they know what the customer wants by now)

2.The customer alone (the developers would only choose the easy things as top priority)

3. The Project Leader (they can give an independent, pragmatic view)

4.The whole team including customer and developers (together they can consider both business value and practicality) © Copyright DSDM Consortium 2009. All rights reserved.

In Agile projects, we plan to “learn as we go” because…

1.It is more fun for the developers

2.Many projects are evolutionary, and a better solution emerges this way

3. It is boring to try to analyse everything at the beginning of a project

4.It gives a good reason for late delivery

In the popular prioritization technique called “MoSCoW”, the “M” stands for:

1.May have


3.Must Have


Once a project is underway, the approach to planning is:

1.Plans should never be changed

2.It is normal to need to plan and re-plan as the project progresses

3.Plans should only be changed with full approval of all stakeholders

4.Plans are not required

One of the stages you would expect to see a team go through is:




4. Yawning

The Agile leader …

1.Should hand out tasks to the team each day

2.Should expect the team to be involved in work-allocation

3.Should give detailed work-plans to the team each day

4.Should micro-manage the work of the team, if they are inexperienced

The customer in an Agile project …

1.Has no control over the prioritization of delivered features

2.Has total control over the prioritization of features

3.Collaborates with the developers over prioritization of features, but the developers have the final decision

4.Collaborates with the developers over prioritization of features, but the business has the final decision

The end result of an Agile development is:

1. A product of a professional quality which fits the business need

2.A product of almost as good a quality to a Waterfall development

3.Rather poor quality but at least it is quick

4.A technically perfect re-factored solution

The leadership style of an Agile Leader is …

1. Fascinating


3. Facilitative


The reason for holding regular retrospectives is:

1.It allows the team to take a welcome break from work

2. It gives management information to use in team members’ performance reviews

3.It allows learning which can be used to improve team performance during the project

4. It prevents deviation from the process which the team has been following

The recommended approach to design in an Agile project is:

1.No design up front

2.Big design up front

3.Just enough design up front

4.Use a previous design – it will be good enough

The working culture of an Agile team is …

1. Collective



4. Contemplative

Tracking project issues in an Agile project is the primary responsibility of the…


2.Project Leader

3.Functional Manager


What are the advantages of maintaining consistent iteration (timebox) lengths throughout the project?

1.They help to establish a consistent pattern of delivery

2.They help the team to objectively measure progress

3.They provide a consistent means of measuring team velocity

4.All of the above

What is a Kan Ban?

1.A list of activities that can be banned by the team

2.The set of Won’t Haves for a project

3.A visible chart of work for the team

4. A ban on fizzy drinks within the team

What is meant by “Yesterday’s Weather” in an Agile project?

1. Teams work less well when it rains

2.Keeping metrics of earlier work to help with future estimates

3.Retrospectives should include less important topics such as the weather

4. Estimating is as futile as predicting the weather

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

1.A big design up front is always a good idea

2. Just enough design up front gives a good foundation to start from and helps to mitigate risk, without unnecessarily wasting time

3. No design up front is the best approach as most of the fun of a project is discovery of the unexpected

4.Design has no place in an Agile project

What is the best approach for running an effective workshop?





What is the effect of having large visible project plan on a wall?

1. It is a fire risk and a health hazard

2. It communicates progress to the team and other stakeholders

3.It is dangerous, as management will misinterpret what the team is doing

4. It is useless, as it does not allow the team to innovate

What is the risk that an Agile leader takes in empowering the team?

1.The Agile leader might lose their job as the team is doing all the work

2. If the team fails, the Agile leader will not get a performance bonus

3.The Agile leader has less direct control over the team’s work, but still has the responsibility

4.The Agile leader cannot share the glory of team success

What should the team do if the customer representative is too busy to be available?

1.Carry on with the work without customer input. It will probably be faster without customer interference anyway

2.Send the customer an email warning that the end product will be completed on time, but will not meet their needs

3.Allow a developer to take on the role of customer representative

4.Draw the problem to the attention of the Project Leader and ultimately the Project Sponsor

When estimating is done for the project, the solution developers should be:

1.Involved in the process

2. In total control of the process

3.Told what the estimates should be

4. Not making estimates at all

When handling team dynamics, the Agile Leader should …

1.A Work to build trust between the team members

2. Encourage an environment of competition and personal advantage

3.Stand for no nonsense and show who is the boss

4.Expect team members to sort out all of their own problems, and not come to the Project Leader for help with anything

Which of the following are attributes of an Agile team?

1. Trust and courage

2. Infinite patience

3. Cynicism

4.Hope and charity

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

1.Planning is a waste of time and should not be done

2.Planning should be done in detail at the outset and then not revisited

3.Planning is an iterative job and involves the whole team

4.Planning should all be done by the Project Manager

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

1.The team can work all night, every night if enough pizza is provided

2.The team should be expected to work overtime towards the end of the project

3.The team should strive for a sustainable pace and a normal working week

4.The team will “burn out” if they have to work overtime for more than two timeboxes (iterations) in a row

Which one of the following is a key feature that you would expect to find in an Agile project?

1. A large number of written progress reports

2.No project documentation, as all communication is tacit information

3.Good face-to-face communication, supplemented by lean but sufficient documentation

4.All documentation done in previous projects would be replicated for the Agile project.

Which one of the following is an important feature of the stand-up / wash up meeting?

1.Everyone must stand for the whole time

2.The meeting must be short and well structured

3.The Project Manager must ensure it is clear to all which team members are not performing

4.No-one is allowed to leave the stand-up meeting until all problems raised have been solved

Which one of the following statement is correct regarding quality of deliverables from an Agile Project?

1.The products produced by an Agile project should be cheaper than those produced by any other approach, but quality will suffer

2.The products will be more expensive than by any other approach but will be top quality

3.The products will be fit for purpose, but may not do what the customer wanted

4.The products will be of appropriate quality, as guided by the customer representative involved throughout the development process

Which one of the following statements is correct regarding acceptance of any deliverables on an Agile Project?

1. The team should allow only senior managers to sign off deliverables

2. The team should get acceptance of project deliverables from the appropriate stakeholders at least at the end of every timebox / iteration

3.The team should get acceptance of project deliverables from the users during a UAT phase at the end of the project

4.Acceptance of any particular deliverable on the project is gained from all stakeholders at the same time.

Who is responsible for prioritizing the product backlog?

1.Product Owner

2.Project Manager

3.Lead Developer


Who should attend the stand-up meetings?

1. Sponsor and Executive Management only

2.Project Manager and Technical Leads only

3.Project Leader and Customer Representatives only

4.The entire team

Who should be the main judge of the business value?

1.The customer representative

2.The project leader

3. The facilitator

4.All of the above

Why is it important to trust the team?

1.High trust teams do not have to be accountable to each other

2.High trust teams do not require a user representative

3.The Project Manager does not have to keep a project schedule

4.The presence of trust is positively correlated with the team performance


  1. Agile Scrum Mcq Question Set 1
  2. Agile Scrum Mcq Question Set 2
R4R Team
R4Rin Top Tutorials are Core Java,Hibernate ,Spring,Sturts.The content on website is done by expert team not only with the help of books but along with the strong professional knowledge in all context like coding,designing, marketing,etc!