The Agile Scrum Product Owner Bridge training and certification is designed to equip a Scrum Master with the knowledge and skills to understand and perform the role of Scrum Product Owner, should they wish to change roles. The Scrum methodology is applied in areas of software development, IT service management, hardware development and science where a value of a product is increased in the context of continuous iterations.
A training in EXIN Agile Scrum Product Owner Bridge costs 460.00 Euro.
Training in EXIN Agile Scrum Product Owner Bridge lasts one day.
The certification in EXIN Agile Scrum Product Owner Bridge costs 102.00 euros plus VAT via agile-scrum-training.de instead of 173.74 euros via EXIN.
|Start - End||Booking|
|On request - On request|
Unfortunately, we do not offer full e-learning training in EXIN Agile Scrum Product Owner Bridge. We do offer exam preparation in EXIN Agile Scrum Product Owner on Udemy.
The exam preparation is approximately 1 hour and 15 minutes long. Participants can study content on agile scrum for the exam preparation. You can find the introduction in the following video.
In agile Scrum, there are three roles according to the Scrum Guide 2020:
The introduction of Scrum can be associated with difficulties, e.g. in established, older and long-established companies there may be specialist departments that only work together to a limited extent (establishment of silos). Scrum requires the right attitude, the courage to create new things, to reject them and to allow experimentation. Scrum is simple, deliberately incomplete, and aims at the collective intelligence of people.
The Scrum team is small (5-9 participants; by avoiding social laziness) and is multidisciplinary in structure to be able to develop a product such as a website, app or refrigerator in all task spectrums (testing, developing the software). The Scrum team must have sufficient skills. Scrum teams organize themselves independently and on their own responsibility. The Scrum team focuses on a product goal. Scrum teams must communicate well and be in the same room. It is attempted after each sprint, a period of one to four weeks of development time to create a functional increment (for example, a functionality of a software specified by the Product Owner) which creates a verifiable value. There are no hierarchies in a Scrum team. All Scrum members work together on a product backlog, a task list with the functions of the software or hardware.
When creating a Scrum team, existing position titles (such as Architect, Engineer, or Designer) remain. Roles are used to define a Scrum team, the framework of a Scrum project, and aims to promote the effectiveness and productivity of a Scrum team. A Scrum team is an interdisciplinary team and is difficult to assemble. The more complex and difficult the projects are, the more difficult it is to assemble an interdisciplinary team.
The developers create a task plan at the beginning of the project, the sprint, the sprint backlog for the sprint and a sprint goal. The tasks to be accomplished are reviewed daily and solution strategies are developed. Project deliverables are only accepted when the Definition of Done is met. The Definition of Done to a function are quality criteria in an increment like the color of a product or functions of a software. Dailies are recommended for collaboration between developers. In the dailies, difficulties are discussed and adjustments are defined. Each team member should contribute to the daily and learn from each other.
The Product Owner organizes the task plan. He develops and communicates the product goal. He monitors the pursuit of the goals and vision. He communicates and creates tasks in the task plan. He sets priorities in the task plan and ensures that the tasks are transparent, visible or accessible and can be understood. The challenge lies in the prioritization or the description of the tasks. The Product Owner must be given so much influence that he can autonomously decide which tasks can be prioritized higher and which lower. The organization must respect the decisions of the Product Owner (whether CEO or CTO). The Product Owner is the mouthpiece between stack holders (whether developers or management).
The Scrum Master coaches team members in self-management and effectiveness of collaboration. They support the achievement of the Definition of Done goals and the desired increments. The Scrum Master ensures that the Scrum Team can pursue its goals undisturbed. The Scrum Master ensures that the Scrum events take place positively, productively and within a time window or timebox. He ensures the effective definition of the product goals and the organization of the product backlog and thus supports the Product Owner. He makes sure that the task list is clear and concise. He supports the planning of the product based on measurable results (empirical approach). He tries to mediate between Scrum teams and stakeholders. The Scrum Master advises the organization in the planning and implementation of the project management Scrum.