SCRUM Master Certification Training
Viswa Online Trainings is one of the world’s leading online IT training providers. We deliver a comprehensive catalog of courses and online training for freshers and working professionals to help them achieve their career goals and experience our best services.
Learners : 1080
Duration : 25 Days
About Course
Our Scrum Master is a professional who leads a team using Agile project management through the course of a project. A Scrum Master facilitates all the communication and collaboration between leadership and team players to ensure a successful outcome. Scrum is an Agile framework for developing complex projects, most often software. The Agile project management methodology uses short development cycles, called sprints, that results in the continuous improvement of a product or service. There are many Agile frameworks, and Scrum is a popular option for fast-moving projects. Enroll now and get certified in it.
SCRUM Master Training Course Syllabus
✔ Why Agile?
✔ Traditional Development
✔ Problems with traditional software development
✔ Usage of features in a system
✔ Makings of a new approach
✔ Agile Manifesto
✔ Principles behind the Agile Manifesto
✔ Authors of the Agile Manifesto
✔ Agile Project Management
✔ Agile Project Management Life-cycle
✔ Agile Project Management Framework
✔ APM Framework
✔ What is Scrum?
✔ Certified Scrum Master
✔ Professional Scrum Master
✔ PMI-ACP
✔ Agile Methodologies
✔ Project Properties in Crystal
✔ Samples of Crystal
✔ Feature-Driven-Development
✔ Roles in FDD
✔ Processes in FDD
✔ Project tracking in FDD
✔ Project tracking methodology
✔ FDD usage guidelines
✔ Dynamic Systems Development Methodology (DSDM)
✔ Planning in DSDM-Atern
✔ DSDM Principles and techniques
✔ eXtreme Programming
✔ XP Values
✔ XP Practices
✔ XP Benefits
✔ Agile Unified Process
✔ Agile Unified Process (AUP)
✔ Agile Unified Process – System Development
✔ Scrum
✔ Scrum Life-cycle
✔ Stakeholders
✔ Chicken and Pig roles
✔ Management of stakeholders
✔ Scrum life-cycle
✔ Product Owner
✔ Product Owner’s role
✔ Prioritization
✔ Cost-Benefit Analysis
✔ Prioritization based on Value and Risk
✔ Prioritizing requirements - MoSCoW
✔ Prioritizing requirements – Kano Model
✔ Prioritizing requirements – Relative weighting method
✔ Scrum life-cycle
✔ Scrum Master
✔ What does a Scrum Master Do
✔ What the Scrum Master Should NOT do
✔ Scrum life-cycle
✔ The team – aka Developers
✔ Building a Scrum team
✔ Building empowered teams
✔ Role of a Manager
✔ Manager 2.0: A new role for a Manager
✔ Some specialist roles you may want
✔ Time-boxing
✔ Advantages of time-boxing
✔ Time-boxing
✔ Release
✔ High-level view of a release
✔ Sprints
✔ Factors in selecting a Sprint duration
✔ Intensity of work
✔ No changes in a Sprint
✔ Daily Scrum
✔ Sprint Review
✔ Also check during a review
✔ Sprint Retrospective
✔ What is a Sprint Retrospective
✔ Making retrospectives effective
✔ Making retrospectives effective
✔ Product backlog
✔ Product, release, and sprint backlog
✔ User story
✔ Story card information
✔ Multiple stories may be required to complete a feature
✔ Epics
✔ Writing good stories
✔ Splitting user stories
✔ Splitting user stories (big picture)
✔ Splitting user stories (user experience)
✔ Splitting user stories (Others)
✔ Refactoring
✔ Pair programming
✔ Continuous integration
✔ Practices of continuous integration
✔ Configuration management
✔ Quality in Agile
✔ Scrum Quality – Home truths
✔ Planning for a Sprint
✔ Test-driven development
✔ Test-driven development
✔ Advantages of TDD
✔ Definition of “Done”
✔ Principles behind Agile planning
✔ Iterations allow for mid-course corrections
✔ Multiple levels of planning
✔ Release planning
✔ Steps to planning a release
✔ Release Planning
✔ Velocity
✔ Sprint planning
✔ Velocity-driven sprint planning
✔ Commitment-driven sprint planning
✔ Planning for each story
✔ Keep this in mind before finalizing the plan
✔ Principles behind Scrum estimation
✔ Estimation techniques
✔ Types of estimates
✔ Uncertainty in estimates
✔ Over-estimation and under-estimation
✔ What contributes to size
✔ Measures of size
✔ Ideal days
✔ Story points
✔ Estimation techniques – Planning poker
✔ Affinity estimation
✔ Affinity estimation - process
✔ Monitoring Scrum Projects
✔ Definition - Metrics
✔ Types of metrics
✔ Metrics do’s and don’ts
✔ Charts in Scrum
✔ Burn-down chart: Iteration level
✔ Burndown chart: Project level
✔ Burndown chart: Bar style
✔ Burn-up and Burn-down chart
✔ Cumulative Flow Diagram
✔ Parking lot diagram
✔ Escaped defects found
✔ Velocity chart
✔ Progress Chart
✔ Niko Niko calendar
✔ Information radiators
✔ Information radiators: Big visible charts
✔ Information radiators
✔ Scrum on large projects
✔ Scrum-of-Scrum
✔ Product coordination teams
✔ Scrum on maintenance projects
✔ Distributed scrum teams
✔ Best practices in distributed scrum
✔ Structure-1: Team in India; PO in US
✔ Structure 2: Team split in two locations
✔ People practices in distributed Scrum
✔ Practices in distributed scrum
✔ Practices in distributed scrum
✔ Scrum-Contracting
✔ Fixed Price/fixed scope
✔ Scrum in fixed-price projects
✔ Transitioning a team/project to Scrum
✔ Transitioning a team/project to Scrum
Live Instructor Based Training With Software |
Lifetime access and 24×7 support |
Certification Oriented content |
Hands-On complete Real-time training |
Get a certificate on course completion |
Flexible Schedules |
Live Recorded Videos Access |
Study Material Provided |
SCRUM Master Training - Upcoming Batches
Coming Soon
8 PM IST
Coming Soon
AM IST
Coming Soon
4 PM IST
Coming Soon
AM IST
Don't find suitable time ?
CHOOSE YOUR OWN COMFORTABLE LEARNING EXPERIENCE
Live Virtual Training
-
Schedule your sessions at your comfortable timings.
-
Instructor-led training, Real-time projects
-
Certification Guidance.
Self-Paced Learning
-
Complete set of live-online training sessions recorded videos.
-
Learn technology at your own pace.
-
Get access for lifetime.
Corporate Training
-
Learn As A Full Day Schedule With Discussions, Exercises,
-
Practical Use Cases
-
Design Your Own Syllabus Based
SCRUM Master Online Training FAQ'S
- Product Owner: The product owner is in charge of enhancing ROI by determining product features, prioritizing these items into a list, determining what should be prioritized for the next sprint, and much more. These are re-prioritized and modified on a regular basis.
- Scrum Master: This person assists the team in learning how to use Scrum to maximize business value. The scrum master removes roadblocks, keeps the team focused, and helps the team embrace agile methods.
- Scrum Team: A Scrum Team is a group of people who work together to guarantee that the stakeholders' needs are met.
Agile is an iterative project management and software development methodology that enables teams to deliver value to clients faster and with fewer difficulties. An agile team provides work in small, consumable pieces rather than putting all on a "big bang" release. Requirements, strategies, and outcomes are all evaluated on a regular basis, giving teams a natural method for adapting to change.
- Commitment: Scrum teams must be able to function as a team to accomplish a common goal. This entails putting faith in one another to complete their jobs and deliver to the best of their abilities. It will only occur if each team member is completely dedicated to the project and the team.
Scrum masters and team leaders can aid commitment by facilitating good sprint preparation and shielding teams from mid-sprint scope changes and undue product owner pressure. - Focus: Each member of the team must remain focused on the work at hand as well as how it affects the sprint goal in order to get the most out of each sprint.
Scrum masters might limit the number of tasks or priorities assigned to each team member throughout sprints to help them stay focused. Individuals can also stay focused on their assigned work by encouraging full team participation in daily Scrum meetings. - Openness: Each member of the team must be absolutely truthful about their personal progress in order for the Scrum team to accomplish the maximum progress in the quickest period possible. The daily Scrum meeting's goal is to identify and solve problems. That won't happen if team members aren't honest about any problems or hurdles they're facing. Team members must also be willing to collaborate with one another and see each other as vital contributors to the project's success.
Being upfront with their teams is one of the finest methods for Scrum masters to foster openness. Giving honest feedback at daily Scrum meetings is not only crucial for making required adjustments, but it will also inspire team members to be honest and open in return. - Respect: Respect in a Scrum team implies understanding that no single individual or their contribution is more valuable than another. Respect also entails putting your faith in your coworkers to complete their jobs, listening to and considering their suggestions, and praising their achievements.
Scrum masters may assist their teams to develop regard for each other by exhibiting respect for the product owner, stakeholders, and team members. - Courage: Scrum teams must have the guts to be genuine, upfront, and honest about the project's progress and any bottlenecks they encounter, both with themselves and with stakeholders. Members of the team must also have the bravery to seek assistance when needed, attempt new techniques or procedures that they are unfamiliar with, and respectfully disagree and engage in open debate.
Scrum masters, like respect, can first and foremost promote courage by displaying it. To avoid mid-sprint adjustments or scope creep, the Scrum Master must have the confidence to stand up to stakeholders and product owners
- Transparency: Those accountable for the outcome must be able to see important components of the process. Transparency necessitates that those elements be defined by a uniform standard so that viewers may comprehend what they are seeing. For example, all participants must speak the same language when referring to the process, and those performing the job and those inspecting the resulting increment must have the same concept of "done."
- Inspection: To spot undesired deviations, Scrum users must examine Scrum artifacts and progress toward a Sprint Goal on a regular basis. Their inspections should not be so frequent that they become a hindrance to their work. Inspections are most effective when performed diligently at the point of work by skilled inspectors.
- Adaption: If an inspector concludes that one or more parts of a process deviate beyond acceptable boundaries, the method or the material being processed must be modified. To avoid future deviation, an adjustment must be performed as soon as feasible.
Our Page: VISWA Online Trainigs