September 8, 2026 · 7 min read
TL;DR: Cross-functional appears in sixteen options in this bank and is keyed five times. One misreading produces most of the wrong answers: treating cross-functionality as something each individual must be. The bank's definition is explicit that it belongs to the team collectively, which holds every skill needed to take an item from idea to done without depending on an outside group, while individuals keep their own specialisms. Once you hold that, the keyed uses become predictable. Cross-functional structure is the answer to hand-offs and to key-person risk. It is not the answer to a cultural problem, a short-term skill need, or a training gap.
The phrase turns up in a lot of agile vocabulary questions, which makes it feel like a term to recognise rather than a structure with consequences. The consequences are what get tested.
Cross-functionality means the team as a unit can finish the work.
The bank asks which statement accurately describes agile teams, and the four options are close enough to be worth listing. Every member should be both cross-functional and self-organising. The team should collectively hold all the skills required to deliver the product on its own. The team should have complementary skills and organise the product backlog itself. The team should self-organise so as to acquire the skills needed to become cross-functional.
Keyed is the second, and the explanation states the rule that resolves the other three: cross-functionality is a property of the team as a whole, not of each person in it. The team collectively holds every skill needed to take an item from idea to done without depending on an outside group, while individuals still have their own specialisms.
That knocks out the first option, which imposes the property on individuals. It knocks out the third, which hands the team the backlog ordering that belongs to the product owner. And it knocks out the fourth, which describes the team acquiring skills it should have been staffed with.
The same idea appears under a different name. Asked which agile method makes quality everyone's responsibility by pooling skill sets and cutting reliance on outside inputs, the bank keys the whole-team approach, and explains that assembling a team holding every skill the work requires means an item can travel from idea to done without leaving the team. Quality becomes everyone's responsibility because there is no separate group to hand it to.
When the problem is a hand-off or a single point of failure.
The key-person record is the strongest. During a critical phase, the specialist designing a key component is unexpectedly placed on extended medical leave, and their tasks stall because they were the only one with the expertise. What proactive measure would have mitigated this? Keyed is building a cross-functional team and spreading the specialist's tasks across several members from the project's start.
The explanation names the exposure precisely: it was structural and predictable, because one person held expertise nobody else had, so any absence, whether leave, illness or resignation, stopped that work. The fix is structural to match. Spreading the work from the outset means knowledge transfers by doing rather than by being written down.
That last clause is what defeats the strongest distractor, which is maintaining thorough documentation for every project task. Documentation is not a bad idea, it just does not do the job here. A document describing a design decision does not make a second person able to make the next one.
The silo record is the other keyed use. A project manager on a hybrid delivery inherits a team organised into functional silos, communication between them is laborious, and delivery has slowed. Two answers are keyed: ask the people working on the project to self-organise into cross-functional teams, and use servant leadership to help the functional managers understand why cross-functional teams are needed.
Both halves matter, and the explanation says why. Reorganising people around the work removes the hand-offs slowing delivery, and because those people report to functional managers, the managers have to understand why the change is being made. Restructuring a team whose managers have not been brought along is not a fix, it is a fight.
It offers structure as the fix for problems that are not structural.
| Scenario in the bank | Cross-functional option offered | What is actually keyed |
|---|---|---|
| Which statement describes agile teams | Every member is cross-functional and self-organising | The team collectively holds all required skills |
| Specialist on medical leave, component stalled | Build a cross-functional team from the start | Build a cross-functional team from the start |
| Team organised into functional silos | Self-organise into cross-functional teams | That, plus servant leadership with the managers |
| Two-week need for expertise in another team | Dedicate the individual full-time to your team | A short matrixed loan agreed with their manager |
| Diverse team across several continents, wants unity | Cross-functional training on cultural differences | Encourage open communication, show confidence |
| Which locating approach helps a team perform | Cross-functional dispersion | Colocation |
| Analytics platform new to the technology landscape | Streamline cross-functional workflows | A precise needs analysis across business areas |
| Team, scrum master and PO disagree on a logo | Enlarge per the cross-functional team's majority | Leave it unchanged per the product owner |
The two-week record is the most instructive of the rejections. Your team needs expertise sitting in another team, but only for a two-week burst of design review before the next release. One option works with the managers to dedicate that individual full-time to your cross-functional team. Keyed is a short matrixed loan of their time for the review window, agreed with their manager.
The explanation gives a sizing principle worth carrying: the need here is bounded and short, not a standing gap in the team's own skill set, so the fix should be sized to match. It then concedes the distractor's logic before rejecting it. Permanently dedicating the person is the overcorrection a real silo calls for, but committing someone full-time to a two-week need wastes their time. Cross-functional structure is a remedy for a standing gap, not for a temporary one.
Common trap: reaching for cross-functional whenever a team has any kind of problem working together. The reforestation record is built on exactly that. A project manager oversees a diverse team spread across continents and wants to build unity, and one option runs cross-functional training on cultural differences. Keyed is encouraging open communication and showing confidence in the team's abilities. The explanation makes the diagnostic point: no misunderstanding has occurred, nothing has been misread and nobody has taken offence, so this is a question about how the team is led rather than about repairing a fault. Structure fixes hand-offs. It does not fix trust, and the bank flags that distractor by name rather than only marking it wrong.
In two vocabulary records, and both are worth recognising for their pattern rather than their content.
Asked which Agile Manifesto value concerns change and planning, one distractor offers cross-functional team members over executive buy-in. Keyed is responding to change over following a plan. The distractor borrows real agile vocabulary and arranges it into the Manifesto's X over Y shape, producing something that reads like a value statement and is not one. The bank uses this technique in a second Manifesto record too, where product owner interaction over scrum master delegation is offered and the explanation notes it borrows agile vocabulary but describes nothing the Manifesto states.
The logo record does something similar with authority. Most of the cross-functional team wants a logo enlarged twenty per cent and the scrum master wants ten, but the product owner is content as it is. Keyed is leaving it unchanged. Being cross-functional gives the team every skill needed to build the product. It does not give the team the right to decide what the product should be.
That is the boundary worth leaving with. Cross-functionality is about capability, not authority. It says the team can do the work without leaving the team; it says nothing about who decides what the work is.
Does every member of an agile team have to be cross-functional? No, and the bank tests this directly. Cross-functionality is a property of the team as a whole, not of each person in it: the team collectively holds every skill needed to take an item from idea to done without depending on an outside group, while individuals still have their own specialisms.
What is the cross-functional answer to key-person risk? Building the team so no single person is the only route to a critical component. When a specialist on extended medical leave leaves their component stalled, the bank keys spreading that work across several members from the project's start, because knowledge then transfers by doing rather than by being written down. Documenting every task is offered as the near miss.
How do you fix a team organised into functional silos? The bank keys two actions together: asking the people working on the project to self-organise into cross-functional teams, and using servant leadership to help the functional managers understand why the change is needed. Because those people report to functional managers, skipping the second action leaves the first without support.
Should you permanently move an expert into your team when you need their skill? Only if the gap is standing. The bank keys a short matrixed loan of the person's time agreed with their manager when the need is a two-week design review, and names permanently dedicating them as the overcorrection a real silo would call for, since committing someone full-time to a two-week need wastes their time.
PMP Practice's 2,141 questions are re-certified against PMBOK 8 and the July 2026 Exam Content Outline, and every wrong answer is explained, not just marked wrong, which is how a term you can define becomes a term you can apply under time pressure. Start the free 20-question sample — no card, no signup required to try it.
Does every member of an agile team have to be cross-functional?
No, and the bank tests this directly. Cross-functionality is a property of the team as a whole, not of each person in it: the team collectively holds every skill needed to take an item from idea to done without depending on an outside group, while individuals still have their own specialisms.
What is the cross-functional answer to key-person risk?
Building the team so no single person is the only route to a critical component. When a specialist on extended medical leave leaves their component stalled, the bank keys spreading that work across several members from the project's start, because knowledge then transfers by doing rather than by being written down. Documenting every task is offered as the near miss.
How do you fix a team organised into functional silos?
The bank keys two actions together: asking the people working on the project to self-organise into cross-functional teams, and using servant leadership to help the functional managers understand why the change is needed. Because those people report to functional managers, skipping the second action leaves the first without support.
Should you permanently move an expert into your team when you need their skill?
Only if the gap is standing. The bank keys a short matrixed loan of the person's time agreed with their manager when the need is a two-week design review, and names permanently dedicating them as the overcorrection a real silo would call for, since committing someone full-time to a two-week need wastes their time.