Learn the value of being agile, the core elements of value-driven development, techniques for agile planning and how to collaborate with customers, clients and your team. In this course, you will get an overview of several different agile techniques, methods and ways of working so that you can evaluate for yourself what suits you and your team best. The course fulfills the requirements for ICP certification (ICAgile Certified Professional) and provides 24 Scrum Alliance SEU.

In this course, you will get an overview of several different agile techniques, methods and ways of working so that you can evaluate for yourself what suits you and your team best. We go through different possibilities with agile methods and several different agile tools.

The course fulfills the requirements for ICP certification (ICAgile Certified Professional) and provides 24 Scrum Alliance SEU.

Course objectives

• Apply values ​​and principles from agile methods to product development
• Compare the most popular agile methods, including Scrum and Kanban
• Understand the cultural and mindset challenges of working agile
• Create a constant focus on delivering customer value
• Develop self-organizing teams that frequently deliver quality-assured products with high business value

To achieve ICAgile certification, you need to get a passing score on the exam written at the end of the course.

Outline

Introduction to agile values ​​and principles

• Formulate agile values ​​and principles
• Understand the principles of the mindset behind Lean
• Comparing agile methods with traditional methods

Comparison between different agile methods
Scrum

• See Scrum as a framework for self-managing teams
• Place Scrum in theories of process management
• Understand roles, artifacts, and events within the Scrum framework

Kanban

• Identify the connection between Kanban and Lean's focus on removing waste from the work flow
• See Kanban as a path to change rather than a method
• Visualize the workflow by designing a Kanban board

eXtreme programming (XP)

• Explain the core values ​​of XP
• Develop software using XP's core practices
• Run a software development project using the XP process

Comparing Scrum and XP with Kanban

• Incorporate the difference between Scrum boards and Kanban boards
• Timeboxing with Scrum and XP
• Understand why Scrum requires cross-functional teams while Kanban is neutral

Value-driven deliveries
Focus on business value

• Prioritize delivering features with high business value
• Expressly focus on business value and product quality
• Develop requirements and solutions together during development

Iterative and incremental deliverables

• Deliver "early and often" for ROI (Return on Investment) and feedback
• Comparing Scrum and Kanban as "pull" systems
• Classify different requirement types for value-driven planning

Promote self-management within a development team
Mapping roles and responsibilities

• Comparing the model with an agile "Feature Team" with a traditional "Component Team"
• Change roles and responsibilities to create a self-directed team
• Lead teams rather than managing tasks

Transition to self-governance

• Facilitate cross-functionality and team learning
• Empower the team to manage their own development process
• Navigate conflicts so that they drive team behavior in a positive direction

Grow agile teams

• Develop genuine collaborative behaviors
• Acquire soft skills for servant leadership
• Adapt coaching styles to the agile team's experience and maturity level

Participation for customers and users

• Define customers and other stakeholders
• Consider customers as individuals or groups that extract or generate business value
• Consider other stakeholders as people or groups who have a holistic approach or who put obstacles in the way
• Prioritize customers as the most important and relevant stakeholders

Engage users

• Understand the differences between how Scrum and XP teams interact with customers
• Write user stories to drive conversations with different types of customers
• Break up user stories so they fit into inspection and adaptation cycles

Plan, monitor progress and adapt operations using agile methods
Plan for business value

• Visualize the products to "see the big picture"
• Plan at the release level, iteration level and at the daily level
• Coordinate work through information bulletin boards (Information Radiators)

Monitor progress

• Estimate work with relative size units (eg Story Points)
• Track progress by measuring speed and/or how long the cycles take
• Have reviews and retrospectives to adapt the product and process

Remove obstacles

• Perceive obstacles as opportunities for continuous improvement
• Keep technical costs down with test automation, Test-Driven Development (TDD) and continuous integration

information boards (Information Radiators)