Certified Agile Professional (CAP) Exam

1. Question

Which statement best describes the role of leadership in Agile Enterprise Strategy Development?

Leadership should delegate all strategic decisions to Agile teams.
Leadership should focus solely on financial aspects.
Leadership should establish and communicate strategic direction.
Leadership should avoid involvement in day-to-day Agile operations.

2. Question

What is the primary goal of Enterprise Strategy Development in an Agile environment?

To define strict project guidelines.
To ensure all projects are completed on time.
To align organizational development with overarching business goals.
To minimize the cost of all projects.

3. Question

How does Enterprise Strategy Development impact decision-making in Agile product development?

It limits team autonomy in decision-making.
It has no impact on decision-making.
It provides direction that guides product alignment with strategic goals.
It dictates all tactical decisions on projects.

4. Question

What aspect of Enterprise Strategy Development is crucial for sustaining competitive advantage in a rapidly changing market?

Reducing operational costs to a minimum.
Ensuring all projects are technology driven.
Continuously adapting strategic goals to market changes.
Keeping strategy development processes static and predictable.

5. Question

Enterprise Strategy Development in Agile environments emphasize the importance of which of the following?

Long-term planning without the need for adjustments.
Rigid adherence to traditional management roles.
Flexibility and responsiveness to change.
Centralized decision-making.

6. Question

What is the main purpose of Agile Design Thinking?

To decrease product development costs.
To align product design with user needs and enhance innovation.
To speed up the manufacturing process.
To standardize product designs across the industry.

7. Question

Which technique is commonly used in Agile Design Thinking to understand user needs?

Financial analysis.
Empathy mapping.
Resource allocation.
Competitive benchmarking.

8. Question

Agile Design Thinking typically includes the following phases?

Problem definition, ideation, prototyping, testing.
Budgeting, testing, delivery, feedback.
Planning, execution, closure.
Analysis, design, coding, maintenance.

9. Question

How does prototyping benefit the Agile Design Thinking process?

It reduces the need for user feedback.
It allows for rapid experimentation and feedback incorporation.
It extends the product development cycle.
It eliminates the ideation phase.

10. Question

Which outcome is a direct benefit of integrating Agile Design Thinking in product development?

Increased bureaucracy in decision-making.
Enhanced alignment between product functions and user expectations.
Decreased interaction with potential users.
Focus on technology over user experience.

11. Question

What role do stakeholders play in the Agile Design Thinking process?

They are excluded to simplify the process.
They provide essential insights during the testing phase only.
They collaborate throughout the process to ensure the product meets business goals.
They are only involved during the budgeting phase.

12. Question

What is the primary role of the Scrum Master in a Scrum Team?

To provide customer support and handle external communications.
To manage the project budget and resource allocation.
To facilitate Scrum events and support the team in following Scrum practices.
To write user stories and ensure product quality.

13. Question

During a Sprint Review, what is the primary focus?

Reviewing the team's code quality and design.
Demonstrating the work completed and gathering feedback.
Planning the next Sprint and assigning tasks.
Discussing team roles and responsibilities for the next project.

14. Question

Which artifact is owned and maintained by the Product Owner?

Sprint Backlog.
Burndown Chart.
Work Breakdown Structure.
Increment.

15. Question

What is the purpose of a Sprint Retrospective?

To demonstrate the product to stakeholders.
To prepare the Product Backlog for the next Sprint.
To reflect on the past Sprint and plan improvements for the next Sprint.
To assign tasks to team members for the upcoming Sprint.

16. Question

Which statement best describes the concept of an Increment in Scrum?

It is a partial piece of work that needs further integration.
It is a fully functioning slice of the product that adds to previously completed work.
It is a temporary layout of work expected to be completed in the future.
It is a detailed plan of tasks that the team hopes to complete in the next Sprint.

17. Question

How often should the Daily Scrum occur?

Once at the start of each Sprint.
Weekly.
Daily, as it is a daily planning meeting to inspect progress towards the Sprint Goal.
At the discretion of the Scrum Master.

18. Question

What is the maximum recommended size for a Scrum Team?

5 members.
7 members.
10 members.
25 members.

19. Question

Which of the following best describes the role of the Product Owner?

Manages the Scrum process and resolves impediments.
Writes code and fixes bugs.
Maximizes the value of the product resulting from the work of the Development Team.
Ensures that the project is under budget and on time.

