Database administrators and database engineers will face new challenges as they adopt Scrum. In your new role, you will learn how to work incrementally on something that is traditionally viewed as part of the project's upfront work. While your day-to-day work may not change all that much, how you approach and schedule that work will dramatically change as part of a Scrum team.
Which Course is Right for Me?
Core
Core courses are fundamental to your effective use of agile.
Certified ScrumMaster® or Working on a Scrum Team
These two courses cover the fundamental principles of Scrum. Both courses are suitable for all team members including Scrum Masters and product owners.
Optional
Optional courses are less specific to this particular role, but will still provide value.
Better User Stories
Overcome the challenge of writing user stories to join the ranks of high-performing agile teams, deliver the right products to market, and delight your customers.
Certified ScrumMaster® or Working on a Scrum Team
Description:
These two courses cover the fundamental principles of Scrum. Both courses are suitable for all team members including Scrum Masters and product owners.
Certified ScrumMaster®
A two-day class taught by one of our Certified Scrum Trainers, the Certified ScrumMaster course covers the fundamental principles of Scrum as well as detail about the different roles, meetings, and artifacts. Despite the name, it's perfect for anyone who wants to understand Scrum, not only ScrumMasters.
Working on a Scrum Team
Based on the content of our popular Certified ScrumMaster course, Working on a Scrum Team differs by being entirely configurable. Prior to the course, you will work with one of our instructors to identify the most important course content. If, for example, you want more time spent on estimating and less on the daily scrum, you can easily make this the course for you.
Topics:
Scrum Overview
- Agile
- Scrum
Sprinting
- Timeboxes
- No Changes Allowed
- Reciprocal Commitments
- Defining Done
- Sprint Types
- Introducing Change into a Sprint
The Development Team
- Rights & Responsibilities
- Self-Organizing
- Cross-Functional
- Collaborating
- Component and Feature Teams
The Product Owner
- What is a Product Owner?
- Rights & Responsibilities
- Managing Stakeholders
The Scrum Master
- The Scrum Master
- Rights & Responsibilities
- Four Facilitation Techniques
- Coaching, Mentoring, Teaching & Facilitating
- The Scrum Master in Dual Roles
- Servant Leadership
Managers
- Project Managers
- Functional (Department) Managers
Product Backlog
- Responsibilities & Attributes
- User & Job Stories
- Two Ways of Adding Detail
- Progressive Refinement
- Organizing the Backlog
- Story Splitting
Planning
- Fixed-Date Plans
- Fixed-Scope Plans
- Creating the Plan
- Technical Debt
Estimating
- Relative Estimating
- Story Points
- Ideal Time
- Affinity Estimation
- Three Ways to Estimate Velocity
Sprint Planning
- Meeting Responsibilities
- The Sprint Goal
- The Purpose
- Capacity-Driven Sprint Planning
- Velocity-Driven Sprint Planning
- Decomposing Stories into Tasks
- Working Out of Order
- What To Do When the Product Owner Is Missing
Other Scrum Meetings
- Daily Scrum
- Sprint Review
- Sprint Retrospective
- Product Backlog Refinement
Scaling Scrum
- Scaling Guidelines
- Scaling the Planning Meeting
- Scrum of Scrums
- Communities of Practice
Better User Stories
Description:
A great product begins with a great product backlog. User stories are by far the most common way of writing product backlog items, used by an increasing number of agile teams.
This course will help participants learn solutions to some of the most common problems with user stories and product backlogs. You will finish the course with known, proven techniques to overcome your current challenges, from spending too much time splitting stories to adding too much detail to managing the need for a requirements document.
During the course, participants will work on product ideas or features you provide. Or they can work on ones we’ve designed to maximize shared learning and bring out the subtle challenges teams can face. During the course, participants can also identify new products to work on throughout the day. This flexibility ensures they are always working on relevant ideas.
Participants will practice conducting a story-writing workshop and will learn how to create a story map to improve communication with stakeholders and to uncover user needs earlier—so last-minute requirements don’t derail a project.
The Better User Stories course goes beyond user stories to give participants practice writing job stories and technical stories, two exciting approaches that can immediately improve a team’s backlog-writing skills.
Knowing how much detail to include (and how early to add it) is a vital skill for agile team members to develop. Adding too much detail too early wastes precious time that could be used on higher priority features. Adding too little detail or adding it too late can jeopardize delivery. Through this course, participants learn simple questions to ask that will get them the right amount of detail every time.
Participants will learn how to split stories so that each can fit within an iteration. Our SPIDR story-splitting framework, taught in this class, will give participants a reliable, repeatable way to split any story.
After taking this course, teams will spend more time building features that deliver the most value to stakeholders each iteration.
Topics:
Common User Story Problems
Story-Writing Workshops
- Four Times to Write Stories
- Focus on a Single, Significant Objective
- Agenda and Participants
Backlog Refinement
- How Much Should Be Known and When
- Adding Detail to Stories
- Disagreements after a Story Is Done
- The Problems with Too Much Detail
- Sub-Stories and Acceptance Criteria
- The Full Lifecycle of a Story
Job and Tech Stories
- When Job Stories Are Appropriate
- Differences Between Job and User Stories
- Technical Stories
Story Mapping
- Common Story Map Problems
- Sub Maps Improve Readability
- Creating a Story Map
- Roadmaps
Splitting Stories
- The Goal in Splitting Stories
- SPIDR
Non-Functional Requirements and Bugs
- Non-functionals and the Definition of Done
- Bugs