Certified ScrumMaster
Friday/Saturday Certified ScrumMaster class in Jacksonville, FL
All CSM courses are taught by Certified Scrum Trainers. Taking a CSM course, passing the CSM test, and accepting the license agreement designates you as a Certified ScrumMaster, which indicates that you have been introduced to and understand the basic concepts you need to perform as a ScrumMaster or team member on a Scrum team. This course also satisfies two elements of the CSD track: Scrum Introduction and Elective.
The 2-day Certified ScrumMaster course introduces attendees to the values, principles, and practices of agile and the agile-based empirical Scrum product development framework. Successful completers can become Certified ScrumMasters, a first step in the journey of learning Scrum and becoming proficient in its use. Attendees also learn the paradigm shifts that occur when organizations move from traditional linear / defined development environments to the empirical agile environment and strategies and tactics used to support and manage the change that occurs. Participants also will learn about the 3 Scrum roles (Team Member, Product Owner, and ScrumMaster), the 4 Scrum meetings (Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective) and process of building product in a time-boxed iteration called a Sprint. Students will assume responsibility for their learning in the course and will work in small teams. The course includes a detailed Scrum project simulation and other exercises that will reinforce course concepts. Participants will have opportunity to explore and apply self-organization and self-direct concepts that contribute most effectively to building a high performing team environment where quality can be built into a product through the empricial process of inspecting and adapting processes and products. After completing this course, the student should be able to: · Demonstrate the appropriate understanding and application of Scrum roles, practices, principles, and values · Apply appropriate analysis about how empirical the approach to project work should be (when to use Scrum) · Appreciate the skills, desired styles, and responsibilities of the Team, Product Owner and ScrumMaster · Accept and explain the rationale behind the absence of a project manager in Scrum · Apply Scrum estimating and planning techniques and practices · Understand the use and presentation of certain data used for inspecting and adapting to improve team performance and the product · Understand the criticality of building trust within and between Scrum teams and between teams and management · Understand the essence of team self-organization and self-direction to build high perfroming teams, and the necessity of servant leadership · Identify and deal with smells (pitfalls) that the organization and its teams may encounter that may impede the use of Scrum
| Dates: | 22-23 Jul 2011 |
|---|---|
| Location: | Jacksonville, FL |
| Venue: |
Embassy Suites, |
| Price: |
$1,295 per person |
| Notes: |
Register for the class online at the PMI – Northeast Florida website: www.pmi-nefl.org |
Course Comments
Be the first to add a comment on this course…
Please login to comment on this course.
-
Values and principles of agile and Scrum
-
Characteristics and behaviors desired in an agile-based organization
-
Empirical-based development versus defined-based development: differences and appropriate uses
-
The Scrum Framework: the practices, roles, artifacts, and meetings
-
Scrum odors and impediments to teams and organizations and how they might be avoided or dealt with
-
Application of agile and Scrum concepts through interactive exercises
-
Debunking agile and Scrum myths
-
Other items of interest as desired by the group
This course is intended for those who wish to explore the benefits that agile and Scrum and who want a foundational education in agile and Scrum values, principles and practices, and enjoy a learning format that is hands-on, experiential and Socratic. Attendees will utilize a variety of exercises and resources to help them learn and apply Scrum in both software and non-software product development situations.


Share on LinkedIn
Share on Twitter