Certified Scrum Master Training
Objective
Become an exceptional Scrum Master with real-time scrum activities and simulations
• Global Registered Education Provider (REP) of Scrum Alliance
• Get trained by globally renowned Certified Scrum Trainers (CSTs)
• Earn 16 PDUs and 16 SEUs in just 2 days
• Experiential learning with Case studies, Scrum Activities, Role plays, & Simulations
• Progressive learning and support to further your Scrum knowledge
WHY SHOULD YOU GO FOR A CSM CERTIFICATION?
In the modern workplace, there is always a deluge of information which employees must sift through. Naturally, this leads to wastage of time, energy and resources which could be better utilised for development instead. The solution to this would be a work environment which would allow a team to make changes quickly and accurately while self-organising in accordance with agile principles. This is termed as Scrum which has been observed to work brilliantly in complex work environments.
The excellence required by the industry is always leaning towards continuous delivery, and the Certified Scrum Master Certification is designed to help organisations do precisely that.
According to Scrum Alliance, more than 42% of teams leverage Scrum exclusively. The CSM Certification in Bangalore provides a holistic view to the participants regarding the Scrum framework and trains them to become Certified Scrum Masters.
Scrum, if leveraged effectively can do away with dysfunctions and improve team workflows in an agile manner.
The certification value can be divided mainly into two kinds of categories:
Value to Individuals
• Professional Credibility- The Scrum Master training in Bangalore will enable you to transition to any new team with a much-improved efficacy which in turn will be a huge benefit to someone who hires you.
• Personal Satisfaction- Open doors to different types of opportunities with the CSM Certification in Bangalore as it empowers you to become an expert in a niche field.
• Salary- According to a PayScale report, Certified Scrum Masters can charge an average total compensation of more than $110k per annum.
• Job Search- These types of certifications give you a natural edge over others in interviews as employers are cognizant of the fact that trained professionals perform faster and better than the non-certified counterparts.
• Professional Growth- Picking up new skills is often advantageous for your career growth which requires you to enhance your techniques and skillsets every few years.
Value to Organisations
Today, it’s not only the IT industry who are leveraging the Scrum framework, but other non-IT industry giants are picking up professionals certified in Scrum as well. A scrum professional who is a certified ScrumMaster can help an organisation in various ways-
• Job Essentials- Help guide team members throughout the product lifecycle.
• Filling Skills Gaps- With the CSM training in Bangalore, you will be able to work with the team to deliver high-end products with quick turnaround times.
• Structured and interactive teams- Improve employee engagement and offer structure to your team as a well-structured team that communicates effectively produces better results.
• Stay relevant in the industry- The Scrum Certification in Bangalore ensures that your organisation stays up-to-date with certifications and methodologies assuring customers that you have the team and the process to deliver the required work.
CSM® certification- Adding value to your career
As a Certified ScrumMaster, you will be known as a part of an elite group engaged with Scrum Alliance. The members of Scrum Alliance are meant to be Scrum specialists, guiding the project teams to success. Here is why CSM® certification should be a part of your skill set:
• Based on the recent salary survey by Ziprecruiter, the average annual salary for the Certified ScrumMaster is $116,659 a year.
• CSM® certification enables you to work across major companies like IBM, Tata Consultancy Services, CapGemini, Honeywell, BOSCH, Accenture, Deloitte and many more in several job roles:
o Scrum Master
o Delivery Lead
o Agile Scrum Master
o Program Manager
o Project Manager
o Agile Coach
o Automation Engineer
o Project Lead
PREREQUISITES
There is no set of eligibility requirements to attend this Scrum Master Certification course and it can be taken by freshers or professionals who want to:
• Further their career in project management.
• Deepen their understanding of Scrum.
Our experienced CSTs deliver training in such a way that is suitable for both novice and experienced professionals. But, it is recommended that you have basic knowledge of using Scrum in a real-world context, in order to get the most from the training.
WHAT YOU WILL LEARN IN THIS CSM WORKSHOP
1. Learn Fundamentals
Understand the foundation of Agile and Scrum concepts and help Scrum teams in using Scrum effectively.
2. Terminologies and Concepts
Acquire knowledge of Scrum terminologies, various concepts, and the complete Scrum process.
3. Scrum Roles
Understand various roles involved in Scrum and the scope of the Scrum Master role in Scrum.
4. Core Competencies
Learn key Scrum Master core competencies and protect the team from internal and external distractions.
5. Scrum Ceremonies
Daily Scrum, Sprint Review, Sprint Retrospective, Product Backlog, Sprint Backlog, Definition of Done.
6. Facilitate Teams
Facilitate the Development Team, Product Owner, and the organization while responding to change.
7. Improve Transparency
Inspect and adapt and increase transparency in each of the Scrum events and make the team’s work visible.
8. Acts as a Servant Leader
Learn to help the team members work collaboratively and follow every Scrum process involved in it.
REGISTER
GROUP OF 3 OR MORE [Rs.22999 Plus GST Per Participant]
INDIVIDUAL STANDARD PRICE [Rs.24999 plus GST Per Participant]
| Training Date | Trainer | Timing |
| Jun 04 – Jun 05 | Marco Mulder | 12:30 PM – 08:30 PM ( IST ) |
| Jun 06 – Jun 07 | Vijay Bandaru | 09:00 AM – 05:00 PM ( IST ) |
| Jun 06 – Jun 07 | Kok Ewe Siew | 08:00 AM – 04:00 PM ( IST ) |
| Jun 06 – Jun 07 | Danny Kovatch | 12:30 PM – 08:30 PM ( IST ) |
| Jun 06 – Jun 07 | Jaya Shrivastava, CST | 11:00 AM – 07:00 PM ( IST ) |
| Jun 10 – Jun 11, | Danny Kovatch | 12:30 PM – 08:30 PM ( IST ) |
| Jun 13 – Jun 14 | Jaya Shrivastava | 09:00 AM – 05:00 PM ( IST ) |
| Jun 13 – Jun 14 | Danny Kovatch | 12:30 PM – 08:30 PM ( IST ) |
| Jun 18 – Jun 19 | Kok Ewe Siew | 08:00 AM – 04:00 PM ( IST ) |
| Jun 18 – Jun 19 | Vijay Bandaru | 08:00 AM – 04:00 PM ( IST ) |
| Jun 20 – Jun 2 | Jaya Shrivastava | 09:00 AM – 05:00 PM ( IST ) |
| Jun 20 – Jun 21 | Danny Kovatch | 12:30 PM – 08:30 PM ( IST ) |
| Jun 20 – Jun 21, | Anderson Diniz Hummel, CST | 12:30 PM – 08:30 PM ( IST ) |
| Jun 22 – Jun 23 | Jacky Shen | 06:30 AM – 02:30 PM ( IST ) |
| Jun 23 – Jun 24 | Vijay Bandaru | 09:00 AM – 05:00 PM ( IST ) |
| Jun 24 – Jun 25 | Jacky Shen | 06:30 AM – 02:30 PM ( IST ) |
| Jun 27 – Jun 28 | Jaya Shrivastava | 08:00 AM – 04:00 PM ( IST ) |
| Jun 27 – Jun 28 | Vijay Bandaru | 09:00 AM – 05:00 PM ( IST ) |
| Jun 27 – Jun 28 | Kok Ewe Siew | 08:00 AM – 04:00 PM ( IST ) |
| Jun 27 – Jun 2 | Danny Kovatch | 12:30 PM – 08:30 PM ( IST ) |
| Jun 29 – Jun 30 | Marco Mulder | 01:30 PM – 09:30 PM ( IST ) |
Course Features
- Lectures 120
- Quizzes 0
- Language English
- Students 45
- Certificate No
- Assessments Yes
You have 1 day 15 hours 59 minutes remaining for the course
-
Agile and Scrum Overview
Get familiar with the 12 principles and 4 values stated in the Agile Manifesto through our popular in-class activity- “Draw and demonstrate”. Herein, you will be asked to form groups and illustrate all 12 principles pictorially
- • Agile Manifesto
- • 12 Principles
- • 4 values
- • Scrum Foundations (5 Scrum Values)
- • Explain the 12 principles and 4 values listed in the Agile Manifesto.
- • Demonstrate the benefits of “responding to change” in Agile over “following a plan” in traditional project management.
- • Describe how the Scrum values (courage, focus, commitment, respect, openness) relate to the Scrum artifacts, events, and roles.
- • List and explain the three pillars in Scrum ― Transparency, Inspection, Adaptation.
- • Explain the differences between framework and methodology and understand why Scrum is called a framework.
- • List 5 ways to develop an Agile mindset.
- • Illustrate 2 differences between Agile and Scrum and explain why these two terms cannot be used interchangeably.
-
The three roles in Scrum
Learn more about the three roles in Scrum with role-based activities. Each group will play a simulation game called “candy catch” that will have three iterations. The Scrum Master and Product Owner (chosen by group members) will coordinate and help the team achieve the highest target within the shortest time.
- • Scrum Master roles and challenges
- • Product Owner roles and responsibilities
- • Development team roles and responsibilities
- • Conduct a retrospective to list 3 techniques to improve the performance and turnaround time.
- • Explain the roles and responsibilities of a Scrum Master and a Product Owner.
- • List 3 differences between a Scrum Master and a Product Owner and understand why these two roles should not overlap.
- • Discuss how a product owner acts as a bridge between the development team and the stakeholders.
- • Understand why a Scrum Master is not an active participant but a facilitator in the Scrum events and ceremonies.
- • List 3 demerits of having a development team of less than 3 members or greater than 10 members.
-
Scrum Ceremonies
-
Scrum Artifacts
Experience how scrum works in real projects with our simulation game “Crime Teller”. The activity will be divided into 3 sprints, wherein the participants will actively employ Product backlog refinement among other scrum artifacts to solve a given “crime” story.
- • Product Backlog
- • Sprint Backlog
- • Product Increment
- • List and demonstrate 5 salient features of a well-formed product backlog (E.g. estimated, prioritized).
- • Discuss 2 responsibilities of the Product Owner, Scrum Master, and the Development team in creating and maintaining a product backlog.
- • The objective of having a product backlog and best approaches to product backlog refinement.
- • Analyze and discuss the ideal time and capacity to be dedicated to product backlog refinement.
- • Demonstrate 3 activities (E.g. budget and timeline, release schedule) that take place during a sprint review.
- • List 5 sprint review anti-patterns (E.g. delayed acceptance) and their negative impacts
-
Sprint Execution
Learn about Scrum life cycle by taking part in the “coin game”. The participants will be linking ceremonies to create effective sprint goals. This module will focus on the common challenges in sprint execution and enable team members to improvise.
- • Sprint Execution Planning
- • Flow management
- • Resolution meetings
- • Communication (Taskboard, Sprint burndown chart using story points, hours effort)
- • Explain the difference between resolution meetings and daily standups.
- • Explain the benefits of collaborations with product owners.
- • List 3 demerits of over collaboration of the product owners.
- • Demonstrate 3 ways to break the barriers and collaborate
- • Demonstrate creation of sprint burndown chart
- • Explain 3 approaches to increase efficiency in the team
-
Daily Scrum and Sprint Retrospective
Play the “Marshmellow Tower” game and learn more about daily scrum and sprint retrospective in real scrum projects. The tallest tower built with the minimum raw materials and in the shortest time frame will win. Acceptance criteria will be defined by the instructor.
- • Activities in daily scrum
- • Activities in sprint retrospective
- • Explain the importance of 15-minute timebox for daily scrum meetings.
- • List 3 differences between traditional meetings and daily stand-ups.
- • Describe 2 roles played by the Scrum Master, Product Owner, and the Development team in daily scrum.
- • List the 3 critical questions pertaining to the daily scrum agenda.
- • List 2 responsibilities of the Scrum Master, Product Owner, and the Development team during the sprint retrospective.
-
Definition of Done (DoD) and Acceptance Criteria
Familiarise yourself with Definition of Done (DoD) and Acceptance Criteria with the “Crazy Juggler” game wherein you need to pass a fixed number of balls to non-adjacent team members within a certain time frame and collect them in a paper bag once marked as “done”.
- • Definition of Done for a feature (user story or product backlog item)
- • Definition of Done for a sprint
- • Definition of Done for a release
- • Definition of Done vs. Acceptance criteria
- • Done vs. Done-Done.
- • Explain Definition of Done at three levels ― user story (e.g. writing code), sprint, and release (e.g. preparing release notes).
- • List 3 benefits of Definition of Done and explain why it can evolve over a certain period of time.
- • Prepare a checklist (with a minimum of 7 entries) of an ideal DoD.
- • Mention 3 risks associated with an ill-formed DoD.
- • List 5 characteristics of good acceptance criteria.
- • Understand who all should be involved in drafting the acceptance criteria.
- • List 3 negative impacts of not following the acceptance criteria.
-
Definition of Ready
Acquaint yourself with the Definition of Ready with our Lego blocks game wherein the attendees will be asked to build a city out of Lego building blocks. The “definition of ready” checklist for the final deliverable will be determined by the instructor.
- • Definition of Ready for user story
- • Definition of Ready for sprint
- • Create an ultimate checklist of Definition of Done.
- • List 3 negative impacts of an ill-formed Definition of Done.
- • Identify at least 3 benefits of a shared Definition of Done for multiple teams working on the same product backlog.
- • List 2 ways to improve Definition of Done.
- • Clearly understand the differences between “done” and “done done”.
-
Release Planning
Play the self-organization game “Human Knots” by forming teams of 5-6. Groups where team members can untie themselves first win. The time frame for this activity will be decided by your instructor. Each team will have a Scrum Master and Product Owner chosen by group members.
-
Sprint Burndown Chart
Acquaint yourself with the Sprint Burndown Chart concepts by taking part in the ball point game. There will be 5 iterations and the number of points being expected at the end of the release will be communicated to the team.
- • Definition
- • Why and when to use a sprint burndown chart
- • Information obtained from sprint burndown chart
- • Define and understand sprint burndown chart.
- • List 3 primary reasons to use a burndown chart.
- • Learn how to create and calculate a burndown chart.
- • Explain how to adjust upcoming sprints based on the burndown.
- • List 3 critical information obtained from a burndown chart.
- • List 5 merits and 2 demerits of using a burndown chart.
- • Understand 5 common errors that lead to misleading information in burndown charts.
-
Release Burn-Up Chart
Take part in the ball point game and understand the in-depth concepts of release burn-up charts and why Scrum teams use them. There will be 5 iterations and once the sprint is completed, the team will put a mark on the release burn-up as to how many points are completed.
- • Definition
- • Features
- • How to create a release burn-up chart (steps)
- • Understand the importance of having a release goal (based on historical data and agreement).
- • Demonstrate the importance of release burn-up in understanding the current status.
- • List 2 differences between burndown and burn-up charts.
- • Explain how to adjust release planning (if needed) based on the burn down.
- • Tell one primary advantage of a burnup chart over a burndown chart.
-
Product Planning
-
User Stories
Be a part of the Lego Building Blocks game wherein participants will be asked to write user stories for every activity involved. The game will entail 3 iterations and attendees will prepare user stories that will cover the features and functionalities along with acceptance criteria.
- • What are user stories?
- • Structure/format of user stories
- • INVEST criteria
- • Define and explain user stories and understand the importance of user stories in real-time projects.
- • Explain the 3 Cs in user stories.
- • Discuss the importance of acceptance criteria and list 3 scenarios that might arise when the acceptance criteria are not met.
-
Agile Estimation
Learn more about the “what” and “how” of Agile estimation with our in-class Agile board game “Scrumble”. In an interactive setting, this game will let you analyze the common challenges faced by Scrum team members during implementing different estimation techniques in Agile.
- • Definition
- • Benefits of Agile Estimation
- • Agile estimation techniques
- • List and demonstrate 5 benefits of Agile estimation.
- • Understand the 7 popular Agile estimation techniques and decide which one is the best for your project.
- • Discuss 3 benefits of Relative Estimation and Planning Poker.
- • List and explain 3 common mistakes made while using Relative Estimation and their negative impacts.
- • Discuss in detail the 5 critical steps in Planning Poker.
-
Planning Poker
Know everything about planning poker from our popular poker card estimation game. Team members/estimators have to privately select one card and the value on each card would represent the story point. Once all cards are revealed, the values need to be discussed.
- • Definition
- • Benefits
- • Participants
- • How to play planning poker
- • Planning Poker rules
- • List 5 benefits of planning poker estimation technique.
- • Decide the best sequence for the values (story points) on cards for your real-time projects.
- • Discuss in detail the 5 critical steps in Planning Poker.
- • List 3 points to heed for employing planning poker for distributed teams.
