Course Overview

The Certified ScrumMaster (CSM) Training assists you in grasping Scrum processes and agile concepts well. It also illustrates the Scrum Master's role in building excellent teams. This training educates people on how professionals can implement Scrum in the workplace. It also assists team leaders who govern agile teams by providing clear insights.

The course is conducted by a Scrum Alliance certified instructor. The training includes major Scrum concepts such as Scrum framework, events, artifacts, roles, and best practices. The hands-on experience will be given to the participants to assist them in trying the certification exam. Practical exercises, interactive sessions, and live examples are utilized to train the participants.

Upon completion, learners will be able to:

✔ Apply Scrum practices to actual projects.

✔ Enable collaboration and communication within Agile environments.

Practice Scrum best practices to be more effective.

✓ Recognize and eliminate the barriers to team performance.

✔ Obtain the well-known Certified ScrumMaster® (CSM) certification.

This course is ideal for:

• Project managers


• Software developers


• Business analysts


• Product owners

It is also useful to anyone looking to become expert in agile project management.

Reviews

Certified ScrumMaster® (CSM) certification assists in learning Agile project management. It is on learning Scrum practices for better usage. No background is needed to join, but some skills assist in learning better.

To whom is the CSM Certification offered?

The CSM course is ideal for:

• Project Managers and Team Leads

• Scrum Masters and Agile Coaches

• Software Developers and Testers

• Product Owners and Business Analysts

• IT Professionals and Quality Analysts

• Anyone interested in Scrum and Agile approaches.

Requirements for CSM Certification

• No official prerequisites: Anybody can go to the CSM training without any experience.

• Underlying Agile knowledge: Knowledge of Agile fundamentals is helpful but not required.

• Desire to learn: Scrum is hands-on. Being engaged and doing things in practice exercises will make you successful.

How to Become a Certified ScrumMaster®

1. Attend a CSM course. You can enroll in a 2-day in-person course or attend live online. Either course is taught by a Scrum Alliance Certified Trainer.

2. Pass the CSM Exam – Pass the CSM certification test with a minimum of 74%. This occurs if you answer at least 37 out of the 50 questions correctly.

3. Get Certified – Once you pass, you are awarded your Certified ScrumMaster® (CSM) certification by the Scrum Alliance.

4. Renew Your Certification – CSM certification is two years valid. To maintain it, you will have to renew it by collecting Scrum Education Units (SEUs).

Why get CSM certified?

• Enhance employment opportunities with a valued Agile credential.

• Build your skills for leading and managing flexible teams.

• Improve your problem-solving ability and optimize project effectiveness.

• Become part of a select group of Scrum professionals by joining the Scrum Alliance.

Below is the complete and detailed Certified ScrumMaster® (CSM) Course Agenda with all the topics and subtopics exactly as provided:

1. Introduction to Agile and Scrum

• 1.1. Why Agile?

• 1.2. Traditional Development

• 1.3. Problems with traditional software development

• 1.4. Usage of features in a system

• 1.5. Makings of a new approach

• 1.6. Agile Manifesto

• 1.7. Principles behind the Agile Manifesto

• 1.8. Authors of the Agile Manifesto

• 1.9. Agile Project Management

• 1.10. Agile Project Management Life-cycle

• 1.11. Agile Project Management Framework

• 1.12. APM Framework

• 1.13. What is Scrum?

• 1.14. Certified Scrum Master

• 1.15. Professional Scrum Master

• 1.16. PMI-ACP

2. Agile Methodologies

• 2.2. Agile Methodologies

• 2.3. Crystal

• 2.4. 7 Project Properties in Crystal

• 2.5. Samples of Crystal

• 2.6. Feature-Driven-Development

• 2.7. Roles in FDD

• 2.8. Processes in FDD

• 2.9. Project tracking in FDD

• 2.10. Project tracking methodology

• 2.11. FDD usage guidelines

• 2.12. Dynamic Systems Development Methodology (DSDM)

• 2.13. Planning in DSDM-Atern

