Scrum Developer

Explore the course structure and the Scrum Certified Developer exam, and learn the certification path and practical tools to start effectively for your scrum team.

Explore introductory level certifications such as the scrum developer and certified programs, and learn why this course serves as a prerequisite for advanced scrum and agile certifications.

Join an mentoring community of scrum and agile practitioners to share practices, ask questions about scrum use and cert prep, and log in to enter the group scrum/agile mentoring community.

Clarify why these scrum skills matter for your team and plan how to apply course knowledge to improve your organization's capabilities and performance.

Explore Bloom's taxonomy as a model for identifying skills, focusing on basic knowledge and comprehension with exercises to apply techniques that improve scrum team performance, including synthesis and evaluation.

Create a formal study schedule, dedicate focused time, and turn off distractions. Review sections as needed, set milestones, and revise your understanding as you gain skills.

Compare different scrum certification exams, outlining question counts, scoring rules, online proctoring, and durations for scrum developer, scrum master, and scrum product tracks.

Explore agile methodologies versus traditional project management, discover the benefits of scrum, learn six core scrum principles, and see how scrum leverages five key project aspects.

Learn key terms such as adaptation, Agile Manifesto, information radiators, inspection, portfolios, programs, projects, Scrum, guidance body, time boxing, transparency, and waterfall.

Explore the origins and key benefits of scrum, see how it scales for enterprise projects, and outline the essential aspects and processes that make scrum work.

Define how to plan, organize, motivate, and control resources and people to reach a specific goal. Initiate, design, execute, monitor, and close projects across methodologies like PMI, PRINCE2, and scrum.

Explore software development lifecycle methodologies and management tools to initiate, plan, execute, control, and deliver projects, while embracing agile approaches to manage changing requirements and regulatory shifts.

Explore traditional waterfall project management, locking down requirements and design architecture before development. Learn why rapid change in six-month projects undermines rigid plans and how to embrace flexible change management.

Explore how the Agile manifesto, published in 2001, shifts from waterfall to valuing individuals, working software, customer collaboration, and flexible response to change for business value.

Put the customer at the center by delivering working solutions and embracing change as a competitive advantage, while enabling frequent delivery through close collaboration between business and development teams.

Create sustainable spaces for regular face-to-face conversations, empower self-organizing cross-functional teams, and deliver working software that maximizes customer value.

Trace the rugby-inspired shift from baton-passing relay development to a team-based approach, emphasizing collaboration, self-organization, and empiricism in lightweight software development lifecycle management.

Adopt scrum to adapt to changing requirements and risks while maintaining transparent delivery. Gain continuous feedback, collective ownership, high trust, and sustainable high-velocity delivery of valuable software.

Scrum principles emphasize empirical process control, team self-organization, value-based product backlog prioritization, time-boxed meetings, and iterative development in two to four week cycles.

Aligns the scrum team's work with the highest business value by maintaining and grooming a prioritized product backlog that reflects evolving customer needs, risks, and dependencies as the environment changes.

Time boxing in scrum constrains meetings to fixed durations, boosting efficiency and value; sprints run two to four weeks with a 15-minute daily standup and time-boxed sprint planning.

Practice iterative development by breaking work into two week or four week sprints, prioritizing high value deliverables, and adapting to shifting requirements, risks, issues, and customer needs to deliver value.

Identify the five phases of a scrum project: initiation and planning with estimation, implementation, reviews in retrospect at the end of each sprint, and release to production.

Plan and estimate effort via user story workshops, write concise feature stories, identify required tasks and effort, then prioritize, approve estimates, and build the sprint backlog.

Implement focuses on turning user stories into deliverables, conducting daily stand-ups, and grooming the backlog to reflect change requests, risks, and priorities before the next sprint.

Conduct sprint reviews with the product owner and stakeholders to confirm completed user stories and gain buy-in. Hold sprint retrospectives to improve team processes and collaboration.

Coordinate and plan a release by ensuring shippable sprint outcomes are ready for production, align release and deployment with the organization, and capture lessons learned to strengthen future Scrum practices.

