Agile Global Certification (Generic Module) | Practice Test / Quiz / MCQs

Home > Agile > Quizzes > Agile Global Certification (Generic Module)

Agile Global Certification (Generic Module)

Fast practice, instant feedback. Timer auto-submits when time’s up.

Avg score: 0% • Most missed: “5 steps in the first half of Sprint planning”

Study First Challenge a Friend Stats

Agile Global Certification (Generic Module)

Time left 00:00

25 Questions

1. 5 steps in the first half of Sprint planning

If there are issues on the items in scope for the Sprint, Team discusses with the Product Owner for the reprioritization A refined and prioritized list of features - An ordered and emerging list of user needs/stories plus anything else that is required to fulfill the Product Vision - Only a single Product Backlog exists and is refined and updated through the lifetime of the project - Responsibility of the Product Owner1. Team collaborates with Product Owner and decides what will be delivered as part of the Sprint 2. Product Owner describes User Stories to team 3. PO details the interaction 4. PO reviews infrastructure and interface 5. PO explains the acceptance criteria1. Embracing Change (traditional: change is not encouraged) 2. Self-organizing team (traditional: team directed by someone else) 3. Collaboration (traditional: processes based mindset instead of agile behavior based mindset)

2. What is the Team supposed to do if there are issues during the first half of the Sprint Planning in the scrum process?

A refined and prioritized list of features - An ordered and emerging list of user needs/stories plus anything else that is required to fulfill the Product Vision - Only a single Product Backlog exists and is refined and updated through the lifetime of the project - Responsibility of the Product Owner1. Embracing Change (traditional: change is not encouraged) 2. Self-organizing team (traditional: team directed by someone else) 3. Collaboration (traditional: processes based mindset instead of agile behavior based mindset)1. Team collaborates with Product Owner and decides what will be delivered as part of the Sprint 2. Product Owner describes User Stories to team 3. PO details the interaction 4. PO reviews infrastructure and interface 5. PO explains the acceptance criteriaIf there are issues on the items in scope for the Sprint, Team discusses with the Product Owner for the reprioritization

3. 3 key mind shifts needed in Agile projects

If there are issues on the items in scope for the Sprint, Team discusses with the Product Owner for the reprioritization1. Embracing Change (traditional: change is not encouraged) 2. Self-organizing team (traditional: team directed by someone else) 3. Collaboration (traditional: processes based mindset instead of agile behavior based mindset)1. Team collaborates with Product Owner and decides what will be delivered as part of the Sprint 2. Product Owner describes User Stories to team 3. PO details the interaction 4. PO reviews infrastructure and interface 5. PO explains the acceptance criteria A refined and prioritized list of features - An ordered and emerging list of user needs/stories plus anything else that is required to fulfill the Product Vision - Only a single Product Backlog exists and is refined and updated through the lifetime of the project - Responsibility of the Product Owner

4. What is a Product Backlog in the scrum process?

1. Embracing Change (traditional: change is not encouraged) 2. Self-organizing team (traditional: team directed by someone else) 3. Collaboration (traditional: processes based mindset instead of agile behavior based mindset)1. Team collaborates with Product Owner and decides what will be delivered as part of the Sprint 2. Product Owner describes User Stories to team 3. PO details the interaction 4. PO reviews infrastructure and interface 5. PO explains the acceptance criteria A refined and prioritized list of features - An ordered and emerging list of user needs/stories plus anything else that is required to fulfill the Product Vision - Only a single Product Backlog exists and is refined and updated through the lifetime of the project - Responsibility of the Product OwnerIf there are issues on the items in scope for the Sprint, Team discusses with the Product Owner for the reprioritization

5. What is the release burn down graph in the scrum process?

