Posted by Daniel Burm in the late afternoon: December 23rd, 2011
My motto regarding innovation is: being a first mover is a strategic choice, moving fast isn’t. Agile and scrum can help you move fast, so how can it accommodate innovation?
Posted by Kristian Spek mid-afternoon: November 26th, 2011
When I start a new consulting job at an organization, I like to ask people how their organization became the organization it is today. Most of the time, people start telling me about the history of their organization or the values and goals they have. People sometimes start telling me about the people who work in the organization. But I have never got an answer that fullfilled my question completely. What made organizations what they are right now? After reading ‘Die Frage nach der Technik’ written by Martin Heidegger (1889-1976), I got an answer that could help me structure all the answers people gave to me. (more…)
Posted by Daniel Burm around lunchtime: November 25th, 2011
I am convinced that the next blue ocean of agile minds can be found in the creation of sharing ecosystems that are built on shared purpose, trust, intuition and a facilitation of the deeply wired human urge to cooperate as a collective. Understanding that modern day individualism is smothering our effectiveness is a catalyst for our drive to start working together and forming the effectiveness of these systems.
(more…)
Posted by Geert Bossuyt at around evening time: October 16th, 2011
Market Driven Development (aka Agile Fixed Price)
I propose a paradigm shift in developing software to deliver business value.
For a team to satisfy a business need,
it is not the amount of work that defines the time needed,
it is the available time that defines the amount of work that can be done.
The deadline is part of the need, and not the result of estimation or planning techniques.
With the deadline being part of the need, the Team and the Product Owner have a shared budget ( = number of Sprints ) to realize the Vision.
Instead of using Poker to give insight in the estimated time of delivery, let’s create a Market Place where Product Owner and Team ‘negotiate’ on the complexity of each story.
Posted by Pieter Rijken mid-afternoon: September 23rd, 2011
In Agile methods focus on short feedback cycles and regular delivery of (business) value. Both are supported by having short lead times. Kanban is one of the tools to manage the flow of tasks and reduce lead times.
This article shows how to reduce lead times even further.
One of the mechanisms in Kanban to manage flow is to explicitly set a limit on the amount of work in progress for a process step. By modifying this to include part of the next process step, this article shows that the amount of work in progress is limited more and therefore also lead times are reduced.
(more…)
Posted by Daniel Burm in the early morning: September 16th, 2011
Agile companies that want to create real ownership, have to say goodbye to traditional stakeholdership and embrace “joint company stakeholdership”. Remain to be an old-skool stakeholder in an agile environment and you will possibly act as a “stakekeeper” instead of a “stakesharer”, therefore withholding the company “staketakers” from focus on value and real ownership of results.
(more…)
Posted by Daniel Burm mid-afternoon: August 26th, 2011
Some time ago I saw an interview on a talk show that intrigued me. It kept me thinking and even to this date the topic discussed still puzzles me. In modern day organizations and markets more and more emphasis is placed on efficient behavior which should lead to better results and better ROI. Effective behavior is also sometimes mentioned, but way less often and it’s is not elaborated upon as much as efficiency. Maybe it’s because both nouns have two f’s and a lot of e’s, so people tend to forget about effectiveness?