Explore the core concepts of Scrum, its benefits, and how it scales, along with its key principles and the 18 associated processes.

Explore how agile methods address overdocumentation and contracts by empowering collaborative teams to deliver working software, and how scrum enables inspectable, adaptable, scalable progress through empirical process control.

Explore how a business case drives scrum projects and shapes a project vision. Build a backlog with epics and user stories, plan sprints, and apply a definition of done.

Explore key scrum terms such as business case, the notion of done criteria, epix gap analyses, the 100 point method, jad sessions, kindo analysis, moskow analysis, persona, and user stories.

Define a coherent high-level project vision from the business case, focusing on cost value and business benefits. Identify the EPIX and user stories to form a value-ordered backlog.

Create a clear project vision by establishing vision meetings and using JAD sessions, Swad analyses, and gap analyses to produce the outputs of this process.

Define a concise project vision that aligns with the organization’s mission and vision, and explains how the future state delivers customer value, guiding resource allocation toward the north star.

Explore jazz sessions to elicit customer requirements with stakeholders, defining broad scope and objectives, and prioritizing how the solution delivers value through agile time-boxed JAD workshops.

Explore swot analysis to define the desired end state by weighing strengths and weaknesses against opportunities and threats, and learn to leverage strengths and mitigate risks.

Define the product owner's role in delivering business value by eliciting customer needs, prioritizing the backlog, and shaping a high-level project vision with a formal charter and budget.

Identify a scrum master as a servant leader who moderates and facilitates team interactions, coaches stakeholders, and removes roadblocks to help the team perform and deliver value to customers.

Identify stakeholders such as customers, users, sponsors, vendors, and the scrum guidance body, alongside core roles like product owner and scrum master, establishing transparency through sprint planning and reviews.

Identify the skills and capabilities needed to form the scrum team and understand how working together drives successful delivery in a scrum project.

Form a cross-functional, self-organizing scrum team that collaborates to deliver a potentially shippable increment each sprint, with independent thinking, self-motivation, and a small, six-to-ten person team.

Develop epic and persona epics to describe what customers might want from a solution, and examine how the solution drives value for a particular user.

Define epics in scrum as high-level, non-technical user goals that guide product backlog, rely on requirements elicitation with stakeholders, and break down into user stories with acceptance criteria.

Define epics and persona through Jim, a traveling instructor who needs expense reporting and reimbursement. Show how this use case reveals stakeholder value and morale in a real-world expense solution.

Identify changes in customer needs and generate outputs from developing epics. Outline aspects and personas, and highlight risks to address and mitigate through the project.

Identify must-have, should-have, could-have, and won't-have requirements using the moskow analysis to prioritize the product backlog.

Master paired comparisons to prioritize epics and user stories by comparing two items at a time, determining which has higher priority, and ordering them for Scrum Developer.

Apply the 100 point method to prioritize user stories by letting each user allocate up to 100 points across stories. The aggregated points drive backlog prioritization.

Coordinate ongoing release planning between the product owner and customer stakeholders to ensure sprint deliverables progressively deliver value for customers, moving from potentially shippable to live solutions.

Learn how Scrum delivers the highest value functionality early by coordinating release planning with the product owner and the team, aligning sprints with continuous deployment or release windows.

Define project vision, identify scrum master and stakeholders, form the scrum team, and collaborate with customers to identify epics and personas for a prioritized product backlog and release plan.

Learn to create user stories, estimate tasks, and populate a sprint backlog as a scrum team to approve estimates, commit to sprint work, and track progress.

Explore essential scrum terms such as acceptance criteria, sprint backlog, velocity, and story points, and practice planning poker, fist of five, sprint planning meetings, and the scrum board.

Use user group meetings to turn APIC information and personas into consumable user stories for inclusion in a sprint, with acceptance criteria that drive sprint or task planning.

Define and communicate objective acceptance criteria for each user story to determine the definition of done; the product owner sets criteria and the scrum master protects the sprint.

Link acceptance criteria and backlog updates to the outputs of writing user stories, mapping them to various personas to show how users carry out tasks and deliver business value.

