Evolutionary Kanban - channel the painHolger HammelAt the agile prague conference on 15th of sept. 2013 I presented about some aspects of our evolutionary Kanban approach at the mobile.de mobile app teams. You can find the slide at the end of this post. Without a little context than what is visible on the slides it is hard to get idea. So I’ve chosen to put some text first.
A few words about my background: I love XP and the software craftmanship movement. I am working with Scrum and especially Kanban a lot. I used to be a Java Developer, now working as a dev manager, sometimes switching to the agile coach hat.
Last 2 years I have had the honour to build up different dev teams at mobile.de. We used an evolutionary approach to build up our process.
When building up the team the first thing I concentrated on was flow. Without flow and a basic understanding of this concept you won’t get anywhere.
There have to be a lot of different absolutely necessary elements to get successful teams, like purpose, fun, innovation and craftsmanship. These are not covered here so much.
Usually flow is visualized as a nice, slow, peaceful floating river. That provides a good feeling right?
I like to look at it more like that: you are in the middle of a dangerous, unknown, wild river in the mountains. You can be thrown with full force against big stones.
That causes pain, right? Or you don’t move at all, that is at least boring.
So what means pain in our agile product delivery context?
Blocked Stories and inefficiency in general. Nobody wants to be inefficient. So pain means:
I cannot finish what I have started.
For continuous improvements, for getting better step by step you first have to find and feel the pain. Teams, managers usually really like to work around these pain points – but that is a false understanding of efficiency.
If you can’t remove the pain within the team, you have to channel it back to where it belongs.
Feeling the pain is necessary for change!
The good thing is: you can change - your team and even the environment. Work in Progress (WIP) Limits show the pain. They are your weapon against wrong efficiency towards Kaizen, towards continuous improvement.
In the presentation there are some examples of of challenges and what have been improvements to our way of working and how we are working with others.
Presentationanuragji20010This document provides instructions for recovering passwords using Ophcrack LiveCD, including downloading and burning the Ophcrack LiveCD ISO file, waiting for it to load and display hard drive partition information, and then waiting for it to recover passwords so the user can log on to Windows with the recovered password.
Ib reg formsamg28The document outlines the registration process and terms of service for State Bank of India's (SBI) online banking service called "OnlineSBI".
It includes sections on general information about registration requirements, security measures like user IDs and passwords, SBI's terms regarding transactions and dispute resolution, customer obligations to maintain secrecy of login credentials, and dos and don'ts for using the online banking service securely.
The document provides customers with important details regarding how to register and conduct transactions securely through SBI's internet banking platform.
Process applied to software developmentRenan HuancaThis document discusses agile software development processes like XP, Scrum, and Kanban. It provides definitions and principles of each process. For example, it states that XP values feedback, simplicity, and embracing change. It also includes quotes about imagination, wasting time, and evolving rather than revolving. The document was created by Renan Huanca, a Java web developer, to share information about agile processes applied to software development.
Continuous development - Growing PainsJohn StevensonThis session focuses on the growing pains and successes of the software teams at Atlassian, when moving to continuous deployment and the opportunities they are creating towards continuous delivery.
When a company takes a big strategic decision, the impact it has on its people is a mark of how well its leaders understand the principles behind the agile approach.
The impact of this decision on the software development teams was to go from a 97 day iteration to a two week continuous deployment approach. Each team was given the responsibility on how they would achieve this and every team had different triumphs and frustrations
Specialist teams were also introduced to build up to specifically transfer knowledge and disseminate useful practices (with context), from UX to build management and wider DevOps practices
лекция 1 регуляция мцcdo_presentationCовременные представления о регуляции менструального цикла. Становление репродуктивной системы женского организма.
Детский сад № 13 "Хрустальный" (город Ирбит)Site365.ruПлан работы городского методического объединения по направлению краеведение за 2014-2015 учебный год
Ib reg formsamg28The document outlines the registration process and terms of service for State Bank of India's (SBI) online banking service called "OnlineSBI".
It includes sections on general information about registration requirements, security measures like user IDs and passwords, SBI's terms regarding transactions and dispute resolution, customer obligations to maintain secrecy of login credentials, and dos and don'ts for using the online banking service securely.
The document provides customers with important details regarding how to register and conduct transactions securely through SBI's internet banking platform.
Process applied to software developmentRenan HuancaThis document discusses agile software development processes like XP, Scrum, and Kanban. It provides definitions and principles of each process. For example, it states that XP values feedback, simplicity, and embracing change. It also includes quotes about imagination, wasting time, and evolving rather than revolving. The document was created by Renan Huanca, a Java web developer, to share information about agile processes applied to software development.
Continuous development - Growing PainsJohn StevensonThis session focuses on the growing pains and successes of the software teams at Atlassian, when moving to continuous deployment and the opportunities they are creating towards continuous delivery.
When a company takes a big strategic decision, the impact it has on its people is a mark of how well its leaders understand the principles behind the agile approach.
The impact of this decision on the software development teams was to go from a 97 day iteration to a two week continuous deployment approach. Each team was given the responsibility on how they would achieve this and every team had different triumphs and frustrations
Specialist teams were also introduced to build up to specifically transfer knowledge and disseminate useful practices (with context), from UX to build management and wider DevOps practices
лекция 1 регуляция мцcdo_presentationCовременные представления о регуляции менструального цикла. Становление репродуктивной системы женского организма.
Детский сад № 13 "Хрустальный" (город Ирбит)Site365.ruПлан работы городского методического объединения по направлению краеведение за 2014-2015 учебный год