If there are issues on the items in scope for the Sprint, Team discusses with the Product Owner for the reprioritization1. Team collaborates with Product Owner and decides what will be delivered as part of the Sprint 2. Product Owner describes User Stories to team 3. PO details the interaction 4. PO reviews infrastructure and interface 5. PO explains the acceptance criteria It records the sum of remaining Product Backlog estimated work across time and depicts the progress of the release on a real time basis - The X-axis contains the number of Sprints for the release - The Y axis contains the effort remaining in the release1. Embracing Change (traditional: change is not encouraged) 2. Self-organizing team (traditional: team directed by someone else) 3. Collaboration (traditional: processes based mindset instead of agile behavior based mindset)

6. What is the iterative planning in XP Programming?

If there are issues on the items in scope for the Sprint, Team discusses with the Product Owner for the reprioritization A planning meeting by the Team to decide upon the tasks and activities, to accomplish requirements planned for the iteration - It has 3 phases: exploration, commitment, steering1. Embracing Change (traditional: change is not encouraged) 2. Self-organizing team (traditional: team directed by someone else) 3. Collaboration (traditional: processes based mindset instead of agile behavior based mindset)1. Team collaborates with Product Owner and decides what will be delivered as part of the Sprint 2. Product Owner describes User Stories to team 3. PO details the interaction 4. PO reviews infrastructure and interface 5. PO explains the acceptance criteria

7. What is the duration of sprints?

1. Team collaborates with Product Owner and decides what will be delivered as part of the Sprint 2. Product Owner describes User Stories to team 3. PO details the interaction 4. PO reviews infrastructure and interface 5. PO explains the acceptance criteria1. Embracing Change (traditional: change is not encouraged) 2. Self-organizing team (traditional: team directed by someone else) 3. Collaboration (traditional: processes based mindset instead of agile behavior based mindset)If there are issues on the items in scope for the Sprint, Team discusses with the Product Owner for the reprioritizationUsually around 1 to 4 weeks

8. What happens in the first half of the Sprint Planning meeting in the scrum process?

1. Team collaborates with Product Owner and decides what will be delivered as part of the Sprint 2. Product Owner describes User Stories to team 3. PO details the interaction 4. PO reviews infrastructure and interface 5. PO explains the acceptance criteriaIf there are issues on the items in scope for the Sprint, Team discusses with the Product Owner for the reprioritization The Team focuses on understanding what the Product Owner wants and what would be delivered as part of the Sprint - The entire Team works together on understanding the scope of the Sprint.1. Embracing Change (traditional: change is not encouraged) 2. Self-organizing team (traditional: team directed by someone else) 3. Collaboration (traditional: processes based mindset instead of agile behavior based mindset)

9. What is the 'Definition of Done' in the scrum process?

1. Embracing Change (traditional: change is not encouraged) 2. Self-organizing team (traditional: team directed by someone else) 3. Collaboration (traditional: processes based mindset instead of agile behavior based mindset) It determines conditions to be considered when a specific task/event is completed, validated and is ready for acceptance - The team agrees on and displays prominently a list of criteria which must be met before a task is considered 'Done'1. Team collaborates with Product Owner and decides what will be delivered as part of the Sprint 2. Product Owner describes User Stories to team 3. PO details the interaction 4. PO reviews infrastructure and interface 5. PO explains the acceptance criteriaIf there are issues on the items in scope for the Sprint, Team discusses with the Product Owner for the reprioritization

10. How often do the project level estimates get refined?

1. Team collaborates with Product Owner and decides what will be delivered as part of the Sprint 2. Product Owner describes User Stories to team 3. PO details the interaction 4. PO reviews infrastructure and interface 5. PO explains the acceptance criteriaIf there are issues on the items in scope for the Sprint, Team discusses with the Product Owner for the reprioritizationRegularly at the planning phase of each Release/Sprint1. Embracing Change (traditional: change is not encouraged) 2. Self-organizing team (traditional: team directed by someone else) 3. Collaboration (traditional: processes based mindset instead of agile behavior based mindset)

11. What is Scrum?

