Duration and language:
Onsite training - 24h - 3 days each 8 hours (including breaks).
Onsite training - 24h - 4 days each 6 hours (including breaks).
Online training schedule:
- 09:00 - 11:30 online session,
- 11:30 - 12:30 break,
- 12:30 - 15:00 online session.
The training is in English.
The training is intended for:
- project and development teams,
- programmers, IT system architects,
- business analysts and novice Product Owners,
- DevOps specialists,
- novice Scrum Masters,
- specialists and domain experts.
The Applying Professional Scrum for Software Development™ training is intended for people who have practical experience in Scrum or who already participated in an introductory training - Applying Professional Scrum™. Experience in working on complex IT solutions covering a number of business domains and requiring the cooperation of a large group of specialists divided into one or more teams is recommended.
For online training, it is required to meet technical requirements: https://valkir.pl/en/online-training/.
- During the COVID-19 pandemic, training will be delivered online (Location: online) or onsite (Location: city_name) in accordance with current governmental guidelines for the participants’ safety.
- Preparation and training performed by an expert, Scrum.org accredited trainer (PST), Agile and Lean experienced consultant.
- $200 voucher for the PSD exam and a certificate of training completion, issued by Valkir Academy (in Polish or English).
- In the case of taking the PSD exam within 14 days and failure, the participant is entitled to a free second-shot attempt.
- Scrum.org accredited training materials, participant manual and exercises requisites.
- License for performing the training (paid to Scrum.org organization).
- 21 Personal Development Units (PDUs) for members of the PMI PMP.
- Lunch and catering (drinks and snacks). Not applicable to online training.
Each training participant will receive an indefinite voucher for a one-time approach to the certification exam at the Professional Scrum Developer (PSD) level. Exam (in English) takes place at Scrum.org, it is an online exam. In the case of taking the PSD exam within 14 days and failure, the participant is entitled to a free second-shot attempt.
|Date||Location||Price per person|
|2021-04-27||Online||1125 EUR||Sign up|
|2021-09-06||Warsaw||Early bird: 1035 EUR, standard 1125 EUR||Sign up|
Expert performing the training:
What is the Applying Professional Scrum for Software Development™ training?
Applying Professional Scrum for Software Development™ is an accredited training program from Scrum.org, targeted at teams developing complex projects and creating IT products/services. Based on the experience of a group of experts from both Scrum.org and recognized world leaders in software development, a program was created to increase the efficiency of complex software development processes.
The use of such practices as e.g. pair programming, TDD, BDD, Clean Code or SOLID allows the cross-functional development team in Scrum to provide high quality product/service increment. By introducing standards for architecture design, technical documentation and the automation of integration/implementation processes, it is possible to continuously deliver business value, minimizing the risk of error or technical debt.
The training takes the form of a workshop based on discussion and simulation of software development in Scrum, including 3 sprints, each lasting about 2 hours. The most benefits it can bring to organizations that are in the process or are planning to provide software in an Agile approach. Each sprint ends with a debrief and discussion on how to adapt the practices used to the participants' own situation. Workshops are usually performed in one of the following languages: .NET, .NET core, Java, Python or C++, and the participants choose the language together.
Who is behind this?
From the engineering side, the vast majority of practices originate from the eXtreme Programming (XP) paradigm, which was formulated by Kent Beck, which was subsequently joined by, among others Ward Cunningham and Ron Jeffries. The assumptions of this paradigm are determined by guiding values, events and specific engineering practices.
As part of Scrum.org, so-called stewards, these are PST (Professional Scrum Trainers) trainers looking after the area of engineering practices, continuous development, improvement and ensuring consistency with the possible use of these practices as complementary to the Scrum framework.
- Introduction - Establishing common grounds and goals for the training
- Let’s get to know each other better. Simple exercises that allow the participants to integrate quickly.
- Initial discussion and clarification of participants’ expectations.
- Agreeing upon workshop’s goals, training backlog refinement and contract for effective participation.
- Restart: (re)definition and review of the Scrum framework
- A brief guide to Scrum theory (S tacie, Cynefin), pillars and values.
- Discussing roles and responsibilities in Scrum, how they relate to job positions.
- Events and processes in Scrum, their duration, frequency.
- Scrum artifacts and ensuring their transparency.
- Product Backlog
- What is Product Backlog, how to manage it and how it governs product vision?
- Estimation: Precision guesswork or point of dialogue.
- How to slice “the Elephant”? Decomposition and requirements analysis techniques.
- Overview of value based product management.
- What is DevOps? Philosophy, benefits and consequences of use.
- What are the 3 ways of DevOps and how it all fits Scrum?
- Leveraging DevOps toolsets (backlogs and boards, version control, build and release management).
- Discussion and hands on Azure or Gitlab exploration.
- Code and Software Quality
- Code quality versus software quality.
- Testing during software development: TDD, ATDD, BDD.
- Clean code, SOLID, refactoring and other engineering practices.
- Rational use of metrics in software development.
- Technical debt: risks, ways to deal with it and avoid it.
- Emergent Architecture
- Big Design Upfront versus Emergent Architecture.
- How to check if your solution fit for current project purpose?
- Monolith or Microservices. Is it always worth starting with microservices?
- Discussion of common challenges, traps and anti-patterns.
- Exercise in the use of reference architecture.
- Simulations and case studies
- 3 sprints simulation (average 2h each) during which participants will experience the concepts, techniques and discussed challenges.
- Case studies presentation in reference technologies: .NET, .NET core, JAVA, Python, C++ (with the possibility of mutual agreement by the group and the trainer).
- The workshop will be supplemented with trainer tips and mini retros between successive sprints/iterations of a given exercise.
- Organizational challenges following the Scrum framework
- Differences between a work group and a team, based on the Tuckman model
- Characteristics of the cross-functional team, competences and responsibility.
- Open discussion of raised questions, challenges and doubts as well as the next steps necessary to introduce Scrum in the organization.
- Training summary
Training goals:What are the challenges we address?
- How can I explain to others what are engineering practices, DevOps and in relation to Scrum?
- How can I improve the continuous delivery of product/service increment without loss of quality?
- How can I design valid tests tailored to the development stage of a product/service?
- How can I consciously manage technical debt - accept, avoid or remove it?
- How can I automate integration, implementation and testing processes?
- How can I design emerging architecture while monitoring stability?
- How can I be sure that I devote time and resources to meeting the actual needs of the client?
What benefits do you get?
Training enables participants to better understand how to use engineering methods and practices to effectively deliver product/service increment that meets the acceptance criteria. It contains theoretical knowledge and practical methods taken from product management, business analysis, systems architecture, code quality, stakeholder management, change management and many other topics.
As a result of this training, participants from different areas of the organization will:
- know and understand aspects needed for effective, incremental development with software quality assurance,
- acquire skills necessary to apply mentioned methods in practice,
- understand how and why new methods can positively affect their work.