Agile Quiz in 20 Questions

Refer to 12 principles in Agile Manifesto.

Agile philosophy believes in sustainable pace.

It says – “Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.”

Option B is correct as instead of acting as a dictator and enforcer, the agile PMO seeks to inform teams of the external compliance challenge, negotiate a reasonable process to satisfy both team and business, and most importantly, listen to the teams to understand what works and what does not work.

Option A is incorrect as agile PMO role is not limited to compliance assurance or enforcer.

Option C is incorrect as agile PMO doesn’t create processes in silos. PMO does check what works best for the team while ensuring compliance.

Option D is incorrect because 1) Compliance mean everyone has to follow. There is no way PMO get waiver for agile teams 2) Agile teams can follow the compliance requirements though with some process tailoring.

Source:
The Software Project Manager’s Bridge to Agility by Michele Sliger, Stacia Broderick. Chapter 15

Daily scrum meeting is for team members to collaborate and make commitments to each other so they should face each other so option C is incorrect and D is correct option.

All team members should provide answers of only three questions (as mentioned in the question) so there is no need for any further details. Hence, option A is incorrect.

Daily scrum is a short meeting and standing helps in keeping this short so option B is incorrect.

Source:
Agile project management with Scrum by Ken Schwaber

Healthy agile teams experience peer pressure. All team members of the team are committed to complete the work of iteration together. This makes the work (and the people) interdependent and accountable to each other.

Source:
Coaching Agile Teams by Lyssa Adkins, Chapter 9 Coach as Conflict Navigator.

Explanation:
Choice D is the correct answer.

Osmotic communication refers to the useful information that flows between team members who are working in close proximity to each other as they overhear each other’s conversations.
Hence it only works with colocation team and distributed team has to miss the advantage of osmotic communication.
Choice A, B and C are not correct with respect to the osmotic communication.
Choice D is correct, whereas choices A, B and C are incorrect.

Three 3C’s are card, conversation and confirmation. In other words, card denotes short written description, confirmation is same as success criteria, conversation is discussion with business to flesh out details of the story. Hence, the correct answer is option B.

Option A is incorrect because of incorrect aspect given ‘closing’.

Option C is incorrect because of incorrect key aspect ‘collation’ .

Option D is incorrect as we do have one correct option .

Source:
User Stories Applied: For Agile Software Development by Mike Cohn, chapter 1

Cost per story point = total budget / total story points = 200,000/400 = 500

PV = baseline velocity *no of iterations*cost per story point = 25*2*500 = 25,000

EV = 60*cost per story points = 60*500 = 30,000

SPI = EV / PV = 30,000/25,000 = 1.2

AC is just extra information which is not required to answer this question.

Source:
The Software Project Manager’s Bridge to Agility by Michele Sliger, Stacia Broderick

Option D is correct as in velocity calculations, team should consider the size estimated during iteration/sprint planning – even if that turns out to be incorrect during the sprint.

Option B is incorrect for the reason mention above. The guideline is to use iteration planning estimates in velocity calculations even team later feels that they made a mistake in estimation. It would otherwise give lot of room for teams to show higher velocity rather than focusing on improving the estimations.

Option A and C are irrelevant options to confuse as there is no point of either summing and find difference between old and new estimates.

Source:
Agile Estimation and Planning by Mike Cohn

Option C is correct as it is against the scrum rule to make scope changes during the sprint. Scrum master should work with product owner to suggest alternate ways. If features is so important, acceptable way is to stop the current sprint and let the product owner take the priority call for new sprint.

Option A is incorrect as escalation can’t be the first step without trying to resolve situation. Moreover, scrum does offer a good way to handle the situation (as mentioned above).

Option B and D are incorrect as overburdening team for additional feature isn’t reasonable. That’s against the idea of sustainable pace.

Source:
Agile project management with scrum by Ken Schwaber

By pair programming, team members discuss their methods more. They learn from each other and tend to feel ownership for entire code base rather than just code written by them so option A is the correct answer.

Option B – Continuous integration and option C- Version control, help in keeping the clean code, ready for deployment but the question here is about collective code ownership.

Option D – Done-Done is release criteria and has nothing to do with collective code ownership.

Source:
The Art of Agile Development by James Shore

Agile projects generally perform only qualitative analysis, agile’s short development cycles and constant reviews making this feasible and effective. Quantitative risk analysis is a overkill for agile projects.

Timeline is about writing significant events during iteration/project/release in chronological order, which is a key activity in “Gather Data” step.

Option A and B are incorrect as these are activities during “Generate Insights” step, rather than “Gather Data” step.

Source:
Agile Retrospectives : Making Good Teams Great by Esther Derby, Diana Larsen and Ken Schwaber

Bottom of the bar is lowered when additional work is added.
Bottom of the bar is raised when scope is removed.
Top of the bar will be lowered when work is delivered.

Source:
Agile Estimation and Planning by Mike Cohn

Option B is correct as roadmap provides a high level view of which features will be released when.

Option A is incorrect as product backlog contains features/capabilities but it doesn’t contain timelines.

Option C is incorrect as project charter does not provide information about delivery timelines for capabilities/features.

Option D is incorrect as vision is a very high level document that talks about mainly the end game – what is that we want to achieve and why that is valuable. This does not contain detailed view of timelines.

Source:
The Software project manager’s bridge to agility by Michele Slinger & Stacia Broderick

MoSCoW is a technique used for requirements prioritization.

It stands for

• Must Have;
• Should have (high priority but can manage without if necessary);
• Could have (desirable but not necessary);
• Won’t have (not for current scope but can be considered in future).

Source:
www.dsdm.org