Dennis Mansell

 Agile (a.k.a. the agile industrial complex) is dead (or dying, or undead... read on). Of course Agile has been declared dead many times, but now we can see that there are fewer visitors to Agile conferences, fewer people looking to get certified as something Agile, fewer people are calling themselves Agile Coach. Dying The Agile conferences have talks about how very large companies do Agile, which tools they use to collaborate or how non-IT departments do Agile, topics that were also there ten years ago. Agile conferences have yet to adapt to topics like decentralized enterprises, fluid teams, remote-only organizations, AI helpers and commons governance. The certification crisis seems to follow a similar pattern: was this ever a good measure? Those courses were meant for setting off down a path that makes you better at discovering and uncovering effective ways of working - perhaps we're running out of people who have yet to start, whilst not offering enough to th

In November 2020, the new Scrum Guide was released, mentioning for the first time a ‘Product Goal’. This block is designed to help you find your product goal.  Attribution to The Liberators , the Scrum Guide and Harvard Business Review .   Preparation (online): Make a Mural from this template You need a video conferencing meeting with 'rooms' of up to 4 people Preparation (physical):  Super Sticky notes in at least 4 colours Print Elements of Value Pyramid as handout Flip-over sheets Flip-over of empty Elements of Value Flip-over of Wicked Questions Flip-over of Integrated ~ Autonomy Flip-over for Actions/Steps 15% Solutions

I've made browsing my CV a bit less cumbersome:

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

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

 After a day's sailing, we've dropped anchor, cleaned the boat and poured ourselves a drink. “So - what is it you do again?” “I’m a Scrum Master.  It’s like the Master of Sail on tall ships.” “What - like the second-in-command?” “No, I don’t have a position in the hierarchy.  I just make sure the boat and crew are fit for purpose and help the sailors and staff understand what is going on.” “Why would an organisation need that?” “Many organisations approach products as if it were an industrial process like transport.  They load the cargo containers as full as they can get - calling it ‘scope’, then they plan very exactly how to drive from A to B to predict the costs and how long it will take to deliver. “For my clients, their product doesn’t actually match this industrial process very well.  I get them to think of it as if they were explorers trying to reach some distant shore. “They should pack very light and get great at teamwork so that they can travel

The second instalment of why Scrum, why Agile? What to say to a CEO... “What do you want?” “I have an idea that could be valuable to the company.” “You have 60 seconds” “We have a lot of people working on the product, but [enter employee survey here] shows that they are unhappy. They are also very clever, yet [some percentage of projects - usually ½ to ⅔] of our projects are failing - costing us a lot of money and frustration. Moreover [some big competitor] are moving faster than we are. Many of our people don't know who they create value for or why. “This is caused by our big plans and need to control the process. “We could take a small, self-organizing team, with all the necessary skills and permissions, and start releasing customer value early and often. It’s called Scrum - I’ve seen it work at a start-up but it also saved [some competitor] from going under.” “What’s in it for us? Sounds like we would lose control” “Scrum would at least show up