10152131
Agile Practices
Course Information
Description
Apply Agile, Lean, and Design Thinking practices to collaborative project work. Identify user needs, organize and define work, estimate and prioritize effort, plan iterative delivery, visualize workflow and progress, evaluate quality, and adapt plans using evidence, feedback, and continuous improvement.
Total Credits
3
Prior Learning Assessment
- Transfer Credit (includes Certifications)
Course Competencies (Course Outcomes)
-
Apply communication and continuous-improvement practices to collaborative workAssessment StrategiesWritten Product, Self-AssessmentCriteriaCommunicate ideas clearly using language and visuals suited to the audience and contextApply active-listening techniques to clarify information and assumptionsAddress disagreement by focusing on the task, evidence, and shared goalIdentify team-development dynamics that affect collaborationAnalyze completed work to identify patterns in how the work was approachedFormulate a specific improvement and identify evidence that can be used to evaluate its effect
-
Apply Design Thinking to identify user needsAssessment StrategiesDrawing/Illustration, Written ProductCriteriaGather and organize evidence about a user or stakeholder experienceDistinguish observed needs from assumptions and proposed solutionsRepresent user evidence using an empathy map or comparable methodGenerate multiple interpretations or directions before narrowingSelect a problem or direction supported by available evidence
-
Improve workflow using Lean and KanbanAssessment StrategiesWritten Product, Skill DemonstrationCriteriaMap the steps of a workflow in the order work occursIdentify and classify waste using Lean conceptsAnalyze flow for waiting, excess work in progress, batching, or bottlenecksVisualize work using a Kanban boardApply a work-in-progress limit to control active workPropose changes that improve flow or reduce waste
-
Plan project work using vision, strategy, and work decompositionAssessment StrategiesDrawing/Illustration, Written ProductCriteriaDistinguish vision, goals, strategy, and tacticsAlign project decisions with goals and constraintsConstruct a hierarchical Work Breakdown StructureOrganize major and supporting deliverables into logical levelsUse deliverable-based labels rather than activity-based labelsApply the 100 Percent Rule to represent project scope
-
Prepare Agile work for readinessAssessment StrategiesWritten Product, Scenario ResponseCriteriaWrite user stories that identify a user, need, and valueOrganize work into levels such as themes, epics, and storiesApply INVEST principles to evaluate or improve user storiesSplit work into smaller, independently valuable items when neededWrite verifiable acceptance criteriaEstablish a Definition of Done that applies across related workEvaluate backlog items for refinement and readiness before planningRelate Scrum accountabilities to decisions about product value, process, and delivery
-
Evaluate Agile work for effort and priorityAssessment StrategiesWritten Product, Scenario ResponseCriteriaCompare work using relative rather than time-based estimatesApply Fibonacci-based story points to estimate effortConsider complexity, uncertainty, and amount of work when estimatingExplain significant differences in estimates to build shared understandingPrioritize work using available information about value, effort, risk, or dependenciesReprioritize work when new evidence or conditions change
-
Plan iterative work based on goals, capacity, dependencies, and changeAssessment StrategiesWritten ProductCriteriaFormulate an outcome-focused Sprint GoalDetermine available capacity for a SprintUse historical velocity as planning evidence rather than a guaranteeSelect work that fits the Sprint Goal and available capacityIdentify dependencies, risks, and uncertainty that may affect the planEvaluate requests for new work against existing commitmentsAdjust the plan while communicating scope and tradeoffs
-
Analyze delivery flow using CI/CD principlesAssessment StrategiesWritten ProductCriteriaDistinguish continuous integration, continuous delivery, and continuous deploymentMap a repeating workflow to stages of a development and delivery pipelineIdentify queues or bottlenecks that slow workPropose changes that reduce bottlenecksApply smaller batch sizes to improve flow and feedbackExplain how delivery feedback can change subsequent work
-
Analyze project progressAssessment StrategiesDrawing/Illustration, Written ProductCriteriaConstruct a burn-up or burn-down chart from project dataLabel time, work, scope, and progress data accuratelyInterpret progress patterns shown by the chartIdentify changes in scope and their effect on the chartCompare information communicated by burn-up and burn-down chartsDistinguish velocity from completed progress
-
Evaluate work quality and direction using evidenceAssessment StrategiesWritten Product, Scenario Response, Self-AssessmentCriteriaIdentify and classify defects by typeEvaluate defect severity and determine a triage responseDetermine whether work meets its Definition of Done and is safe to build uponClassify technical debt using a decision frameworkDetermine whether new evidence requires a fix, replan, reprioritization, pivot, or stop decisionJustify changes in direction using evidenceSelect an Agile practice that fits a given problem or scenario