Agile methods
Innovations need the courage to experiment – and and the permission to fail.
Agile methods help. But not everywhere and at every price. As described in the overview text on “agile methods”, a context is required in which the use of agile methods makes sense and is possible. “Why?” are we introducing agile methods? What is “purpose” here? Are we following a fashion, do we want to appear more attractive as an employer? Or are we facing up to the changed reality and ready to question the truths of yesterday? Do we really live values such as openness, trust, courage and personal responsibility? Are a constructive error culture and working in iterative loops natural and practiced principles for us? If you “only” find these topics on the slides of the last management conference, pause before you proclaim agile transformation in your company in white sneakers.
These and other questions need to be asked before the introduction of agile methods can generate added value for your company.
You will probably encounter various dilemmas during the introduction: On the one hand, agile methods such as design thinking can only work if the group/company allows and even encourages a high degree of self-direction and autonomy. On the other hand, and here there is often a major misunderstanding, a “high degree of discipline” is required when using such methods. At the method level, “agile” does not mean “let’s do this creatively and flexibly with lots of colorful post-its”. When I conduct a “brain dump session”, it is not another form of “brainstorming”, although it is often used that way, and a “daily standup” is not one of the usual “morning meetings”. Agile methods are more regulated in their pure form than many people realize. And that’s a good thing!
But which of the many methods are suitable for me and my team in my context?
There are now many agile methods that start at different points in the development process. However, they have clear similarities that relate to both agile product development and agile service development: They start from the user (the customer) and solve their problems. They are designed for speed and therefore work with prototypes. Only when it is clear how the target group will react to a product or service is it launched on the market. Agile methods have a clear goal, but are geared towards the changing needs of the user. You approach the solution iteratively, i.e. in small steps of approximation.
In the following, we present the three most frequently used agile methods (actually frameworks) that are an integral part of any agile transformation: Scrum, Design Thinking and Design Sprint. But of course we can also “do” all the others. Just ask us and we will be happy to advise you here with regard to your company.
If you already have a business model or a product in mind and want to start working on or developing it, it is best to use Scrum. As a framework for agile project management, this method provides the framework for an iterative approach in which teams organize themselves independently, work together optimally, sometimes make decisions autonomously and ultimately reach their goal faster. Scrum also enables the use of many different tools. In most companies, a Scrum interval (“sprint”) lasts 14 days. During these two weeks, the team members work on their task packages, but meet frequently to exchange ideas. Part of the Scrum process involves constantly checking the quality and functionality of a product or business model and regularly obtaining feedback from the customer.
This means that adjustments can be made at any time and the end result improved. Scrum is not only a helpful method of self-organization in product or software development, but also in many other areas. You will establish a completely new way of working in your company, which your teams will see as an exciting journey. Admittedly, it takes a bit of courage to get involved. Try it anyway, you can only get better. We will of course be happy to help you.
Design thinking is one of the best-known agile methods and is more of a basic approach. Before you introduce design thinking, you should know that the consistent use of this framework can turn your company and your business model upside down. Design thinking is characterized by doing everything possible to promote creativity. The use of colorful materials, brightly designed workspaces and a variety of PostIts has become a trademark. And the more multidisciplinary the creative team is, the more outstanding the ideas are. And that is almost always an enrichment for the process and for the result.
Another basic feature of design thinking is its strong customer focus: how do customers behave in everyday life, what are their needs, wishes and fears? Once as much information as possible has been gathered, the process of finding a solution begins
with a variety of creative techniques. Once the decision has been made in favor of an idea, it must be tested repeatedly with the customer using a prototype and, if necessary, adapted and improved. We only implement what has proven itself one hundred percent.
In any case, Design Thinking promises an extremely creative way of working that demands flexibility from each individual and from teams. We will be happy to guide you through the design thinking process or enable you to carry it out independently.
Design Sprint was developed at Google and is methodologically very similar to Design Thinking. But while a design thinking process can take months, the design sprint only lasts five days. The aim is to develop ideas quickly and, under certain circumstances, to discard them again quickly. By consistently taking the customer’s point of view into account, the customer virtually sits at the table and is presented with a prototype at the end. The design sprint is carried out by a group of around eight employees, because here too it is essential to consider as many perspectives as possible. A clear set of rules is required to be able to actually present a product after a maximum of five days. For example, the task for each of the five days is precisely defined: Day 1: Gather information; Day 2: Ideate, i.e. collect ideas;
Day 3: Select ideas to be turned into prototypes; Day 4: Prototypes; Day 5: Testing with the customer/user. No matter how the process develops, you will have a result at the end.
bt has a lot of experience with design sprints and is happy to apply the method in your company. By the way, sometimes we have already completed the design sprint process in four days.
