I wrote a LinkedIn article after being inspired by Joost Icke's original piece. Johan Cruijff had some amusing sayings but also had a very deep understanding of team performance as a system.
This was a blog post on one of the sites of Highberg , in Dutch. The blog is about: 1) Agile is not a goal 2) Change should be continuous, not following a plan 3) Change should not be top-down or bottom-up but collaborative Drie Agile-transformatielessen van een Agile Coach In de wereld van Agile ontwikkeling deelt onze Agile Coach, Dennis Mansell, de drie meest waardevolle lessen die hij heeft geleerd. Ontdek de essentiƫle inzichten voor een succesvolle Agile transformatie. Hoe ben je in de wereld van Transformaties terecht gekomen? Bijna tien jaar geleden ging ik over van een leven als zeiler en ondernemer naar fulltime Agile coach en/of programma manager. Ik kende Scrum inmiddels redelijk goed uit de softwareontwikkeling en had wat Design Thinking ervaring. Dit was een zeer zeldzame combinatie, want veel bedrijven wilden toen "Agile" werken. Intussen heb ik organisaties gezien van startups tot eeuwen-oude familiebedrijven, online gemeenschappen tot overheidsinstant...
Traditional management wisdom tells us that 'time is money'. However, during the years I have come to find that there is no conflict between learning and productivity, even that productivity increases as learning increases. To me this is such a no-brainer that I have had some difficulty in understanding why some managers might be against learning. In fact, on closer inspection, the managers I came across were not actually against learning, they are just against 'wasting time' and unaware that their push to save on wasteful activities such as study time was in fact destroying productivity.
The Company to Consumer model under threat teambrunel.com Originally I became interested in agile software development when I started to discover a pattern between great teamwork in yacht racing and teams that produced software. Some of the greatest software teams that I worked with were people working together on open source projects. Thousands of people worked together in self-organizing teams throughout their technology stack, much as if they had belonged to a single organization. Could that model work in more organizations? There was an essential thing missing though - most of these teams were making things that were useful to themselves but not necessarily to a user who would be willing to pay. Motivation was often very idealistic: working on free (as in liberty) software usually entailed working for free (as in beer). Some projects became wildly successful, imagine a world without Linux , Wikipedia or Bitcoin . But do you remember Joomla , M...
Comments
Post a Comment