© Mapbox, © OpenStreetMap

Speaker

Peter Häfliger

Peter Häfliger

agile software developer and product owner

Zürich, Switzerland

Actions

Peter has been working in the software industry since 2001. Since 2008, he's been with Avaloq, a leading financial technology and service provider, in various roles such as software developer, project manager, team lead, technical business analyst and scrum master. He currently serves as product owner of Business Process Automation and Client Lifecycle Management. He has great interest in agile practices but also in more technical software engineering and programming topics, mathematical and algorithmic puzzles, languages, literature and music.

Area of Expertise

  • Information & Communications Technology

Topics

  • Agile Methodologies
  • DevOps Agile Methodology & Culture
  • Agile software development
  • Software Engineering
  • Scrum
  • Kanban

rhythm, flow and goals - agile practices for the devops age

We used to have yearly releases and waterfall projects. Then we moved to monthly releases and Scrum fit just perfectly.

The Scrum Guide defines the Sprint as a fixed-length event of one month or less and as the heartbeat of Scrum: a continuous cycle of planning, doing, review, retro and repeat. With monthly releases, it is usually the release which is demonstrated, reviewed and celebrated in the Sprint Review.

But if we now move into the devops age of continuous integration and delivery, with possibly hundreds of releases every single day, is then the scrum sprint still the right heartbeat? Or should we aim for uninterrupted flow with Kanban instead? Or quarterly goal-setting with OKRs? Or both?

wholesome talk - language patterns for feedback and learning

My personal blog's motto is "don't just talk agile, walk agile!" because I have always been well aware of the trap of merely using agile jargon instead of actually applying an agile mindset and living agile values.



However, I recently came to understand that while the "walk" is important, the "talk" has its own challenges. As L. David Marquet - the author of “Turn the Ship Around!” - shows in his second book “Leadership is Language”, some language patterns can actively promote diversity of opinion, invite feedback and foster learning, while others unintentionally limit diversity, suppress feedback and prevent learning.



That's why I would like to explore what I call "wholesome talk" in an agile work environment.

Peter Häfliger

agile software developer and product owner

Zürich, Switzerland

Actions

Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.

Jump to top