Category

Agile organization

Category

I have been asked a lot lately about strategies for change in the company and how agility can be carried in 100% of the areas of the company. My first answer is of course: 100% agile is unlikely to exist and agility doesn’t actually need a special change strategy. Agility can be seen in exactly the same way as the introduction of a product, or it can be introduced in the classic way according to Kotter’s change strategy. Every model has its origin in the considerations of Kurt Lewin, who classified a change in three phases in 1943. Basically, two forces work in organizations: own security strivings and habits that demand the maintenance of the status quonew technologies, executives new competitors who demand changes Kurt Lewin then established in 1947 that change only takes place as soon as the force of necessity for change is stronger than that of habit.…

“What leeway do you have in your projects to try out other approaches and to consciously go new, simple paths? To what extent do companies give project managers, scrum masters and product owners as well as consultants a free hand in choosing the procedure, in project planning, in communication or in the type of cooperation in the team (keyword self-organization)? And with which approaches are you successful? ” This is what the project magazine asks in the latest blog parade with the topic ” More success through new freedoms in the project “. I am happy to take part in this blog parade and answer the questions asked from my point of view. I am part of a team (with 5 people) that provides infrastructure services for a major customer. The product is a mixture of hardware and software such as a car, airplane or an ICE. So that the…

I often take part in expert interviews on the blog and thus help students and other researchers. I am often asked about my assessment of the following question: How agile / digital do companies become? The question is often aimed at 5 or even 15 years. On the other hand, I am also asked the question in another form: Will only agile companies survive?Do all companies have to become agile? Furthermore, the Andre Häusling’s blog parade with the question: “Is agility an obsolete model or a future model?” and the hashtag AgileDeadOrAlive to this article. I would therefore like to write a blog article with my assessment. I will go into this a little further and give a specific answer. However, this is only my personal opinion. 2 theses on agility and digitization of companies In my PhD I have a roundtable carried out. This brought together 12 board members…

The streaming service Spotify was founded in 2006, today has sales of over 4 billion euros and has 3,000 employees. This success story can be traced back to a wide variety of factors. One of them is the agile organizational form of Spotify, which is now taken as a model by numerous companies. Reading tip: Spotify model in traditional companies Spotify model – how does it look in practice? If you open current magazines, you will find the following headline: ” ING – a bank on speed “. ING DIBA is aiming for an agile change based on the Spotify model with the help of a major restructuring. Furthermore, squads, tribes and chapters from the Spotify model can also be found in the IT of Deutsche Telekom. Telekom currently has around 15 squads, which are distributed over four tribes. Quote from an agile coach at Telekom is to: “We have…

Large companies such as Daimler or Bosch in particular have been promoting the trend of “Working out Loud” for a while now. In the course of New Work and digitalization this seems the next level Agile organization to be. But what does it actually mean? Just another fad or a serious concept? What is Working out Loud about? The term “working out loud” has actually been around for almost a decade. The term first appeared in 2010 in a blog article by IT consultant Bryce Williams. Williams dealt in his text with the idea of publicly sharing work and knowledge so that added value is created for everyone. To do this, he created the term “Working out Loud” (WOL) from the previously known concepts of social collaboration and collaborative learning. After WOL was discussed in more detail by John Stepper in his book 5 years later, it quickly found acceptance…

You have been playing with the idea for a long time more agility in your company bring to? Do you want to know how agility is structured? Here is a guide to what to look out for if you want to introduce an agile business organization. 5 pillars for agile business organization Agility arises from the realization of 5 important dimensions. If you observe these measures, an agile business organization can be implemented much more easily in your company. Or they make it through to lead even more agile . Target image In order to introduce agility and, in particular, an agile company organization, a vision is required first of all. What should be changed? Just project or product management or the entire company? As a manager, you should therefore ask yourself to what extent the company should become more agile. This applies above all to the areas of personnel…

I blog a lot about medium-sized companies and thus also about the specific problems they have. However, I do not want to neglect the specific problems of large corporations. To this day I am interested in the specific problems with scaling Scrum on a large scale. Managers from three different corporations wrote to me via my blog asking me to come over. Of course I gladly accepted this invitation. The aim was an intensive professional exchange (4h). The agenda of the workshop was as follows: What is the current status of the scaling of Scrum in corporations? What are the challenges? How could this be solved? tip : You are welcome to read additionally what the Differences between medium-sized companies and corporations are. Scaling agility in corporations The last time I was really active as an agile consultant in corporations in 2015, the first teams were organized according to agile…

In the IT sector, DevOps has been gaining in importance for a long time. But what is actually behind the term and what is the aim of the concept? We get to the bottom of these and other questions. What is DevOps actually? The term DevOps is a combination of the English words “Development” and “Operation”. The concept originating from the IT sector deals with practices for automating processes between software development and IT. The aim is to accelerate the development of software solutions and then to test and release them more quickly. In order to unite the strengths of software developers and IT teams in the course of this, the concept specifies to link the areas more closely with one another. More integration and new perspectives instead of working in isolation. For this, DevOps makes use of techniques such as agile or continuous delivery. The goal behind it: Gaining…

Lately, a lot of my contacts have been talking about the term Objective Key Results (OKRS). This is a new management method that sets goals based on key performance indicators. But what is actually behind it? What are Objective Key Results (OKRS) The method was invented by Andy Grove and John Doerr and first mentioned on Google in 1999. You can currently find the method at Oracle or Twitter, for example. The T3N describes this as follows: Measurable key results are assigned to each objective (objective). The successes are measured at regular intervals and new OKRs are defined. The OKRS are not determined at the company level, but are negotiated with each team. A manager then has the task of synchronizing these together with all employees and adapting them to the company’s goals. The idea behind the goals is that they cannot be fully achieved and are therefore an incentive.…

“It is they who drive the transformation of companies and industries: courageous lateral thinkers, risk-takers who are different and visionaries. Every change, every innovation needs people who think beyond borders, question the status quo and convince others of their ideas. We call them thought leaders, rebels, or drivers”so Haufe in the invitation to the latest blog parade with the hashtag organizational rebels. I would like to participate in this and have set myself to answer the following questions on this topic: What are my very personal experiences in my life as a rebel? What best practices can I share – and what have been my biggest mistakes that others can learn from? In the first step I would like to tell my very personal story about a change in which I was involved for a whole year. From this story I derive best practices that can help an organizational rebel…

By continuing to use the site, you agree to the use of cookies. more

The cookie settings on this website are set to "Allow Cookies" to provide the best browsing experience. If you use this website without changing the cookie settings or click "Accept", you agree to this.

close