-
Apply communication and continuous-improvement practices to collaborative work
Assessment Strategies
Written Product, Self-Assessment
Criteria
Communicate ideas clearly using language and visuals suited to the audience and context
Apply active-listening techniques to clarify information and assumptions
Address disagreement by focusing on the task, evidence, and shared goal
Identify team-development dynamics that affect collaboration
Analyze completed work to identify patterns in how the work was approached
Formulate a specific improvement and identify evidence that can be used to evaluate its effect
-
Apply Design Thinking to identify user needs
Assessment Strategies
Drawing/Illustration, Written Product
Criteria
Gather and organize evidence about a user or stakeholder experience
Distinguish observed needs from assumptions and proposed solutions
Represent user evidence using an empathy map or comparable method
Generate multiple interpretations or directions before narrowing
Select a problem or direction supported by available evidence
-
Improve workflow using Lean and Kanban
Assessment Strategies
Written Product, Skill Demonstration
Criteria
Map the steps of a workflow in the order work occurs
Identify and classify waste using Lean concepts
Analyze flow for waiting, excess work in progress, batching, or bottlenecks
Visualize work using a Kanban board
Apply a work-in-progress limit to control active work
Propose changes that improve flow or reduce waste
-
Plan project work using vision, strategy, and work decomposition
Assessment Strategies
Drawing/Illustration, Written Product
Criteria
Distinguish vision, goals, strategy, and tactics
Align project decisions with goals and constraints
Construct a hierarchical Work Breakdown Structure
Organize major and supporting deliverables into logical levels
Use deliverable-based labels rather than activity-based labels
Apply the 100 Percent Rule to represent project scope
-
Prepare Agile work for readiness
Assessment Strategies
Written Product, Scenario Response
Criteria
Write user stories that identify a user, need, and value
Organize work into levels such as themes, epics, and stories
Apply INVEST principles to evaluate or improve user stories
Split work into smaller, independently valuable items when needed
Write verifiable acceptance criteria
Establish a Definition of Done that applies across related work
Evaluate backlog items for refinement and readiness before planning
Relate Scrum accountabilities to decisions about product value, process, and delivery
-
Evaluate Agile work for effort and priority
Assessment Strategies
Written Product, Scenario Response
Criteria
Compare work using relative rather than time-based estimates
Apply Fibonacci-based story points to estimate effort
Consider complexity, uncertainty, and amount of work when estimating
Explain significant differences in estimates to build shared understanding
Prioritize work using available information about value, effort, risk, or dependencies
Reprioritize work when new evidence or conditions change
-
Plan iterative work based on goals, capacity, dependencies, and change
Assessment Strategies
Written Product
Criteria
Formulate an outcome-focused Sprint Goal
Determine available capacity for a Sprint
Use historical velocity as planning evidence rather than a guarantee
Select work that fits the Sprint Goal and available capacity
Identify dependencies, risks, and uncertainty that may affect the plan
Evaluate requests for new work against existing commitments
Adjust the plan while communicating scope and tradeoffs
-
Analyze delivery flow using CI/CD principles
Assessment Strategies
Written Product
Criteria
Distinguish continuous integration, continuous delivery, and continuous deployment
Map a repeating workflow to stages of a development and delivery pipeline
Identify queues or bottlenecks that slow work
Propose changes that reduce bottlenecks
Apply smaller batch sizes to improve flow and feedback
Explain how delivery feedback can change subsequent work
-
Analyze project progress
Assessment Strategies
Drawing/Illustration, Written Product
Criteria
Construct a burn-up or burn-down chart from project data
Label time, work, scope, and progress data accurately
Interpret progress patterns shown by the chart
Identify changes in scope and their effect on the chart
Compare information communicated by burn-up and burn-down charts
Distinguish velocity from completed progress
-
Evaluate work quality and direction using evidence
Assessment Strategies
Written Product, Scenario Response, Self-Assessment
Criteria
Identify and classify defects by type
Evaluate defect severity and determine a triage response
Determine whether work meets its Definition of Done and is safe to build upon
Classify technical debt using a decision framework
Determine whether new evidence requires a fix, replan, reprioritization, pivot, or stop decision
Justify changes in direction using evidence
Select an Agile practice that fits a given problem or scenario