Agile Scrum Master Training and Certification Course in Stuttgart, Germany

• Interactive instructor-led Agile Scrum Master training
• Highly qualified, certified, and accredited trainers
• Agile Scrum Master course adhered to global standards

• Get Agile Scrum Master Study Guide created by subject matter experts
• 96% pass success rate
• Get to know industry best practices and case studies

• Prepare better with sample mock tests
• EXIN official Agile Scrum Master certificate

The daily agenda of the 2-day Agile Scrum Master Training Course is detailed below:

• Day One
• Agile Way of Thinking
• Agile concepts
• The candidate can:
• Explain the Agile way of thinking
• Explain how Agility brings predictability and flexibility
• Continuously improving the process
• The candidate can:
• Explain how to use continuous improvement
• Other frameworks and other Agile frameworks
• The candidate can:
• Recognize other frameworks and methodologies: Waterfall, Crystal, Lean, XP, DSDM, DevOps.
• Applying Agile principles in IT Service Management 2.5%
• The candidate can:
• Explain how to apply Agile principles to IT Service Management
• Scrum Master Role

• Responsibilities and commitment
• The candidate can:
• Explain which tasks and responsibilities belong to the Scrum Master role
• Explain which solutions are suitable for solving problems
• Explain which tools to us to facilitate the team

• Coaching the team and mediating
• The candidate can:
• Explain when and how to mediate through conflict
• Explain how to coach and challenge the team
• Explain the importance of training

• Other roles (Product Owner, Development Team)
• The candidate can:
• Explain all roles within the Scrum framework

• Agile Estimating, Planning, Monitoring and Control
• Writing and maintaining the Product and Sprint Backlog
• The candidate can:
• Explain why a good Definition of Done is so important
• Create and recognize good User Stories
• Explain how to maintain the Product Backlog and how to add Product Backlog Items
• Agile Planning
• The candidate can:
• Explain iterative planning in all the planning moments: Roadmap, Release and Sprint Planning
• Explain the role of the Scrum Master in all the planning moments: Roadmap, Release and Sprint Planning
• Agile Estimation
• The candidate can:
• Explain when and how to estimate using Story Points, Ideal Hours and Ideal Days
• Explain how to guide a planning session, with and without Planning Poker
• Recognize errors in estimation
• Explain how to calculate ROI (Return on Investment)
• Tracking and communicating progress
• The candidate can:
• Identify impediments, deviations, roadblocks and other obstacles that influence the progress positively and negatively
• Explain how to create Information Radiators, how to interpret them and how to act on the results
• Explain commonly used tracking methods (Burn-Down Chart, Velocity…)
• Staying in control
• The candidate can:
• Explain how to manage issues, bugs and informing
• Day Two
• Complex Projects

• Scaling Agile projects
• The candidate can:
• Explain how to use the Product Backlog in a scaled environment
• Explain how to scale to larger teams using Scrum-of-Scrums

• Suitability of Agile for different types of projects
• The candidate can:
• Explain in which cases it is not possible to use Agile
• Identify the limits of a Scrum Team

• Agile administration in tooling and tool integration
• The candidate can:
• Explain which tools can help a team to use or adopt Agile and thereby increase the quality of the development process

• Adopting Agile
• Introducing Agile
• The candidate can:
• Explain which project management activities are important to include in the transition plan
• Explain which milestones are important in the transition
• Explain how to deal with resistance to change
• Self-organization
• The candidate can:
• Explain what self-organization means and how project management is shared
• Explain what it means to have a cross-functional team
• Agile requirements and proper environment
• The candidate can:
• Explain what changes in culture need to be made before adopting Agile
• Explain what physical changes need to be made before adopting Agile