20. Question

What is the outcome expected from the Sprint Planning meeting?

A detailed list of the product features desired by stakeholders.
A set of completed product features ready for deployment.
A Sprint Goal and a plan for the Sprint that includes the Sprint Backlog.
Final product release and project closure documentation.

21. Question

What is the primary purpose of Kanban in Agile development?

To manage the project budget.
To facilitate continuous delivery and improvement.
To assign specific roles to team members.
To schedule and plan releases.

22. Question

Which of the following is NOT a core practice of Kanban?

Visualizing the workflow.
Limiting work in progress.
Maximizing resource utilization.
Managing flow.

23. Question

What does limiting work in progress (WIP) in Kanban help with?

Increasing the number of tasks to be done.
Reducing multitasking and focusing on work completion.
Planning future projects.
Allocating resources to projects.

24. Question

How does Kanban differ primarily from Scrum?

Kanban requires sprints; Scrum does not.
Kanban focuses on time-boxed delivery; Scrum focuses on continuous flow.
Kanban emphasizes continuous flow without predefined iterations; Scrum uses fixed-length iterations.
Kanban mandates daily stand-up meetings; Scrum does not.

25. Question

What is a Kanban board used for?

To display project budgets and costs.
To visualize the work and workflow of a team.
To assign tasks to team members.
To schedule product releases.

26. Question

Which Kanban concept involves adjusting the process based on what the team learns?

Management reviews.
Continuous integration.
Kaizen.
Product ownership.

27. Question

What role does the Kanban card or User Story play in a Kanban system?

It is used to schedule meetings.
It represents a piece of work in the workflow.
It is used to evaluate employee performance.
It dictates the strategic direction of the project.

28. Question

Which of these is a benefit of using Kanban?

It eliminates the need for project management.
It allows for fixed delivery dates for products.
It provides flexibility and improves efficiency by reducing wasted time.
It strictly defines team roles and responsibilities.

29. Question

In Kanban, what does the term ‘pull system’ refer to?

Team members pull tasks from the backlog as capacity allows.
The project manager assigns tasks to team members.
Customers pull products as needed, dictating the workload.
Software automatically assigns tasks to optimize workflow.

30. Question

How should teams handle a bottleneck discovered through a Kanban board?

Increase the WIP limits to push more work through the bottleneck.
Ignore the bottleneck so that it goes away.
Analyze and address the cause of the bottleneck to improve flow.
Remove the task causing the bottleneck from the board.

31. Question

What is the main goal of implementing Kanban at the enterprise level?

To standardize one methodology across all teams.
To increase the size of all teams.
To improve the overall flow and efficiency across multiple teams.
To enforce strict reporting and managerial controls.

32. Question

Which of the following is NOT typically a focus of enterprise-level Kanban?

Enhancing individual performance reviews.
Reducing cycle times across processes.
Managing dependencies between different teams.
Aligning multiple workflows to improve delivery.

33. Question

How does Kanban for Enterprise help manage work across multiple teams?

By implementing fixed-length sprints across all teams.
By visualizing work at various levels to identify bottlenecks.
By assigning specific tasks to specific teams permanently.
By requiring all teams to work synchronously on the same tasks.

34. Question

What is a service delivery review in the context of Enterprise Kanban?

A meeting to evaluate the personal performance of team members.
A regular assessment of the flow and quality of work between interdependent teams.
A customer-facing update on product features.
A financial review of the cost-effectiveness of Kanban practices.

35. Question

What is the primary purpose of using a Cumulative Flow Diagram (CFD) in Enterprise Kanban?

To visualize project schedules and individual task durations.
To identify bottlenecks and understand work-in-progress at various stages.
To calculate the total cost of completed projects.
To track individual team members' performance and productivity.

36. Question

Why is feedback particularly important in Enterprise Kanban?

It helps in promoting the personal achievements of team members.
It ensures that learning and improvements are continuously integrated across teams.
It is only used for annual performance evaluations.
It determines the pay scale for employees based on their feedback scores.

37. Question

How does Enterprise Kanban typically handle change management?

By using static processes that resist changes to ensure consistency.
By frequently changing the team structure to fit the project needs.
By encouraging incremental changes and continuous improvement.
By focusing solely on immediate customer feedback and demands.

