EXIN-Agile Scrum
Master

ENROLL NOW

Course Description

EXIN Agile Scrum Master is a certification that looks to confirm both skills and knowledge of the Agile framework and Scrum methodology.

Agile Scrum is about working together to successfully reach a goal. Agile methodologies are popular approaches in software development and are increasingly being used in other areas. Scrum practices include establishing cross-functional and self-managed teams, producing a working deliverable at the end of each iteration or Sprint. This certification focuses on adopting Agile or Scrum in the workplace and taking on the role of Scrum Master.

Accredited By

Agile Scrum Foundation

Examination details

  • Exam duration: 90 minutes
  • Exam duration: 90 minutes
  • Number of questions: 40
  • Pass mark: 65% (26 out of 40)
  • Open book/notes:no
  • Electronic equipment/aides permitted: no

Who should take it?

The Agile way of thinking is best known in the field of software development but the principles are increasingly being applied in other types of projects. Scrum is the most used Agile methodology and is suitable for all professionals looking to keep their knowledge up to date with the latest developments in the fields of IT and Project Management, particularly those leading or participating in projects. In particular, the certification is suitable for professionals working in the areas of: Project Management; Software development; IT Service Management; and Business Management.

Syllabus – Agile Scrum Master

It is mandatory that all delegates must hold either the ITIL Foundation Certificate or the ISO 20000 Foundation Certificate to qualify to sit the Practitioner examination and attend the training course.

1.1  Agile concepts

1.1.1 Explain the Agile way of thinking

1.1.2 Explain how Agility brings predictability and flexibility

1.2  Continuously improving the process

1.2.1 Explain how to use continuous improvement

1.3 Other Frameworks and other Agile Frameworks

1.3.1 Remember other frameworks and methodologies: Waterfall, Crystal, Lean, XP, Atern, DevOps.

1.4 Applying Agile principles in IT Service Management

 1.4.1 Explain how to apply Agile principles within IT Service Management

2.1 Responsibilities and Commitment

2.1.1 Explain which tasks and responsibilities belong to the Scrum Master role

2.1.2 Explain which solutions are suitable for solving problems

2.1.3 Explain which tools to use to facilitate the team

2.2 Coaching the Team

2.2.1 Explain when and how to mediate through conflict

2.2.2 Explain how to coach and challenge the team

2.2.3 Explain the importance of training

2.3 Other roles (Product Owner, Development Team)

2.3.1 Explain all roles within the Scrum Framework

3.1 Writing the Backlog

3.1.1 Explain why a good Definition of Done is so important

3.1.2 Create and recognize good user stories

3.1.3 Explain how to maintain the Backlog and how to add Backlog items

3.2 Agile Planning

3.2.1 Explain iterative planning in all the planning moments: Roadmap, Release and

Sprint planning

3.2.2 Explain the role of the Scrum Master in all the planning moments: Roadmap,

Release and Sprint planning

3.3 Agile Estimation

3.3.1 Explain when and how to estimate using Story Points, Ideal Hours and Ideal Days

3.3.2 Explain how to guide a planning session, with and without Planning Poker

3.3.3 Recognize errors in estimation

3.3.4 Explain how to calculate the ROI (Return on Investment)

3.4 Tracking and Communicating Progress

3.4.1 Identify impediments, deviations, roadblocks and other obstacles that influence the progress positively and negatively

3.4.2 Explain how to create Information Radiators, how to interpret them and how to act on the results

3.4.3 Explain commonly used tracking methods (Burn-Down Chart, Velocity,…)

3.5 Staying in Control

3.5.1 Explain how to manage issues, bugs and informing people outside of the Team

4.1 Scaling Agile Projects

4.1.1 Explain how to use the Product Backlog in a scaled environment

4.1.2 Explain how to scale to larger teams using both Scrum-of-Scrums and SAFe-framework

4.2 Suitability of Agile for different types of projects

4.2.1 Explain in which cases it is not possible to use Agile

4.2.2 Identify the limits of a Scrum Team

4.3 Agile administration in tooling and tool integration

4.3.1 Explain which tools can help a Team to use or adopt Agile and thereby increase the quality of the development process

5.1 Introducing Agile

5.1.1 Explain which project management activities are important to include in the transition plan

5.1.2 Explain which milestones are important in the transition

5.1.3 Explain how to deal with resistance to change

5.2 Self-Organization

5.2.1 Explain what self-organization means and how project management is shared

5.2.2 Explain what it means to have a cross-functional Team

5.3 Agile requirements and proper environment

5.3.1 Explain what changes in culture need to be made before adopting Agile

5.3.2 Explain what physical changes need to be made before adopting Agile

Get More Information





    I agree to be contacted over email and phone.


    For Corporate Batches and Group Discounts,
    kindly email to info@vyomlabs.com

    Still confused? Take expert advice now.

    TALK TO EXPERT