Advanced Agile & Scrum test (Advanced)
40 questions · 40 minutes · Free
Scaling Agile, flow metrics, continuous delivery and coaching teams.
Take the Advanced Agile & Scrum test
What it covers
- Scaling Agile with SAFe and LeSS
- Agile metrics: velocity and flow
- Agile and continuous delivery
- Agile retrospectives
- Agile coaching
Interview format
- Questions: 40 questions — 24 multiple choice, 16 multi-answer
- Time: 40 minutes, timed from the first question
- Difficulty: Advanced
- Skill area: Engineering practices
- Price: Free
Earn a certificate
The Advanced Agile & Scrum test is one of the 8 tests of the QA Automation Engineer: Advanced learning path. Pass it and the other 7 tests at 70% or more and readyforhires issues you a verifiable certificate in your name, with its own code and verify link to share or add to LinkedIn.
Sample questions
5 sample questions from the Advanced Agile & Scrum test, with the answers. Samples are taken out of the live test, so you will not meet these when you sit it.
Which scaling framework is known for being prescriptive, layered, and introducing constructs like the Agile Release Train (ART) and Program Increments (PI)?
- LeSS
- Scrum@Scale
- Nexus
- SAFe
Answer: D. SAFe
SAFe (Scaled Agile Framework) is a prescriptive, layered framework designed for scaling Agile practices across large organizations. It introduces constructs like the Agile Release Train (ART), Program Increments (PI), and events like PI Planning. LeSS (Large-Scale Scrum) is another scaling framework, but it is more lightweight and emphasizes a single Product Owner and shared Product Backlog across teams. SAFe is the correct answer here because it is more prescriptive and layered compared to LeSS, which is more principles-based and less prescriptive.
A LeSS team is encountering frequent delays and bottlenecks due to handoffs between different teams working on components of a feature. What is the most likely cause of this issue based on LeSS principles?
- The team is not following SAFe's PI Planning process correctly.
- The team is using a hybrid of SAFe and LeSS frameworks.
- The team is not adhering to the Definition of Done in Scrum.
- The team is using component teams instead of feature teams, leading to frequent handoffs and delays.
Answer: D. The team is using component teams instead of feature teams, leading to frequent handoffs and delays.
In LeSS, feature teams are preferred as they are responsible for end-to-end customer features, reducing dependencies and handoffs. Using component teams can lead to frequent handoffs and delays, which is a violation of LeSS principles.
Which of the following is a common mistake when implementing trunk-based development in an Agile and continuous delivery environment?
- Using long-lived feature branches to isolate complex changes before merging them into the main branch.
- Implementing automated testing and continuous integration to ensure code quality.
- Favoring small, incremental changes that are merged frequently into the main branch.
- Using feature toggles to manage the visibility of new features in production.
Answer: A. Using long-lived feature branches to isolate complex changes before merging them into the main branch.
Trunk-based development emphasizes short-lived branches and frequent integration into the main branch (trunk) to maintain a stable and up-to-date codebase. Using long-lived feature branches undermines this practice by introducing delays in integration, increasing the risk of conflicts, and reducing the ability to deliver changes continuously. This is a common mistake when implementing trunk-based development.
Which of the following statements accurately describes deployment frequency as a DORA metric?
- Deployment frequency is a quality metric that evaluates the stability of deployed changes.
- Deployment frequency is a metric that measures the time it takes to deploy changes to production.
- Deployment frequency is a DORA metric that measures how often changes are deployed to production, but it does not directly indicate the quality or stability of those deployments.
- Deployment frequency measures the number of features released in a sprint.
Answer: C. Deployment frequency is a DORA metric that measures how often changes are deployed to production, but it does not directly indicate the quality or stability of those deployments.
Deployment frequency is a DORA metric and measures how often changes are deployed to production, but it doesn't capture the quality or stability of the deployments. It is a measure of speed, not quality. The other options incorrectly associate deployment frequency with quality, stability, or the number of features released.
As an Agile coach, you notice that a team is struggling with collaboration and frequent miscommunication. Which of the following actions would best address this issue?
- Assign individual performance targets to each team member to increase accountability.
- Encourage the team to identify and address communication barriers through open dialogue and team-building exercises.
- Reduce the frequency of team meetings to minimize disruptions.
- Implement a new project management tool to streamline task tracking.
Answer: B. Encourage the team to identify and address communication barriers through open dialogue and team-building exercises.
Encouraging open dialogue and team-building exercises directly addresses communication barriers, which is a key aspect of fostering collaboration. Other options may focus on individual improvement or external factors, which are less directly related to enhancing team collaboration.
Frequently asked questions
- How many questions are in the Advanced Agile & Scrum test?
- 40 questions (24 multiple choice, 16 multi-answer), with 40 minutes to answer them.
- What does the Advanced Agile & Scrum test cover?
- Scaling Agile with SAFe and LeSS, Agile metrics: velocity and flow, Agile and continuous delivery, Agile retrospectives, Agile coaching.
- Is the Advanced Agile & Scrum test free?
- Yes. It is free to take with a readyforhires account.
- What level is the Advanced Agile & Scrum test?
- Advanced, in Engineering practices.