If there are issues on the items in scope for the Sprint, Team discusses with the Product Owner for the reprioritization an iterative and incremental approach for software development achieved through iterative cycles known as Sprints - software should be fully integrated, fully working, fully tested - the Sprints are strictly time-boxed and occur sequentially1. Embracing Change (traditional: change is not encouraged) 2. Self-organizing team (traditional: team directed by someone else) 3. Collaboration (traditional: processes based mindset instead of agile behavior based mindset)1. Team collaborates with Product Owner and decides what will be delivered as part of the Sprint 2. Product Owner describes User Stories to team 3. PO details the interaction 4. PO reviews infrastructure and interface 5. PO explains the acceptance criteria

12. What happens during estimation at the Project Level? (2)

If there are issues on the items in scope for the Sprint, Team discusses with the Product Owner for the reprioritization1. Team collaborates with Product Owner and decides what will be delivered as part of the Sprint 2. Product Owner describes User Stories to team 3. PO details the interaction 4. PO reviews infrastructure and interface 5. PO explains the acceptance criteria1. We gather additional details about the Epics (i.e. high level User Stories/ requirements) mentioned in the Product Backlog during the project initiation 2. Epics are sized and the overall effort is derived based on several inputs - Interactions with the Product Owner (or Client manager) will be necessary to get more information about it1. Embracing Change (traditional: change is not encouraged) 2. Self-organizing team (traditional: team directed by someone else) 3. Collaboration (traditional: processes based mindset instead of agile behavior based mindset)

13. What is the main purpose of a Requirements Workshop?

1. Team collaborates with Product Owner and decides what will be delivered as part of the Sprint 2. Product Owner describes User Stories to team 3. PO details the interaction 4. PO reviews infrastructure and interface 5. PO explains the acceptance criteriaIf there are issues on the items in scope for the Sprint, Team discusses with the Product Owner for the reprioritization1. Embracing Change (traditional: change is not encouraged) 2. Self-organizing team (traditional: team directed by someone else) 3. Collaboration (traditional: processes based mindset instead of agile behavior based mindset)To gather, understand/prioritize requirements, and define a high level plan for the Releases mainly during the Project Initiation phase

14. Any team member recommending a change to a Product Backlog item's priority, has to discuss this with the Product Owner in the scrum process (T/F)

1. Team collaborates with Product Owner and decides what will be delivered as part of the Sprint 2. Product Owner describes User Stories to team 3. PO details the interaction 4. PO reviews infrastructure and interface 5. PO explains the acceptance criteriaIf there are issues on the items in scope for the Sprint, Team discusses with the Product Owner for the reprioritization1. Embracing Change (traditional: change is not encouraged) 2. Self-organizing team (traditional: team directed by someone else) 3. Collaboration (traditional: processes based mindset instead of agile behavior based mindset)TRUE

15. Release planning does not provide detailed view of how the team would plan to drive the work within Sprints (T/F)

If there are issues on the items in scope for the Sprint, Team discusses with the Product Owner for the reprioritizationTRUE1. Team collaborates with Product Owner and decides what will be delivered as part of the Sprint 2. Product Owner describes User Stories to team 3. PO details the interaction 4. PO reviews infrastructure and interface 5. PO explains the acceptance criteria1. Embracing Change (traditional: change is not encouraged) 2. Self-organizing team (traditional: team directed by someone else) 3. Collaboration (traditional: processes based mindset instead of agile behavior based mindset)

16. What is Extreme Programming?

1. Team collaborates with Product Owner and decides what will be delivered as part of the Sprint 2. Product Owner describes User Stories to team 3. PO details the interaction 4. PO reviews infrastructure and interface 5. PO explains the acceptance criteriaIf there are issues on the items in scope for the Sprint, Team discusses with the Product Owner for the reprioritization One of the popular Agile methodologies and it is mostly used along with Scrum framework to create a blend of both engineering and management practices in Agile projects1. Embracing Change (traditional: change is not encouraged) 2. Self-organizing team (traditional: team directed by someone else) 3. Collaboration (traditional: processes based mindset instead of agile behavior based mindset)

