This two–day course provides the basic principles of Scrum by the Co–Creator of Scrum. It allows participants to assess their Scrum implementations using the practices that produce the best Scrum teams worldwide. It gives participants hands–on experience using Scrum by simulating Scrum projects. The first simulation provides experience with the basic Scrum practice in a 59–minute Scrum through a non–technical group exercise. The second simulation leads participants through the entire planning and estimation phase of setting up the first Scrum. The third simulation provides hands on experience of executing a Scrum pulling from the Product Backlog, creating a Sprint Backlog, and delivering velocity of production during a Scrum. The secret sauce that Dr. Sutherland uses to coach over 20 venture funded portfolio companies will be described. This will show how participants can practically apply the Scrum roles (Product Owner, ScrumMaster, and Team), the Scrum meetings (Sprint Planning, Daily Scrum, and Sprint Review with a demo and Retrospective), and the Scrum artifacts (Product Backlog, Sprint Backlog, Burndown Charts, and Working Software) to double and then quadruple the productivity and quality of their teams. Participants will learn how to scale Scrum projects to any size, how to distribute them locally and globally, and how to use outsourcing to produce extreme business value.
Dr. Sutherland’s courses are used to train every person in all roles in some companies. Participants are using Scrum on senior management teams, in marketing, sales, consulting, client services, installations, and support, as well as development. While successful completion of the course designates each participant Certified ScrumMaster, the course is designed to help anyone in any role in a Scrum company, as well as being the best available training for ScrumMasters. This certification includes a one–year membership in the Scrum Alliance, where additional ScrumMaster–only material and information are available.
Participants Will Learn:
• Proven practices developed in nine companies where Dr. Sutherland has been CTO or VP of Engineering
• How to set up Scrum teams and begin work in the most effective way
• How to create, prioritize, and estimate user stories for the product backlog
• The role of management in a company powered by self–organizing teams
• How to help both new and experienced teams be more successful
• How to scale Scrum to large, multi–continent projects building systems with millions of lines of code.
• The secret sauce developed from the instructors fifteen years of using Scrum that is used by venture capitalists and venture funded companies worldwide.
Agenda:
Overview of Scrum
Why Scrum works
What Scrum is
Origins
Sprints
Potentially shippable
Architecture on a Scrum project
Sequential vs. overlapping work
Sprint length
Release sprints
Abnormal terminations
The ScrumMaster
Responsibilities
ScrumMaster mindset
Situational ScrumMastering
ScrumMaster as team member
The 59–minute Scrum project
The product owner
Description
Responsibilities
Sharing the vision
Product backlog
Size of the items
User stories on the product backlog
Backlog–writing workshops
INVEST in your backlog
Meetings
The daily scrum
Sprint review
Sprint retrospective
Sprint planning
Sprint prioritization
Sprint goal
Sprint planning meeting
Sprint backlog items
Release planning
Velocity
Estimating the product backlog
Release planning meeting
Tracking progress
Sprint burndown charts
Release burndown charts
Task boards
The team
Composition
Teams are cross–functional
Organizing
Scalability
The scrum of scrums
Focus of initial sprints
Shared vs. specific product backlogs
Scaling the product owner
Getting started
Who Should Attend
Whether youre a manager, programmer, tester, analyst, product manager, or someone interested
in working on or with a Scrum team, this course is suited for you. You will leave with solid
knowledge of how and why Scrum works. Through practical, hands–on exercises and smallgroup
discussion you will be prepared to plan your first sprint immediately after this class.
PMPs can receive 16 Professional Development Units (PDUs) for this course.
Exam:
Changes from Scrum Alliance on how to become a Certified ScrumMaster (CSM). The changes will take place on 1 March.
The Scrum Alliance no longer require the exam to become a CSM, instead there will be an assessment.
The assessment or test will be online after you completed your Scrum training. You will have 90 days to take the test. On the test it will be given 25 questions drawn from a pool of 13 terminology questions, 15 practices questions, and 7 principles questions. When the test is completed you will get your score percentage and the right answers on those you missed.
The results will explain why an answer is correct and will point out to you the web–based resources to read up on the missed question. The goal is to help you learn rather than just give you a score percentage. You can not fail the test, and that the purpose of it is to provide further learning. Pleas do not hesitate to contact us for any questions, we are more than happy to answer the questions you may have.
About the instructor:
Dr. Sutherland is a Certified Scrum Trainer and invented the Scrum process [1] in 1993 at Easel Corporation. Jeff was the Chief Engineer for the Object Studio team that created Scrum [1]. He defined the roles and hired the first Product Owner and ScrumMaster and led the effort to build the first series of products created with Scrum. In 1995, Jeff worked with Scrum Co?Creator Ken Schwaber, to formalize the Scrum development process at OOPSLA95 [2]. In the same year, Sutherland provided support for development of eXtreme Programming [3] by giving Kent Beck all background information on the creation of Scrum [4] and the results of two years of experience with the Scrum process delivering new products. XP engineering practices then evolved along with SCRUM and the two leading Agile development processes work well together. Scrum and XP are the most widely used Agile processes worldwide and their creators are authors of the Agile Manifesto.