Which IT roles should be interested in requirements for solution adoption?

Question

Options

• AThe Project Manager and Executive Sponsor
• BThe lead application developer and the testing team leader
• CApplications, infrastructure, and project management professionals
• DThe training lead and a user design subject expert

• A
  5% (1)
• B
  5% (1)
• C
  89% (17)

Explanation

Solution adoption requires broad organizational buy-in, so requirements for it span multiple disciplines - applications teams ensure the solution fits user workflows, infrastructure teams confirm it can be deployed and sustained, and project management professionals coordinate timelines, resources, and stakeholder alignment. C is correct because all three groups have distinct but equally essential stakes in whether a solution is actually adopted.

Why the distractors fall short:

• A (Project Manager + Executive Sponsor) is too narrow - executives set vision but aren't hands-on with adoption requirements; project managers alone can't account for technical feasibility.
• B (Lead developer + testing team leader) focuses only on build/QA phases, missing the infrastructure and management dimensions critical to rollout success.
• D (Training lead + user design expert) addresses end-user experience but ignores the technical and organizational layers that enable adoption in the first place.

Memory tip: Think of solution adoption as a three-legged stool - Apps (does it work for users?), Infrastructure (can we run it?), and Project Management (can we deliver it?) - all three legs are needed or the stool falls over.

No community discussion yet for this question.