CSE 110 EVALUATION 2026 EXAM TEST
QUESTIONS AND ANSWERS SURE A+
✔✔Tuckman team stages: Norming - ✔✔Team creates norms, communication patterns,
workflows, roles, and shared expectations.
✔✔Tuckman team stages: Performing - ✔✔Team works effectively, communicates well,
handles conflict, and produces quality work.
✔✔Tuckman team stages: Adjourning - ✔✔Team disbands, hands off knowledge,
reflects, documents, and closes work.
✔✔Communication graph - ✔✔Team members are nodes; communication paths are
edges. More people means more coordination cost.
✔✔Two-pizza rule - ✔✔Team should be small enough to be fed by two pizzas;
shorthand for keeping teams manageable.
✔✔Conway's Law - ✔✔Software architecture tends to mirror the organization's
communication structure. Bad architecture may reflect bad team/org structure.
✔✔Bus factor - ✔✔How many people can disappear before the project is in danger. A
bus factor of 1 is bad because only one person knows a critical thing.
, ✔✔Specialist team - ✔✔People have distinct roles like frontend, backend, design,
testing. Higher expertise but more bus-factor risk.
✔✔Generalist team - ✔✔Everyone does similar work. Easier substitution but maybe
less depth/quality.
✔✔Psychological safety - ✔✔Feeling safe to ask questions, admit mistakes, disagree,
and share concerns without punishment. The reading says this is the most important
team factor.
✔✔Groupthink - ✔✔Team avoids disagreement and critical thinking, leading to poor
decisions.
✔✔Hero unit syndrome - ✔✔One person takes on too much, becomes overloaded, and
creates team risk.
✔✔Job security via obscurity - ✔✔Someone hides knowledge so they stay necessary;
bad for the team.
✔✔5 factors of high-performing teams - ✔✔Psychological safety, dependability,
structure and clarity, meaning of work, and impact of work.
✔✔Most important factor of high-performing teams - ✔✔Psychological safety because
without it, people hide mistakes, avoid asking questions, and do not share risks early.
✔✔User-Centered Design (UCD) - ✔✔Designing around real users and their needs, not
around the developer's assumptions or favorite technology.
✔✔Persona - ✔✔A representative user profile. Useful, but can become a stereotype if
done badly.
✔✔User story - ✔✔Agile-style requirement: "As a ___, I want to ___, so that ___."
✔✔Customer journey map - ✔✔Shows the user's full experience over time, including
offline/contextual steps.
✔✔Wireframe - ✔✔Rough layout/design sketch. Should often start low-fidelity before
"pretty pixels."
✔✔Observation - ✔✔Watching users interact with something to learn real behavior.
✔✔Interview - ✔✔Asking users questions, ideally non-leading and open-ended.
QUESTIONS AND ANSWERS SURE A+
✔✔Tuckman team stages: Norming - ✔✔Team creates norms, communication patterns,
workflows, roles, and shared expectations.
✔✔Tuckman team stages: Performing - ✔✔Team works effectively, communicates well,
handles conflict, and produces quality work.
✔✔Tuckman team stages: Adjourning - ✔✔Team disbands, hands off knowledge,
reflects, documents, and closes work.
✔✔Communication graph - ✔✔Team members are nodes; communication paths are
edges. More people means more coordination cost.
✔✔Two-pizza rule - ✔✔Team should be small enough to be fed by two pizzas;
shorthand for keeping teams manageable.
✔✔Conway's Law - ✔✔Software architecture tends to mirror the organization's
communication structure. Bad architecture may reflect bad team/org structure.
✔✔Bus factor - ✔✔How many people can disappear before the project is in danger. A
bus factor of 1 is bad because only one person knows a critical thing.
, ✔✔Specialist team - ✔✔People have distinct roles like frontend, backend, design,
testing. Higher expertise but more bus-factor risk.
✔✔Generalist team - ✔✔Everyone does similar work. Easier substitution but maybe
less depth/quality.
✔✔Psychological safety - ✔✔Feeling safe to ask questions, admit mistakes, disagree,
and share concerns without punishment. The reading says this is the most important
team factor.
✔✔Groupthink - ✔✔Team avoids disagreement and critical thinking, leading to poor
decisions.
✔✔Hero unit syndrome - ✔✔One person takes on too much, becomes overloaded, and
creates team risk.
✔✔Job security via obscurity - ✔✔Someone hides knowledge so they stay necessary;
bad for the team.
✔✔5 factors of high-performing teams - ✔✔Psychological safety, dependability,
structure and clarity, meaning of work, and impact of work.
✔✔Most important factor of high-performing teams - ✔✔Psychological safety because
without it, people hide mistakes, avoid asking questions, and do not share risks early.
✔✔User-Centered Design (UCD) - ✔✔Designing around real users and their needs, not
around the developer's assumptions or favorite technology.
✔✔Persona - ✔✔A representative user profile. Useful, but can become a stereotype if
done badly.
✔✔User story - ✔✔Agile-style requirement: "As a ___, I want to ___, so that ___."
✔✔Customer journey map - ✔✔Shows the user's full experience over time, including
offline/contextual steps.
✔✔Wireframe - ✔✔Rough layout/design sketch. Should often start low-fidelity before
"pretty pixels."
✔✔Observation - ✔✔Watching users interact with something to learn real behavior.
✔✔Interview - ✔✔Asking users questions, ideally non-leading and open-ended.