17. 4 key steps to a disciplined team

If there are issues on the items in scope for the Sprint, Team discusses with the Product Owner for the reprioritization1. Embracing Change (traditional: change is not encouraged) 2. Self-organizing team (traditional: team directed by someone else) 3. Collaboration (traditional: processes based mindset instead of agile behavior based mindset)1. Update ALM daily (Product Backlog, Sprint Backlog, Release and Sprint Burndown charts) 2. Transparency 3. Retrospective1. Team collaborates with Product Owner and decides what will be delivered as part of the Sprint 2. Product Owner describes User Stories to team 3. PO details the interaction 4. PO reviews infrastructure and interface 5. PO explains the acceptance criteria

18. 3 techniques for release planning estimation

If there are issues on the items in scope for the Sprint, Team discusses with the Product Owner for the reprioritization1. Wideband Delphi (Consensus approach) 2. Estimation by Analogy (Extrapolation) 3. Planning Poker1. Team collaborates with Product Owner and decides what will be delivered as part of the Sprint 2. Product Owner describes User Stories to team 3. PO details the interaction 4. PO reviews infrastructure and interface 5. PO explains the acceptance criteria1. Embracing Change (traditional: change is not encouraged) 2. Self-organizing team (traditional: team directed by someone else) 3. Collaboration (traditional: processes based mindset instead of agile behavior based mindset)

19. What are the characteristics of the coding activity in XP Programming? (4)

1. Team collaborates with Product Owner and decides what will be delivered as part of the Sprint 2. Product Owner describes User Stories to team 3. PO details the interaction 4. PO reviews infrastructure and interface 5. PO explains the acceptance criteria1. Most important activity of Software Development 2. Used to find out the software solution 3. Used to communicate thoughts among programmers 4. Working product is nothing but codeIf there are issues on the items in scope for the Sprint, Team discusses with the Product Owner for the reprioritization1. Embracing Change (traditional: change is not encouraged) 2. Self-organizing team (traditional: team directed by someone else) 3. Collaboration (traditional: processes based mindset instead of agile behavior based mindset)

20. Who participates in Sprint planning? (3)

1. Team collaborates with Product Owner and decides what will be delivered as part of the Sprint 2. Product Owner describes User Stories to team 3. PO details the interaction 4. PO reviews infrastructure and interface 5. PO explains the acceptance criteria1. Embracing Change (traditional: change is not encouraged) 2. Self-organizing team (traditional: team directed by someone else) 3. Collaboration (traditional: processes based mindset instead of agile behavior based mindset)1. Product Owner 2. Scrum Master 3. All the team members (analysts, programmers, testers, database engineers, user interaction designers, etc.)If there are issues on the items in scope for the Sprint, Team discusses with the Product Owner for the reprioritization

21. What do we base the prioritization of a Product Backlog on? (3)

1. Embracing Change (traditional: change is not encouraged) 2. Self-organizing team (traditional: team directed by someone else) 3. Collaboration (traditional: processes based mindset instead of agile behavior based mindset)1. Business value 2. Release date 3. Interdependency1. Team collaborates with Product Owner and decides what will be delivered as part of the Sprint 2. Product Owner describes User Stories to team 3. PO details the interaction 4. PO reviews infrastructure and interface 5. PO explains the acceptance criteriaIf there are issues on the items in scope for the Sprint, Team discusses with the Product Owner for the reprioritization

22. What is Continuous Integration? (XP)

A code base is integrated on a frequent basis from the start of the feature development - It is an automated process in which builds are created from the common source code repository - Helps in identifying integration issues much ahead in the lifecycle and hence, reduces much of the rework cost1. Team collaborates with Product Owner and decides what will be delivered as part of the Sprint 2. Product Owner describes User Stories to team 3. PO details the interaction 4. PO reviews infrastructure and interface 5. PO explains the acceptance criteria1. Embracing Change (traditional: change is not encouraged) 2. Self-organizing team (traditional: team directed by someone else) 3. Collaboration (traditional: processes based mindset instead of agile behavior based mindset)If there are issues on the items in scope for the Sprint, Team discusses with the Product Owner for the reprioritization