38. Question

How does managing flow differ from managing resources in Enterprise Kanban?

Managing flow focuses on maximizing resource usage; managing resources focuses on speed.
Managing flow emphasizes smooth movement of work across systems; managing resources deals with optimal allocation and utilization.
Managing flow is about reducing team sizes; managing resources is about increasing output.
There is no difference in Kanban; both terms mean the same thing.

39. Question

What might trigger a risk review in Enterprise Kanban?

Scheduled project milestones only.
Detection of significant deviations in workflow or critical blockages.
Only financial risks are reviewed in Enterprise Kanban.
Annual strategic planning meetings.

40. Question

In Enterprise Kanban, how is the concept of ‘scaling’ typically approached?

By increasing the number of Kanban boards linearly with team size.
Through careful coordination and integration of Kanban systems at various operational levels.
By adopting stricter project management methodologies.
Scaling is discouraged in Enterprise Kanban.

41. Question

What is the primary goal of Hybrid Agile Development?

To replace traditional methodologies entirely with Agile practices.
The primary goal of Hybrid Agile Development is to integrate different development methodologies, optimizing workflow efficiency and adaptability across projects by addressing and resolving bottlenecks.
To enforce strict Agile practices across all departments.
To isolate Agile practices within specific teams.

42. Question

Which of the following best describes the benefit of Hybrid Agile Development?

Reduces the need for communication across different teams.
Allows for the strict application of a single methodology.
Enables flexibility and responsiveness by integrating various methodologies.
Promotes the use of Waterfall methodology over Agile.

43. Question

How does Hybrid Agile Development typically handle project documentation requirements?

By eliminating all documentation in favor of verbal communication.
By maintaining traditional comprehensive documentation standards.
Hybrid Agile Development tailors' documentation to the specific needs of each project and methodology, aiming to minimize documentation while ensuring it is adequate for project success.
By using only automated documentation tools.

44. Question

In a Hybrid Agile environment, how are changes in project scope typically managed?

Changes are discouraged and rarely accepted.
Through flexible adaptation and iterative reassessment.
Only through high-level management approval.
Scope changes are managed strictly as per Waterfall practices.

45. Question

What is a key challenge in implementing Hybrid Agile Development?

Too much consistency in project management methodologies.
Difficulty in integrating different methodologies and practices.
Overemphasis on speed over quality.
Lack of need for managerial oversight.

46. Question

Which tool or technique is most beneficial in a Hybrid Agile environment for managing workflow across different methodologies?

Gantt charts exclusively.
Enterprise Kanban boards.
Waterfall schedules only.
No tools are needed; informal agreements suffice.

47. Question

Why is communication particularly important in a Hybrid Agile environment?

It is only necessary during the planning phases.
Effective communication is crucial in a Hybrid Agile environment to ensure that output flow from different methodologies is balanced to maximize needed dependency alignment.
Communication is not emphasized in Hybrid Agile environments.
To document decisions for external audits only.

48. Question

How are team roles defined in a Hybrid Agile environment?

Roles are rigidly defined and do not overlap.
Roles are flexible, often overlapping to enhance collaboration and efficiency.
Roles are undefined and chosen spontaneously.
All team members perform the same roles.

49. Question

What is the impact of a well-implemented Hybrid Agile Development strategy on time-to-market for products?

Significantly increases time-to-market due to complexity.
Has no impact on time-to-market.
Reduces time-to-market by optimizing workflows and reducing bottlenecks.
Time-to-market is extended to ensure compliance with traditional practices.

50. Question

How is leadership typically structured in a Hybrid Agile environment?

Centralized with one leader making all decisions.
Decentralized with leaders facilitating team autonomy and integration of practices.
Leadership roles are eliminated in favor of self-managing teams.
Each methodology retains a separate and uncoordinated leadership structure.

51. Question

What is the primary focus of Agile Architecture within Agile methodologies?

Ensuring that architecture remains unchanged throughout the project.
Developing a one-time architectural plan that all teams follow.
Adaptive, iterative architectural enhancements aligned with evolving project needs.
Prioritizing documentation over implementation.

52. Question

How does Agile Architecture differ from traditional architecture approaches?

