Drie Agile-transformatielessen van een Agile Coach


 

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

Comments

Post a Comment

Popular posts from this blog

Agile after Corona

Image
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 , Mutuala or Erpal ? It was
Read more

Why Scrum? Why Agile? Answering a Project Manager

Image
I'm a Project Manager, how will we organize projects with Scrum? Scrum has no Project Managers. Projects are generally only focussed on developing something, whereas Scrum Teams design, create and sustain something. Managers are generally responsible for something or some people, whereas Scrum Teams are self-organizing. In Scrum - as long as a product exists, it has a Product Backlog of everything that will be done to it. That includes, but is not limited to what can be termed 'projects', however it is ordered so that working on it, produces the maximum amount of value, first. In project management, value is assumed to be a function of the 'iron triangle' - this budget, spent in this time, with this scope of solutions will make the project done. Quality is a cost to these variables: running out of time or money whilst still making the same scope will lead to reducing the quality. This is working ‘inside out’ - from what we can make, towards value for customers. S
Read more

Deep Democracy meets Scrum

Image
About a year ago, I went to a training given by Sandra Bouckaert and Lydie van de Laar on the basics of Deep Democracy .  My wife was 35 weeks pregnant and I was working on a project with worryingly limited financing so I was not exactly in the perfect 'zen' mindset for a day of mind-battering brainstorming.  I expected to leave the day dazed and confused, yet found myself in the car buoyed up and even excited about what I had just experienced. Deep Democracy is a method developed in South Africa at the end of the apartheid regime and specializes in getting minority views heard.  It is concurrently a team-building tool and an ideation tool. 
Read more