23. What are the characteristics of the designing activity in XP Programming? (2)

1. Team collaborates with Product Owner and decides what will be delivered as part of the Sprint 2. Product Owner describes User Stories to team 3. PO details the interaction 4. PO reviews infrastructure and interface 5. PO explains the acceptance criteriaIf there are issues on the items in scope for the Sprint, Team discusses with the Product Owner for the reprioritization1. Embracing Change (traditional: change is not encouraged) 2. Self-organizing team (traditional: team directed by someone else) 3. Collaboration (traditional: processes based mindset instead of agile behavior based mindset)1. Creating the design structure to organize logic of the system 2. Good design practices

24. What is MoSCoW methodology?

1. Team collaborates with Product Owner and decides what will be delivered as part of the Sprint 2. Product Owner describes User Stories to team 3. PO details the interaction 4. PO reviews infrastructure and interface 5. PO explains the acceptance criteria'Must have', 'Should have', 'Could have', and 'Won't have'1. Embracing Change (traditional: change is not encouraged) 2. Self-organizing team (traditional: team directed by someone else) 3. Collaboration (traditional: processes based mindset instead of agile behavior based mindset)If there are issues on the items in scope for the Sprint, Team discusses with the Product Owner for the reprioritization

25. What are the 4 XP activities?

1. Embracing Change (traditional: change is not encouraged) 2. Self-organizing team (traditional: team directed by someone else) 3. Collaboration (traditional: processes based mindset instead of agile behavior based mindset)1. Team collaborates with Product Owner and decides what will be delivered as part of the Sprint 2. Product Owner describes User Stories to team 3. PO details the interaction 4. PO reviews infrastructure and interface 5. PO explains the acceptance criteriaIf there are issues on the items in scope for the Sprint, Team discusses with the Product Owner for the reprioritization1. Coding 2. Testing 3. Listening 4. Designing

⚡ Recently practiced quizzes in this topic

Live quiz activity

Agile Scrum Methodology Agile Development Agile Knowledge Test Agile Methodologies Quiz PMI ACP Review PMI-ACP Agile Certified Practitioner Certification Exam Practice Test: Value-Driven Delivery in Agile Projects PMI-ACP Agile Certified Practitioner Certification Exam Practice Test: Planning for Agile Projects Agile Certified Practitioner Agile Methodology Practice Test Questions Agile Certification Questions

25 Questions

❤ If you liked Fatskills, consider supporting us by checking out The Life Manuals You Never Got.

About | Explore | User Guide | Topics | Subjects | Doubt Solver | Career Aptitude Test | Answers | Free Tools | OSHA Basics Quiz | What Should We Know?
Privacy | Terms |

Without work one finishes nothing. - Ralph Waldo Emerson
© 2026 Fatskills.com

All trademarks, logos and brand names are the property of their respective owners. All company, product and service names used in this website are for identification purposes only. Use of these names, trademarks and brands does not imply endorsement.

25 Questions

❤ If you liked Fatskills, consider supporting us by checking out The Life Manuals You Never Got.

About | Explore | User Guide | Topics | Subjects | Doubt Solver | Career Aptitude Test | Answers | Free Tools | OSHA Basics Quiz | What Should We Know? Privacy | Terms |

Without work one finishes nothing. - Ralph Waldo Emerson© 2026 Fatskills.com

All trademarks, logos and brand names are the property of their respective owners. All company, product and service names used in this website are for identification purposes only. Use of these names, trademarks and brands does not imply endorsement.

About | Explore | User Guide | Topics | Subjects | Doubt Solver | Career Aptitude Test | Answers | Free Tools | OSHA Basics Quiz | What Should We Know?
Privacy | Terms |

Without work one finishes nothing. - Ralph Waldo Emerson
© 2026 Fatskills.com