Engage stakeholders early through user group meetings to align customers, business managers, and sponsors on the project vision, establish clear expectations, and secure buy-in to prevent rework.

Use planning poker with a deck of cards representing short, medium, and long effort to estimate user stories, discuss questions with the product owner, and reach consensus on effort.

Use the fist-to-five voting technique to gauge team consensus on sprint decisions. Members signal agreement or concerns with one to five fingers, revealing consensus or issues to address.

Use story points to estimate a user story’s cost or effort against a benchmark, such as 10 points, to gauge its size and the team's velocity.

Apply estimation techniques like Wideband Delphi and story points to gauge effort for delivering a user story, using ranges and comparisons to past work to improve accuracy.

Approve, estimate, and commit user stories generate the sprint backlog, with the product owner identifying initial stories, the scrum team committing to them, and the scrum master protecting the sprint.

Identify and decompose the sprint into tasks, then create and estimate the level of effort for delivering user stories, and note the dependencies and key outputs of task creation.

Explore how the task planning part of sprint planning breaks user stories into tasks to deliver a product increment, with team consensus on effort and commitments.

Leverage functional decomposition to break epics into user stories and then into tasks, ensuring alignment with acceptance criteria and the down criteria for deliverables.

Identify and manage dependencies early to align technology, design, development, and testing needs. Distinguish mandatory, discretionary, external, and internal dependencies, and coordinate with other scrum teams.

Establish relative size strategies for task estimation using story points as benchmarks. Use ideal time as the best-case duration and anticipate deviations.

Produce an effort estimated task list from user stories to shape the sprint backlog, and track progress with a burn down chart as tasks evolve.

Create the sprint backlog by listing the user stories the team will deliver this sprint, with tasks and risks, and organize them on a scrum board.

Observe how a scrum board converts user stories into organized tasks, uses story points to estimate effort, and moves task cards from to do through verification to done, ensuring transparency.

Track remaining work hours and completed tasks to gauge sprint progress against the plan using a burndown chart across the sprint window.

Define and produce the sprint backlog and its key outputs, including a sprint burn down chart, to track and manage the team's progress during the sprint.

Identify and refine user stories with acceptance criteria, secure team estimates and approvals for the sprint, estimate tasks, and create a sprint backlog and burn-down chart to track progress.

The team plans sprints by reviewing user stories and estimating effort, cost, and resources. They size work, commit to deliverables, and create sprint backlog and burn down to track progress.

Apply your sprint planning and estimation skills by taking chapter 04 quiz and assessing your performance.

Learn how to produce project deliverables, run daily stand-ups to facilitate communication and identify roadblocks, and use the scrum master to manage impediments, reduce technical debt, and boost agility.

Deliver a potentially shippable sprint by completing cross-functional work and applying test-driven development to write just enough code and refactor to reduce technical debt.

Explore the daily standup, a 15-minute scrum meeting where the team asks key questions, shares focus, and the scrum master identifies impediments to support the team.

Attend the daily standup to sync on progress within a 15-minute timebox, standing in a circle as the scrum master facilitates and the team stays equal.

Set up war rooms to boost collaboration in co-located scrum teams, enabling cross-functional work among developers, testers, analysts, and the product owner with information radiators, a scrum board, burndown charts.

Capture updates to information radiators, impediments, burned down charts, dependencies, risks, and changes from the daily standup to nurture a self-organizing, motivated team delivering higher quality solutions.

Explore the product owner's role in grooming and prioritizing the product backlog while the scrum team executes the sprint, and identify risks and changes for planning future sprints.

Keep the product backlog current and prioritized by engaging customers and stakeholders, validate user stories and acceptance criteria with the team, and prepare for the next sprint planning.

facilitate communications by supporting informal collaboration among co-located teams, customers, users, and the product owner, and regularly groom the backlog to reflect changing priorities using Moskow analyses and paired comparisons.

Grooming activities by the product owner drive updates to the prioritized product backlog and related release plans.

Carry out a sprint within Scrum by delivering customer-focused deliverables, running the daily standup, and grooming the backlog to reflect customer change requests and shifting priorities.