• 2.14. DSDM Principles and techniques

• 2.15. eXtreme Programming

• 2.16. XP Values

• 2.17. XP Practices

• 2.18. XP Benefits

• 2.19. Agile Unified Process

• 2.20. Agile Unified Process (AUP)

• 2.21. Agile Unified Process – System Development

• 2.22. Scrum

• 2.23. Scrum Life-cycle

3. Scrum Roles

• 3.2. Stakeholders

• 3.3. Chicken and Pig roles

• 3.4. Management of stakeholders

• 3.5. Scrum life-cycle

• 3.6. Product Owner

• 3.7. Product Owner’s role

• 3.8. Prioritization

• 3.9. Cost-Benefit Analysis

• 3.10. Prioritization based on Value and Risk

• 3.11. Prioritizing requirements - MoSCoW

• 3.12. Prioritizing requirements – Kano Model

• 3.13. Prioritizing requirements – Relative weighting method

• 3.14. Scrum life-cycle

• 3.15. Scrum Master

• 3.16. What does a Scrum Master Do

• 3.17. What the Scrum Master Should NOT do

• 3.18. Scrum life-cycle

• 3.19. The team – aka Developers

• 3.20. Building a Scrum team

• 3.21. Building empowered teams

• 3.22. Role of a Manager

• 3.23. Manager 2.0: A new role for a Manager

• 3.24. Some specialist roles you may want

4. Scrum Ceremonies

• 4.2. Time-boxing

• 4.3. Advantages of time-boxing

• 4.4. Time-boxing

• 4.5. Release

• 4.6. High-level view of a release

• 4.7. Sprints

• 4.8. Factors in selecting a Sprint duration

• 4.9. Intensity of work

• 4.10. No changes in a Sprint

• 4.11. Daily Scrum

• 4.12. Sprint Review

• 4.13. Also check during a review

• 4.14. Sprint Retrospective

• 4.15. What is a Sprint Retrospective

• 4.16. Making retrospectives effective

• 4.17. Making retrospectives effective

5. Scrum Artifacts

• 5.2. Product backlog

• 5.3. Product, release and sprint backlog

• 5.4. User story

• 5.5. Story card information

• 5.6. Multiple stories may be required to complete a feature

• 5.7. Epics

• 5.8. Writing good stories

• 5.9. Splitting user stories

• 5.10. Splitting user stories (big picture)

• 5.11. Splitting user stories (user experience)

• 5.12. Splitting user stories (Others)

6. Scrum Best Practices

• 6.2. Refactoring

• 6.3. Pair programming

• 6.4. Continuous integration

• 6.5. Practices of continuous integration

• 6.6. Configuration management

• 6.7. Quality in Agile

• 6.8. Scrum Quality – Home truths

• 6.9. Planning for a Sprint

• 6.10. Test-driven development

• 6.11. Test-driven development

• 6.12. Advantages of TDD

• 6.13. Definition of “Done”

7. Scrum Planning

• 7.2. Principles behind Agile planning

• 7.3. Iterations allow for mid-course corrections

• 7.4. Multiple levels of planning

• 7.5. Release planning

• 7.6. Steps to planning a release

• 7.7. Release Planning

• 7.8. Velocity

• 7.9. Sprint planning

• 7.10. Velocity driven sprint planning

• 7.11. Commitment driven sprint planning

• 7.12. Planning for each story

• 7.13. Keep in mind before finalizing the plan

8. Scrum Estimation

• 8.2. Principles behind Scrum estimation

• 8.3. Estimation techniques

• 8.4. Types of estimates

• 8.5. Uncertainty in estimates

• 8.6. Over-estimation and under-estimation

• 8.7. What contributes to size

• 8.8. Measures of size

• 8.9. Ideal days

• 8.10. Story points

• 8.11. Estimation techniques – Planning poker

• 8.12. Affinity estimation

• 8.13. Affinity estimation - process

9. Monitoring Scrum Projects

