What is Servant Leadership? Is it just “unblocking all the things and getting out of the way”?
In this session, Mike would like both to challenge that misrepresentation of this classic leadership model and to show Servant Leadership’s present-day relevance to the challenges of Lean-Agile transformation.
We'll explore six transformation strategies (honestly, with their respective pitfalls) and the opportunities for demonstrating and developing Servant Leadership that go with each of them.
There's a lot of buzz on Kanban right now in the agile software development community. Since Scrum has become quite mainstream now, a common question is "so what is Kanban, and how does it compare to Scrum?" Let's clear up the fog. What are these things? Where do they complement each other? Are there any potential conflicts? The purpose of this session is to clarify Kanban and Scrum by comparing them, so you can figure out how these may come to use in your environment.
Software is everywhere today, and countless software products and projects die a slow death without ever making any impact. Today's planning and roadmap techniques expect the world to stand still while we deliver, and set products and projects up for failure from the very start. Even when they have good strategic plans, many organisations fail to communicate them and align everyone involved in delivery. The result is a tremendous amount of time and money wasted due to wrong assumptions, lack of focus, poor communication of objectives, lack of understanding and misalignment with overall goals. There has to be a better way to deliver! Gojko presents a possible solution, impact mapping, an innovative strategic planning method that can help you make an impact with software.
Gojko is a strategic software delivery consultant who works with ambitious teams to improve the quality of their software products and processes.
He specialises in Lean|Agile quality improvement, in particular Agile testing, Specification By Example and behaviour-driven development.
Gojko’s book Specification By Example was awarded the number two spot of the top Agile books for 2012 and won the Jolt Award for best book of 2012. In 2011, he was voted by peers as the most influential Agile testing professional and his blog won the UK Agile award for the best online publication in 2010.
We spend a lot of time in product development trying to minimize uncertainty and its negative consequences. We push people to do careful estimates; we adopt Six Sigma programs to reduce variability; we conceal uncertainty by padding estimates and using buffers. We strive to protect our carefully designed plans from the hostile assaults of a random and uncaring universe. We celebrate robust solutions that remain imperturbable in the face of variability. In reality, this robustness can come at high cost: it can make our projects slower, less efficient, and ultimately less successful. What would happen if our goal was to thrive in the presence of uncertainty, instead of just trying to survive it? How would we design and operate development processes if we wanted to get the best outcomes precisely when uncertainty was highest? In this keynote, Don Reinertsen will present a different perspective on development process design.