NEW
Font size
WorksheetsAgile Methodology Quiz
Total questions: 49
Worksheet time: 25mins
What is the role of the customer in XP?
Approve hiring
Assign developer tasks
Prioritize stories
Write code
Velocity in planning indicates:
Lines of code
Cost of software
Hardware capability
Team productivity per iteration
Refactoring should be done:
Continuously
Only after testing
Never
Only before deadlines
A spike solution is used to:
Increase velocity
Replace tests
Finalize UI
Explore technical risk
Sustainable pace implies:
Work 24/7
Avoid overtime
Work without breaks
Deliver once yearly
Pair programming increases:
Code quality
Customer distance
Work isolation
Documentation size
Which artifact guides iteration planning?
Class diagram
Deployment plan
Database schema
User Story
Test-first approach ensures:
More code duplication
Better design
More documentation
Slower coding
Acceptance tests define:
Network configuration
Database engine
UI style
Done criteria
Which Agile principle supports incremental architecture evolution?
Manager-driven refactoring
Fixed design upfront
Documentation-heavy planning
Continuous attention to technical excellence
Why does Agile avoid big upfront design?
Design is unnecessary
To reduce testing
Requirements evolve
Coding is more important than thinking
In TDD, why is minimal code written first?
To satisfy the failing test only
To avoid pairing
To finish project faster
To avoid acceptance testing
Refactoring without tests is risky because:
It changes architecture permanently
It slows performance
It increases team size
No safety net to detect breakage
A company introduces a new tool but lets the team decide whether to use it. Which principle applies?
Self-organizing teams
Manager-driven adoption
Mandatory compliance
Top-down decision making
Why are frequent software releases valuable in Agile?
They reduce testing effort
They create more documentation
They enable constant feedback and improvement
They avoid user involvement
Which Agile value is being demonstrated when a team welcomes changing requirements halfway through a project?
Following a Plan
Customer Collaboration
Responding to Change
Documentation over Software
Why does Agile encourage short, focused iterations?
They reduce communication
They provide early feedback and flexibility
They allow less testing
They make plans permanent
The product owner joins the daily stand-up to share feedback. What value is demonstrated?
Individuals and interactions over processes and tools
Customer collaboration over contract negotiation
Responding to change over following a plan
Working software over documentation
Agile teams reflect on their work regularly to:
Fill time between sprints
Find ways to become more effective
Create new documentation
Add more tasks
What does “technical excellence” mean in Agile?
Using complex tools
Following coding standards
Maintaining good design and code quality
Writing more lines of code
What is the main purpose of Refactoring?
Optimize code for speed
Improve internal structure without changing behavior
Rewrite old features
Add new functionality
What is meant by “Collective Code Ownership”?
Each developer owns specific modules
Any developer can modify any code
Only senior developers can edit
Each pair owns its feature
The “YAGNI” principle helps teams:
Avoid unnecessary complexity
Over-design for future needs
Delay testing
Write code faster
XP promotes what kind of work environment?
Open workspace for communication
Private cubicles for focus
Remote only
No shared tools
A developer removes duplicate code and simplifies logic after adding new functionality. What is this practice called?
Refactoring
Sustainable Pace
Incremental Delivery
Planning Game
When should Continuous Integration be performed?
At the end of the project
Every few hours
Once a week
Only during testing
The purpose of Small Releases in XP is:
To reduce testing effort
To get feedback early and often
To avoid planning
To delay deployment
What is the key focus of Scrum?
Predictability and control
Inspection and adaptation
Documenting every step
Reducing team size
Which meeting is time-boxed to 8 hours for a 1-month Sprint?
Sprint Review
Sprint Planning
Sprint Retrospective
Daily Scrum
What does “Done” mean in Scrum?
Work has been started
Work meets the Definition of Done
Work is reviewed by Product Owner
Work is pushed to testing
Who ensures Scrum events occur and are productive?
Scrum Master
Product Owner
Team Manager
Stakeholders
Which event inspects the work and adapts the Product Backlog?
Sprint Planning
Sprint Review
Retrospective
Daily Scrum
What is the time-box for Sprint Planning for a 2-week Sprint?
4 hours
8 hours
2 hours
1 hour
Which of the following statements about Scrum is TRUE?
Scrum is prescriptive and fixed
Scrum is lightweight but difficult to master
Scrum eliminates documentation
Scrum replaces all management roles
The Product Owner and Agile Project Manager work together to ensure:
The product meets evolving customer needs
Detailed requirement documents
Fixed schedule compliance
No feedback loops
Agile Project Managers use the term “Backlog Grooming” to describe:
Removing unnecessary meetings
Refining and prioritizing backlog items
Reviewing employee performance
Checking documentation completeness
What is the Agile Triangle of Constraints?
Time, Cost, Quality
Time, Scope, Cost
Quality, Communication, Risk
Cost, Resources, Reports
What is the main purpose of Agile metrics like velocity and burndown charts?
Evaluate individual performance
Measure project progress and predictability
Track documentation completeness
Monitor resource allocation
What is the biggest risk of not having retrospectives?
Missing meetings
No improvement in team performance
Delayed delivery
Documentation errors
In Agile Project Management, how are priorities set?
By senior management
By the Product Owner in consultation with stakeholders
By team leads
Randomly based on requests
Which Agile concept helps the team limit ongoing work and focus better?
WIP Limits (Work In Progress Limits)
Iteration Planning
Velocity
Burnup Chart
In the Spotify model, “Guilds” represent:
Groups of people sharing knowledge across squads
Management units
Budgeting committees
External consultants
Which of the following best describes the typical release schedule in SAFe?
Releasing whenever code is ready and business value is high
Releasing only after project end
Following fixed quarterly releases
Delaying release for approvals
In SAFe, what does "ART" stand for?
Agile Review Team
Agile Release Train
Agile Reporting Technique
Agile Resource Tracker
What role in SAFe facilitates PI Planning and ensures alignment across teams?
Release Train Engineer
Product Owner
Scrum Master
Business Analyst
What does the "House of Lean" emphasize?
Respect for people and relentless improvement
Strict documentation
Waterfall practices
Micro-management
What is the typical duration of a Program Increment (PI) in SAFe?
1 week
5–12 weeks (usually 10 weeks)
1 year
3 days
Which framework uses the concept of “Nexus Integration Team”?
SAFe
Nexus
Spotify
DAD
Which of the following is not a principle of SAFe?
Take an economic view
Centralize control
Unlock intrinsic motivation
Apply systems thinking