Agile Architecture discourages change and focuses on long-term planning.
It emphasizes flexibility and responsiveness to changes in product requirements.
It relies solely on initial detailed architectural designs.
It does not incorporate feedback loops.

53. Question

Which of the following best describes a key benefit of Agile Architecture?

It extends project timelines due to continuous redesign.
It reduces the need for stakeholder involvement.
It supports rapid adaptation to new technologies and business goals.
It focuses on complete upfront designs before development begins.

54. Question

What role does feedback play in Agile Architecture?

Feedback is considered only at the project's completion.
Regular feedback is integral for iterative improvements in the architectural design.
Feedback is discouraged to maintain the original architecture.
It is used to penalize teams for architectural flaws.

55. Question

In Agile Architecture, how are architectural decisions typically made?

Based solely on the preferences of senior architects.
Through a collaborative process involving cross-functional teams.
Decisions are predefined in the project scope and not revisited.
Randomly, without any strategic planning.

56. Question

Which tool or technique is often used in Agile Architecture to manage complexity?

Rigid adherence to initial architectural blueprints.
Ignoring stakeholder feedback to simplify designs.
Modular design and microservices architecture.
Sole reliance on one type of technology irrespective of project needs.

57. Question

What is the primary goal of integrating Agile practices with DevOps?

To reduce the frequency of software releases.
To separate development and operations teams.
To enhance collaboration and streamline workflows between development and operations.
To increase the use of manual processes in software development.

58. Question

Which of the following best defines Continuous Integration in DevOps?

A practice that requires developers to integrate code into a shared repository once per month.
The process of automating the build and testing of code every time a team member commits changes.
A strategy where code integration is performed manually to ensure quality.
Integrating customer feedback at the end of the project.

59. Question

In Agile DevOps, what role does Continuous Delivery play?

It ensures that code can be deployed to production at any time.
It extends the development phase to capture more user feedback.
It prevents frequent code deployments to avoid risks.
It is used to discourage changes in the production environment.

60. Question

Which tool is commonly used in DevOps to automate the deployment process?

Jenkins.
Microsoft Word.
Adobe Photoshop.
AutoCAD.

61. Question

How does Test Automation benefit Agile DevOps practices?

It increases the need for manual testing.
It decreases software quality by rushing releases.
It enables frequent and reliable software updates by automating testing processes.
It ensures that developers have less involvement in the testing process.

62. Question

What is the primary purpose of Agile Scaling?

To decrease the speed of delivery.
To manage larger product development or product portfolios efficiently.
To reduce the number of teams in an organization.
To implement traditional management styles in Agile environments.

63. Question

Which scaling framework(s) emphasizes the alignment of Agile teams with business goals and large solutions?

Waterfall
FAST Agile (Flow Adaptive Scaling Technology) & Nexus
Six Sigma
PRINCE2

64. Question

What is a key benefit of using Competitive Prioritization in Agile Scaling?

It delays decision-making to ensure more information is available.
Competitive prioritization in Agile scaling maximizes value by reducing low-value work and enhancing efforts that align with strategic objectives.
It encourages teams to work in silos.
It reduces the importance of stakeholder feedback.

65. Question

In the context of Agile Scaling, what is meant by ‘load balancing’?

Distributing work evenly across teams to manage capacity effectively.
Removing all processes to speed up delivery.
Focusing solely on the most important tasks.
Balancing the company's financial books.

66. Question

Which role is critical for integrating security practices in Agile Scaling?

Agile Security Director.
Agile Financial Analyst.
Agile Legal Advisor.
Agile Catering Manager.

67. Question

How does Service Level Agreement (SLA) play a role in Agile Scaling?

By ignoring customer needs and focusing only on development speed.
By providing a formalized approach to managing expectations and delivery timelines.
By limiting team communication to reduce distractions.
By enforcing a strict no-change policy after project commencement.

68. Question

What is one of the responsibilities of the Agile HR Director in an Agile Scaling environment?

To reduce the workforce as much as possible.
To ensure HR practices align with Agile values and support scalability.
To ignore team culture and focus only on individual performance.
To maintain traditional HR practices without adaptation.

69. Question

Why is Continuous Feedback important in Agile Scaling?

It discourages teams from making any changes to their processes.
It helps teams to continuously learn and improve their practices.
It ensures that teams do not communicate with each other.
It focuses on punishing teams for mistakes.