Agile Scrum Developer Certification

Trace the evolution of software development processes from waterfall and spiral models to agile and lean approaches, driven by the information age, globalization, and iterative development of minimum viable products.

Advance agile thinking by embracing the manifesto's core values—individuals and interactions over processes and tools, working software over documentation, customer collaboration, and responding to change—while planning frequently amid uncertainty.

Explain empiricism and empirical process control with a Google Maps example, showing decisions based on observation and evidence. Maintain a constant team, sprint length, and work type to improve flow.

Explain the three pillars of scrum—transparency, inspection, and adaptation—and how lean thinking uses muda, mura, and muri. Emphasize aligning changes with sprint goal and dropping low-priority work to prevent overburden.

Describe how a methodology provides a rigid, documented what-and-how approach, exemplified by waterfall and the PMBoK, while a framework offers loosely coupled guidelines based on values and why.

Explore the scrum framework, its roles—product owner, development team, and scrum master—and the sprint planning, daily scrum, sprint review, and sprint retrospective, plus product backlog and sprint backlog.

Explore the Scrum values of commitment, courage, focus, openness, and respect alongside the pillars of transparency, inspection, and adaptation, to build trust and deliver value within an agile team.

Own and manage the sprint backlog, a dynamic subset of the product backlog created in sprint planning and updated during the sprint to deliver sprint goal through transparent, small tasks.

Learn how a product increment represents the sum of work completed in a sprint and delivers value through a potentially shippable, fully functional feature set.

Prioritize the product backlog as a living, ordered list owned by the product owner to maximize value, using deep criteria and methods like MoSCoW and wsjf to guide sprint planning.

Define and agree on the definition of done to ensure releasable increments. Distinguish it from acceptance criteria and address technical debt to maintain high-quality software.

Explore how the definition of ready prepares user stories for sprint planning with acceptance criteria, dependencies, and team capacity, and how it differs from the definition of done.

Understand how sprints create a time-boxed iteration with a cross-functional team to deliver a potentially shippable product increment and maintain cadence, transparency, and accountability.

Explore how product backlog refinement, or grooming, continually reviews and prioritizes backlog items, with the product owner and development team estimating and detailing work to ready items for sprint planning.

Coordinate the daily 15-minute scrum to plan the next 24 hours, monitor progress on the sprint board, and remove impediments with the development team, scrum master, and product owner.

Learn to run a timeboxed sprint planning session aligning the product backlog with the sprint backlog and sprint goal. Estimate capacity and craft a plan to deliver a product increment.

The sprint review is a collaborative scrum event at sprint end that inspects the increment, gathers stakeholder feedback, and adapts the product backlog toward a potentially shippable increment.

Facilitate a time-boxed sprint retrospective to inspect performance, identify improvements for people, processes, and tools, and create actionable plans with owners and timelines for continuous improvement within the scrum team.

Coordinate agile delivery by writing clear PBIs, estimating effort, refining through backlog grooming, and validating with stakeholders via testing and acceptance criteria.

Master MoSCoW, value-based, and risk-based prioritization to guide project and sprint planning, focusing on must-have features, maximizing value, mitigating risks, and stakeholder-aligned, data-driven decisions.

Refine and estimate PBIs using planning poker, story points, and Fibonacci sequence to improve accuracy, prioritization, and project predictability by leveraging historical data.

Transform PBIs into increments of value by breaking them into tasks, implementing with quality, and validating through unit, integration, and user acceptance tests, with continuous integration, deployment, and stakeholder feedback.

Discover how to run an effective sprint planning meeting: define the sprint goal, review and estimate backlog items, create and commit to a dynamic sprint backlog, and align the team.

Create and maintain a dynamic sprint backlog by breaking down user stories, estimating effort, and assigning tasks to team members, with updates and stand-ups guiding progress toward the sprint goal.

Plan capacity with the scrum team to balance sustainable workloads and prevent burnout across sprints, using velocity, availability, and holidays.

Master forecasting for the sprint by refining the product backlog, estimating story points with planning poker, and using velocity and a burndown chart to guide collaborative sprint planning.

Learn how velocity measures a team's sprint capacity in story points to forecast timelines, set realistic sprint goals, and communicate progress with stakeholders.

Learn how the daily scrum coordinates the team, plans the next 24 hours, and adapts the sprint backlog to achieve the sprint goal in a 15-minute, transparent, collaborative stand-up.

Master daily scrum meetings to synchronize the team toward the sprint goal within a 15-minute timebox. Promote transparency and adaptation by addressing impediments, updating the sprint backlog, and encouraging participation.

Synchronize work with teammates through clear communication channels, collaborative planning, cross-functional collaboration, and transparency, then integrate code regularly and test to maintain quality and momentum.

Identify and remove impediments promptly to maintain team efficiency and accelerate project delivery. Collaborate with team members and Scrum Master to address bottlenecks, encourage open communication, and implement incremental improvements.

Harness the Daily Scrum to drive progress, collaboration, and accountability by synchronizing work, identifying blockers, and adapting tasks to sprint goals using digital tools.

In sprint reviews, showcase a fully functional increment to stakeholders, gather feedback, validate the definition of done, and align the product backlog for future sprints.

Plan and conduct a sprint retrospective to reflect on the sprint, identify improvements, address blockers, and implement action items for continuous team performance in Scrum.

Learn to design and facilitate retrospectives in scrum by creating psychological safety, time boxing phases, and using visual tools to turn data gathering and insights into action.

Empower self-organizing scrum teams to make autonomous decisions and own their work. Align goals with sprint planning, backlog grooming, and regular retrospectives to improve collaboration and performance.

Apply architectural and design principles within agile teams to balance flexibility with architectural integrity, using evolutionary architecture, TDD, and ci/cd to deliver value with simplicity and maintainability.

drive technical excellence in agile teams by practicing test-driven development, automated testing, code reviews, pair programming, refactoring, and continuous learning to deliver high-quality, maintainable software.

Refactor code without changing external behavior to improve readability, maintainability, and performance within agile development; apply small incremental steps, red-green-refactor in TDD, and techniques like extract method, rename variables.

Learn how test driven development writes tests before code and follows a cycle of failing test, minimal code, and refactoring to deliver robust, maintainable software with early bug detection.

Embrace continuous integration to automatically build, test, and integrate code in a single repository, delivering fast feedback, early issue detection, and a stable, high-quality software base through ci/cd practices.

Learn to deliver a great sprint demo using a universal three-step outline—beginning, middle, end—preview, demonstrate, and summarize with clear context, while handling questions and backup plans.