Coordinate the scrum team to deliver deliverables via daily stand ups that answer what was completed, what’s next, and impediments, with colocated war rooms guiding backlog grooming reflecting customer priorities.

Identify key terms from this chapter, including agreed actionable improvements, cumulative flow diagrams, earned value analysis, SVP, retrospect, sprint meetings, scrum of scrums, speedboat, and sprint review meeting.

Explore how to scale scrum with a scrum of scrums to coordinate teams, facilitate communication, and support program and portfolio management, while guiding the four questions used in the practice.

Explore the four questions per team in a scrum of scrums: what we worked on since last meeting, what we will do next, and dependencies or risks affecting other teams.

Coordinate the outputs from the scrum of scrums to align team progress through the prioritized product backlog, collaborate to resolve identified issues, and update impediments and dependencies.

Demonstrate user stories as vertical slices, fully tested and ready to hand over, gather feedback from the product owner and customer stakeholders, and update the product backlog for future sprints.

Compare gantt charts with scrum tracking tools like earned value analysis and cumulative flow diagrams to measure value delivered and track evolving work items.

Demonstrate and validate sprint by ensuring deliverables meet the definition of done and product owner acceptance criteria; reject incomplete work and update risks, release plans, and dependencies.

discover how sprint retrospective reviews team performance for continual improvement in scrum, using speedboat and related exercises to identify metrics and potential improvements.

Conduct a sprint retrospective in an open and relaxed environment to identify what works, opportunities, and bottlenecks. The scrum master and scribe guide, producing actionable improvements for the next sprint.

Learn how to facilitate a sprint retrospective by gauging team engagement with the sbp technique, where participants assume explorer, shopper, vacationer, or prisoner roles and vote anonymously.

Identify engines that speed toward the project vision and anchors that slow progress in a speed boat retrospective. Prioritize mitigations and create action items for the scrum master.

Explore metrics and measures a scrum master uses to assess team performance, including velocity, story points completed, estimation accuracy, stakeholder feedback, and progress toward release with business value.

Capture actionable improvements and due dates from the retrospect sprint. Surface nonfunctional requirements for the backlog and log lessons learned, then share recommendations with the organizational scrum guidance body.

Wraps up a sprint with scrums of scrums for cross-team collaboration, demonstrates progress in sprint reviews to gain product owner commitment, and uses retrospectives to improve team performance.

Coordinate multiple scrum teams with a scrum of scrums for larger programs; demonstrate and validate the sprint with product owners and stakeholders, ensuring definition of done and acceptance criteria.

Learn about the sprint review meaning and the sprint retrospective, then take the quiz to test your understanding.

Learn the key terms to know in this section, including communications plan, minimum functionality, and pilot plans.

Learn to ship deliverables that are potentially shippable at sprint end, determine production readiness, pilot services, align scrum and release activities, and establish communications plans.

Decide when to deploy by coordinating customer needs, risk management, and organizational readiness, and maintain a release plan to deliver value early and frequently within each sprint.

Establish a pilot plan to test new functionality with stakeholders, gather feedback, and ensure a smooth transition to production through clear objectives, scope, user base, schedule, and evaluation.

Define and execute a communications plan using scrum artifacts like the sprint board and burndown chart to keep stakeholders informed, while prioritizing knowledge transfer and readiness for release.

Highlight the key outputs from the ship deliverables, including a deliverables agreement and customer sign-off for handoffs to release and deployment management, revenue recognition, and release notes for operational support.

Conduct a final project-wide retrospective of the timeline to identify what worked well, opportunities for improvement, and lessons learned to inform Scrum guidance bodies and project owners for future projects.

Conduct the project retrospect in an open, relaxed environment to identify process improvements, capture lessons learned, and share actionable improvements with stakeholders and the enterprise for future projects.

Assess your understanding of release processes by taking the checkpoint quiz to see how you perform.

Explore how scrum practices boost collaboration between customers, users of services, development teams. Emphasize empiricism, self-organization, time boxing, daily stand up meetings, sprint planning, and iterative development to maximize value.