We all love Star Wars, don't we? One of the most spectacular, intriguing, and charming characters of this series is Yoda – the Jedi Master. He is a symbol of wisdom, thoughtful leadership, and courage. What I found surprising is that those characteristics are also the ones we would like to attribute to a Servant Leader in any organisation! 

            In this presentation I will analyze seven aspects of Yoda’s approach and leadership behavior that can directly inspire current and future Leaders in any IT organisation and improve agility. Lessons focus on either the approach to teamwork and collaboration or individual perspective that can help you stay focused on what’s of most value. Yoda’s seven lessons aim at identifying a way Leaders can grow their teams and themselves. I also focus on how they build adaptive organisations that are designed to respond to change. As a bonus I will describe one fatal decision Yoda made in his leadership history and how we can build on it not to repeat his mistake in our everyday work.

At dev / agile / product conferences software or product development using Scrum framework is almost always described from one perspective. Either it’s Developer(s) showing how to write code or Product Owner communicating requirements / identifying business value or Scrum Master trying to increase agility / transparency of work. This always gives you a limited view on the process in which whole Scrum team is heavily engaged.

            In this presentation three speakers – Dev, PO and SM - show 360⁰ view of real case software development using Scrum framework. In 30 min we will show how full stack development team was able to develop real digital products for QVC – one of the biggest video-commerce and e-commerce business in UK. You will be able to see how deliver value to your customers – from requirements gathering to coding to experimenting with new ways of working. We show how the focus on value delivered to the customer changed the way we work with business and among the developers and QAs within the Scrum Team. Only by having transparency around the work done by three Scrum roles, you will get the most out of the framework itself and your team.