• 9.2. Monitoring Scrum Projects

• 9.3. Definition - Metrics

• 9.4. Types of metrics

• 9.5. Metrics do’s and don’ts

• 9.6. Charts in Scrum

• 9.7. Burn-down chart: Iteration level

• 9.8. Burndown chart: Project level

• 9.9. Burndown chart: Bar style

• 9.10. Burn-up and Burn-down chart

• 9.11. Cumulative Flow Diagram

• 9.12. Parking lot diagram

• 9.13. Escaped defects found

• 9.14. Velocity chart

• 9.15. Progress Chart

• 9.16. NikoNiko calendar

• 9.17. Information radiators

• 9.18. Information radiators: Big visible charts

• 9.19. Information radiators

10. Scrum – Advanced Concepts

• 10.2. Scrum on large projects

• 10.3. Scrum-of-Scrum

• 10.4. Product coordination teams

• 10.5. Scrum on maintenance projects

• 10.6. Distributed scrum teams

• 10.7. Best practices in distributed scrum

• 10.8. Structure-1: Team in India; PO in US

• 10.9. Structure-2: Team split in two locations

• 10.10. People practices in distributed Scrum

• 10.11. Practices in distributed scrum

• 10.12. Practices in distributed scrum

• 10.13. Scrum-Contracting

• 10.14. Fixed Price/fixed scope

• 10.15. Scrum in fixed price projects

• 10.16. Transitioning a team/project to Scrum

• 10.17. Transitioning a team/project to Scrum

Q1. What are the payment methods for online CSM training?

You can sign up for the CSM course on our website:

We accept various payment methods, which are:

• PayPal

• MasterCard

• American Express

• Visa Credit Card or Debit Card

Once you pay, you will be provided with payment receipt and access details to the e-mail address you had subscribed with.

Q2. Do you have a money refund guarantee for CSM training?

Yes, we do offer a money-back guarantee for the majority of our training courses.

Q3. Is cancellation of admission permitted? Will the money be refunded ?

Yes, you may cancel your registration, and you will be refunded after a deduction of administrative fees.

Q4. How and when do I get my CSM certification?

Once you have cleared the CSM exam, you will be awarded your certificate through an email within 5 business days.

Q5. Who is accountable for the CSM certification and exam process?

The Certified ScrumMaster (CSM) certification and exam are managed by the Scrum Alliance, Inc. Be aware that the Certified Trainer (CRT) is the one managing the certification.

Q6. Will I get the certificate upon completion of the CSM training?

Yes, once you complete the CSM training program (classroom training and workshop), you will receive a certificate for completing ProctorLearn's CSM training course.

Q7. Is employment available after being certified as CSM ?

Indeed! Agile and Scrum Master are extremely sought-after positions in most sectors. A few of the top companies seeking CSM professionals are:

• JP Morgan

• Capital One

• Bank of America

• IBM

• Wells Fargo

Career sites normally post numerous Scrum Master and Agile Project Manager job positions, so CSM is a good certification to get for career development.

Q8. Where can I find information on the CSM training program?

You can find information about the training program by:

• Press the 'Need Help & Support' button and complete the form.

• Use the 'Request a Call Back Now' facility.

• Reaching out to our support team via Live Chat for immediate assistance.

Q9. Do you grant PDU certificates?

Yes, on completing our two-day CSM training , you will be granted 16 PDUs (Professional Development Units).

See PMI's guidance for additional information on renewing your certification using PDUs.

Q10. Is CSM worth it?

Right! The CSM certification is definitely worth it because it enhances your Scrum and Agile abilities, broadens your career opportunities, and raises your income levels.

Q11. How difficult is the CSM exam?

The CSM exam is not difficult at all if you have undergone training and have some knowledge of the Scrum principles. The exam has 50 multiple-choice questions, and in order to pass it, you must answer at least 74% or 37 questions.

Q12. Is the CSM exam available online?

Yes, you can sit for the CSM exam online from anywhere. You will receive the exam link after the training.