Kanban vs Scrum? Which method leads to success?

Kanban vs Scrum
The question of which agile method is suitable for which project is not always easy. We try the comparison Kanban vs Srum.

Advantages and disadvantages of agile working methods

Those who decide to work agilely are spoilt for choice when it comes to methods. Kanban, Scrum or Lean Management are just a few of the keywords that are on everyone’s lips. Often, it is Scrum with its precisely timed sprints and user stories that those in charge choose. Whether this decision was the right one sometimes only becomes clear after a long process of trial and error. How can such a mistake be avoided?

Decision criteria for agile development methods

There is no generally valid answer to this, but some criteria can help to make a reorientation in the middle of a work process. The best way to explain this is to use a negative example in the case of a choice between Kanban and Scrum. Because it is also true in agile working that mistakes are the best teachers.

In our case, the client was faced with the challenge of organising a team that worked at different locations and whose participants did not all speak the same language. In other words, the best conditions for agile working. The task was to further develop a product that was in operation. Therefore, the choice of agile method fell on Scrum. With its clearly structured blocks, sprints and firmly outlined requirements described in user stories, this method is very popular in product development.

Adapting the agile approach

In our case, however, exactly what is otherwise an advantage became problematic: the requirements, which were precisely tailored to the team, did fit the mandate to further develop the product. In addition, however, the team had to take over the ongoing operation and support. As a result, critical defects were repeatedly added to the already existing tasks, the processing of which could not wait until the next sprint. The workload of the individual team members increased, as they felt obligated to their commitment to the user stories.

An adjustment of the method became necessary. After careful consideration, the decision was made to implement the task with Kanban. From then on, both the further development and the ongoing operation ran without further problems. But why was the Kanban method better suited than the Scrum method in this case?

Difference Scrum Kanban

It makes sense to look at the fundamental differences in the methodology of the two approaches. On the one hand we have Scrum. Here, precisely specified scopes of work are defined for a certain period of time and the progress is communicated in the daily routine. Here, it is not planned that the requirements change in the course of a sprint or that more are added, which works wonderfully well with a precisely outlined task without “disruptive factors”.

The Kanban method, on the other hand, is primarily about establishing a continuous flow of work. For this purpose, the individual work processes from the idea to the completion of the task are made visible in various so-called status columns. The starting point is usually a collection of prioritised pending issues, which are drawn up by the individual team members themselves. The ingenious thing about this is that only a certain number of tasks may be listed under the individual headings of the tables, i.e. it is not possible to start any number of new tasks before others have been completed.

Advantages of the Kanban method

This leads to tasks being completed, but unlike Scrum, it allows new requirements/ideas to be fed into the process. Of course, prioritisation of tasks and monitoring is necessary so that no “task corpses” are left on the way to completion. The product owner is responsible for monitoring the continuous process to ensure that no tasks are left undone.

Another difference is the focus of the dailies. While Scrum focuses on the team members, Kanban is more about organising the tasks and finding solutions to problems that arise.

More flexibility and faster work flow through Kanban

In our case, it became clear that Kanban had to be the method of choice because it fulfilled two requirements that were necessary for the successful implementation in the client’s sense: it was possible to feed in newly arising problems and, by focusing on the workflow, it guaranteed that both the activities that could be planned in the longer term and those that were newly added were completed.

What we have learned from this is that it is important from the beginning to examine exactly which factors play a role in the completion of a task in order to find the appropriate method. In keeping with the spirit of agility and the fault tolerance implicit in it, the courage is required to revise and reconsider a decision that has already been made if it becomes clear after the application has been launched that one has made a mistake in the choice of method.

Content:

Resilient in times of crisis: Adaptive or rather agile?

Resilienz Unternehmen
Companies must be able to react ever faster in the face of crises and rapid, disruptive changes. As with people, resilience plays an increasingly important role in this. But how can they achieve it?

How companies can position themselves for the future

 In a world characterised by crises and rapid changes, the concept of resilience is also gaining more and more importance for companies. But what does resilience mean in this context and how can the concept, which originates in psychology, be transferred to it? If you read up on the subject on the internet, two terms quickly come to mind: Adaptability and innovative learning culture.

Taking external factors into account

From these terms, it is not far to the buzzword agility. For a long time, agile working was seen as the magic bullet for making a company so crisis-proof that it could react adequately to the rapid changes so typical of our times and thus remain fit for the future. In the meantime, this way of working has lost its nimbus of being a universal remedy. What remains, however, is the need to adapt quickly to new circumstances in order to be resilient. But how can this best be achieved? This is where the topic of adaptive organisation comes into play. A one-sided perspective from which an agile way of working is introduced usually does not lead to the desired improvement. Instead, in the sense of systemic thinking, all systems, internal complexity as well as external circumstances such as competitors, market changes, wars must be considered and taken into account.

Resilient through a change of perspective

The decisive factor is therefore a change of perspective to the meta-level, i.e. a view from the outside of the company and its influencing factors. From this changed perspective, other possibilities arise and potential for improvement becomes visible. However, it is a fallacy that this potential can only ever be exploited by introducing an agile way of working. It is important to find the right means for your own organisation.  Because just because a method such as design thinking was the perfect solution approach for a topic, this does not mean that this approach will be the means of choice the next time. If we return to the initial question, it can be said that agile and adaptive are not mutually exclusive; rather, agility is a building block for creating an adaptive organisation.

However, the change from a classic or agile to an adaptive organisation can only succeed if it takes into account not only the external but also the human factors such as corporate culture, communication and the employees.

Balance between structure and flexibility

It is important to develop a balance between structures and flexibility. This is the only way to create a protected framework in which new creative spaces can open up and solutions can be found. In this way, a company can change sustainably and, in the spirit of resilience, protect itself against external influences. This process is never complete. Only when an organisation continues to develop is it protected in the long term against the disruptive influences of the outside world.

The conclusion to be drawn from the question of agile or adaptive is therefore that agility is usually part of an adaptive organisation, but its methods alone are not always sufficient; companies must always keep the big picture in mind when making adjustments and changes.

Content:

"Compatibility of family and work"

Vereinbarkeit Familie und Beruf
In our series of interviews on the occasion of our 20th anniversary, we are talking today to Cornela Kapl, who has helped shape the development of our company from the very beginning.

Cornelia Kapl, team leader talks about the focus of her work

What are your most important career steps at think tank?

I started in 2003 as a project manager. Later, I was involved in various IT projects on site with clients and managed software development projects in the area of banking software, including testing and support. When we expanded our range of services, I also worked as a security consultant. Since 2006, I have also been a member of the company’s supervisory board. One of the most important steps for me personally, however, was the start of my work as a team leader in 2019. Initially, I was responsible for five employees, but now there are 15. The special thing about this job is that I can actively help shape the working environment of the employees and promote the compatibility of family and career. As a mother of two children, this topic is also important to me personally. I really appreciate that at think tank you can develop professionally even if you work part-time.

You've been with the same company for almost 20 years. What is the most exciting thing about your work?

Overall, I’ve always had very interesting tasks that have changed over time. I particularly value working on and with people. In the beginning, we were a start-up and of course did a lot ourselves internally, for example marketing, accounting, office management. Gradually, we were able to create jobs for the different tasks. When I look back on my career, I see that I have virtually grown with the company and also helped to shape it, which gives me a good feeling. And today, like all the other employees, I can help shape the face of think tank, because a company can only grow through its employees.

What do you see as the milestones in the history of the company?

Professionally, it is certainly the expansion from the core business of software development via IT consulting to information security consulting. The development of our own sales department, which gave us access to two large car manufacturers, was a major milestone. At that time, our third pillar, IT security, was added.

The move from Freystraße to Messerschmittstraße to more representative premises was also important. With this move, we finally left the image of the “small clit” behind us. By gaining a large real estate platform as a partner, we have further expanded our image as a reliable partner. We have built up a relationship of trust as a constant external partner and now work with 4 project owners and 18 developers together on better solutions with the client.

What makes think tank different for you?

We differ from other companies in that we pay a lot of attention to our employees. We take individual needs into consideration, employees can actively contribute. Our board members work on projects themselves, so we don’t lead from the top down, but at eye level. Everyone who works at think tank can help shape the company, every opinion is heard. You can contribute right from the start, even as an intern or junior, everyone is equal.

The development from classic to self-organisation in 2018/2019 has further strengthened these processes. We see ourselves as a self-learning organisation in which more competences and responsibilities are assigned to the employees.

We also work agilely internally on many topics, for example, we have introduced OKR as a framework for modern management and thus involve all employees in important strategic topics. The development is far from complete, our organisation is in a state of flux and this year we would like to strengthen self-organisation even further.

How do you see the future for think tank? What is important?

We are currently in the process of focusing and positioning ourselves better, making our portfolio even clearer for our clients. Our great strength is that we are very reliable and flexible. Once we have won over a client, this often develops into a long-term partnership. In addition, we know our clients’ pains and can react flexibly to them. We have succeeded in making our working methods hybrid. Our employees can work flexibly from home as well as in the office. We make up for the lack of office communication with daily joint meetings in the morning and virtual coffee chats and other joint appointments.

What are your personal goals for the next few years?

For me, the compatibility of family and career and the creation of an optimal work-life balance remains a topic close to my heart. Many of our employees work part-time without any disadvantages or being put on the sidelines, which is often the case at other companies. In addition, I would like to further my own education in order to be able to master the challenges of digital work in the future.

Content:

Neuauflage ISO 27001 kommt

Iso 27001 neu
The ISO 27001 standard is adapted and receives some additions. What you need to consider when introducing an information security management system (ISMS) or during a new certification or re-certification.

What changes and what to consider

The ISO/IEC 27001 standard is not only getting a refresh and restructuring, there are also some changes to be aware of. However, all those who are already certified still have time to adjust to the changes, because the release of the new standard is not planned until the end of the year. After that, a transition period of three years is expected to apply. However, anyone planning an initial certification or introduction of an ISMS (information security management system) should do so on the basis of the updated guide, ISO 27002. This is because it has already been published since February 2022 and offers a good basis for implementation.

New title and restructuring of ISO/IEC 27002

The title of ISO 27002 is already new: From now on, it is Information Security, Cybersecurity and Data Protection – Information Security Measure. This is the standard’s reaction to the new challenges that companies are facing in the context of data security. While the old version still had fourteen subject areas and 35 measure objectives, these are now divided into the four main areas of Organisational Measures, Measures in Connection with People, Physical Measures and Technical Measures. This is to ensure better readability. In addition, the number of controls has changed from 114 to 93. This change is due to the fact that some controls have been combined. However, the new version of ISO 27002 does not contain fewer required measures, but eleven controls have been added.

Innovations and necessary steps for ISMS certification

New controls include web filtering, data masking, physical security monitoring and information deletion. But what does this mean for the re-certification or new certification of an ISMS? Especially some of the new controls, such as physical security monitoring, where it must be ensured that it is clear at all times who was in the company’s premises and when, could pose new challenges for smaller companies. How big the effort for the changeover is certainly depends as much on the size of the company as on its structures. This can only be determined after a close look at existing measures. What is certain, however, is that companies should already start analysing the gap between the existing ISMS and the one required by the new standard. Those planning an initial certification according to ISO 27001 should immediately work on the basis of the new regulations in order to avoid having to adapt existing, newly implemented processes and documentation.

"My vision: creating innovations for people"

Mensch im MIttelpunkt
"For me, the focus is on people." This is what Mohamed Chergui, one of the founders of think tank Business Solutions AG, says. As the IT and business counselling company celebrates its 20th anniversary, he talks about his goals and greatest successes in an interview.

think tank founder Mohamed Chergui in an interview

When did you first think about founding your own company?

The idea came to me during my student days in Germany. At that time, a fellow student and I updated all the programmes on a company’s computers at night by going from computer to computer with a CD. That was good for earning money, of course, but we also thought about how we could do it better. That’s when we came up with the idea of networking the world together to help people do their work. That made the direction I wanted to go in clear: new technologies and IT. My diploma thesis was about how to install software once, deploy it and then use it indefinitely.

You were offered a job at a consulting firm, but you preferred to become self-employed. Why?

I wanted to realise my own ideas and work innovatively right from the start. It was also important for me to combine the two worlds of Tunisia and Germany in order to create a synergy from the different mentalities. Initially, I and my colleagues started in Tunisia and worked with partners in Germany. We first wanted to take time to strengthen the bridge to Germany and adapt the structures in both countries, and then scale the business with the resources in Tunisia. It became clear that it is important to establish a presence in Germany as a window to Europe. Think tank Business Solutions AG was then founded in December 2002.

What were the first years like?

In the first few years we were often something like the fire brigade. We were deployed wherever there was a fire, because we were set up from the beginning to be able to react quickly. In addition, we have always relied on the latest technologies. This is how we were able to convince customers like Osram and BMW of our merits and can now look back on almost 20 years of successful cooperation. Our first projects were, for example, the optimisation of the filling of ATMs as well as the reduction of returns of the Springer publishing house from 1,000,000 to 150,000 to 200,000 within one month with the help of AI.

What were tt's biggest successes in terms of innovation?

We developed an automatic news dispatcher for dpa. This was based on the first use of an XML database with keywording in Germany and was developed as part of a diploma thesis. Even today, many good ideas are generated in this way, as we still supervise three to four diploma students a year in Tunis.

We developed the first online grocery delivery service for Karstadt. However, we were ahead of time and it was not accepted by the customers. It was important for us to be able to expand our expertise in web applications. At Osram, we implemented the first digital asset management for video and image management back in 2002, which we still maintain. In the health sector, we helped to develop the health card.

To date, we also have a wealth of experience in banking finance, ranging from online transaction processing to risk analysis regarding money laundering. We have been supporting PlanetHome as a full-service provider in the field of real estate since 2011, and together we are developing a platform on which both real estate agents and prospective buyers can take care of everything related to the purchase of a house or flat.

In the automotive industry, we are broadly positioned, from the development of an electronic calculation model to the conception and implementation of a tool for testing car parts to collaboration on an application for agile process planning.

You mention the topic of agile here. For some years now, the think tank has been increasingly focusing on agility. What is agility for you?

Developing something is very difficult because you have to react quickly. We realised pretty soon that we had to coordinate at short intervals. To do this, we set ourselves internal deliveries every week, which were reviewed by the quality assurance team the following week. So basically we were already working agile there without calling it that. The change to an agile organisation was therefore only the logical step for me on the path of digitalisation, which we have been following for a long time.

How do you see yourself as a boss?

For me, it is important to have connections, to work with people. The basic prerequisite for this is trust. I trust my team and let them decide a lot for themselves, because teamwork is very important to me. I don’t like prohibitions and I believe in flat hierarchies. The worst thing for me is when I influence someone to change. Everyone should be able to develop as they wish. First of all, there is no “must” with me, you can talk and discuss about everything.

What do you see in the staff?

Every person is special and the most important thing for me is that I perceive and value everyone as a person. I find it’s best to let people run themselves. That way I can learn from their experiences and their knowledge. Because everyone is innovative and can contribute in this way. That way, everyone benefits and a sense of “we” can develop. For me, think tank is much more than just a job; my employees are like a family to me.

What is your personal vision for the future?

I would like think tank to continue to establish itself as a think tank and contribute to simplifying people’s lives, bringing people closer together with the technologies that are available to us.

Content:

Agile transformation begins in the mind

agile Transformation
The topic of agility and agile transformation has arrived at most companies as an alternative to classic workflows. But to this day, some misconceptions persist among both proponents and critics of agile working.

The six biggest prejudices about agility

The topic of agility and agile transformation has arrived at most companies as an alternative to traditional work processes. But to this day, some misconceptions stubbornly persist among both proponents and critics of agile working.

Agility is chaotic

Until today, many decision-makers in companies believe that working agile means that there are no fixed responsibilities. The result is organisational chaos that no one can keep track of. In reality, however, there are requirements that have to be met even in agile working. What is not specified is how these are to be implemented. The responsibility for this lies with the team. The advantage is that there is no basis for assigning blame and the focus is on solving the problem.

If I use agile methods, I am agile

Another misconception is that it is already enough to introduce agile methods such as Scrum or a Kanban Board in order to benefit from the advantages of agile working. But there is much more to agility. A prerequisite for the successful implementation of the agile transformation is that it is incorporated into the company’s goals. Only in this way a corresponding agile mindset can develop among the employees and the company management.

Agility only works for software development and start-ups

If you start from this premise, it is also quickly clear that agile project management works in many areas. After all, agility is a matter of mentality and means above all that all employees are willing to take responsibility and to design and adapt their processes themselves according to the tasks to be solved require. This enables companies to react better to the ever faster changing circumstances.

Agile working is the answer to everything

Conversely, this does not mean that agile working makes sense for every company or every task. If the existing structures and processes work well, there is no reason per se to adapt them, as change causes unrest and must be accompanied. A regular review of the existing organisation always makes sense, because as the Corona pandemic showed, circumstances can change quickly.

Agile transformation is done in three months

The experience with the pandemic and the necessary adjustments associated with it have shown that change takes time. The same is even more true when introducing the agile way of working. Not only do the processes have to be adapted, but the entire corporate culture has to be changed. The transformation towards agile working is an ongoing process in which the narrative that exists in every company has to be reworked and developed.

Agility no longer needs leadership

The last misconception closes the circle. Because of course agile organisations need leadership. However, the understanding of a leader is different. He or she is part of the team and becomes a coach, creating the framework conditions so that the team members can carry out their work as undisturbed as possible. Important here is communication at eye level and a pronounced tolerance for mistakes.

If one takes a closer look at these prejudices, several conclusions can be drawn: Firstly: every company should check for itself whether and to what extent agile working makes sense for its own goals. Secondly, anyone who decides in favour of agile transformation should be aware that, in addition to the external structures, the attitude of the employees must also change. Because agility begins in the mind. That’s why the agile transformation needs time and often support from outside.

Content:

More investments through simplified lending

Kreditvergabe für mehr Investitionen
A trip to Antananarivo, the capital of Madagascar, marked the start of the concrete implementation of the project of an online platform for applying for loans, which the think tank (tt) is carrying out on behalf of the government of Madagascar.

Government of Madagascar commissions think tank

Workshops and meetings to plan the project

A delegation from think tank Business Solutions flew to Madagascar with a finished concept and UX design. In four full-day workshops with the various partners, all details for the implementation were clarified. In addition, the project staff from all organisations were able to get to know each other in this way in order to clarify roles and responsibilities and to ensure that the project runs even more smoothly. In addition, further meetings were held with payment providers to guarantee the connection to the interfaces with the other platforms such as payment solutions, electronic signature and with the RCS-CM trade registry of Madagascar. A highlight of the trip was the signing of the official project contract by Mrs. Micheline Hery Manantenasoa, Head/President of PIFM and Yassine Kaaniche of think tank and with the local IT partner IBONIA. IBONIA is to support think tank on site, organise appointments and provide all necessary information for the project. After the go-live, it is planned that IBONIA will support the tt team with training and support.

Project members and go-live

In total, five major organisations belong to the project team besides tt: the International Finance Corporation (IFC), part of the World Bank Group, PIFM (Project d’Inclusion Financière de Madagascar), RNCS (Ministry of Justice of Madagascar), UGD (Unité de Gouvernance Digitale), EDBM (Economic Development Board of Madagascar) and tt’s local partner IBONIA. After the successful kick-off meeting, nothing now stands in the way of the go-live on 3 November this year.

Why is digitalisation so slow in Germany?

Digitalisierung in Deutschland
Germany is having a hard time with digitalisation. What are the causes for this? The reasons that companies give for not starting or failing with digitisalisation projects are manifold. Important issues are a lack of know-how in the companies and too high costs.

Background, causes and solutions

Corona has provided a digitalisation boost in some areas, but overall Germany continues to lag behind in digitalisation. In a study by the Berlin-based European Center for Digital Competitiveness (ECDC), Germany only ranked 17th among the digital upstarts of the G20 countries. Why is Germany having such a hard time with digitalisation?

What does digitalisation mean: a clarification of terms

First of all, a clarification of terms: what exactly is meant by digitalisation? Digitalisation affects everyone in society, but especially the economy. Here we speak of digital transformation or digital change. It refers to changes in processes, forms of work, customer interactions, products, services and complete business models. For example, during the Corona crisis, communication was moved to online platforms or companies are developing apps to offer their services there as well.

Front-runner and tail-runner in digitalisation

Looking at these examples, it is not surprising that there are large fluctuations in the state of digitalisation in Germany, both among the sectors and among the company sizes. Overall, however, an upward trend can be seen in most sectors and company types. The frontrunners in terms of sectors are the information and communications industry, followed by the automotive and mechanical engineering industries and business-related service providers. In terms of company size, companies with more than 250 employees are ahead with a digitisation index of 205.2. The value for medium-sized companies declined (125.4 to 119.4), and companies with 1 – 49 employees were able to increase their degree of digitalisation, but still only have a value of 93.9. The digitalisation index is based on 50 indicators such as the digitalisation of processes or human capital.

Ziele der digitalen Transformation

Klar ist jedoch, dass die Notwendigkeit des digitalen Wandels in den Köpfen angekommen ist und dass Unternehmen begonnen haben, an ihrer Transformation zu arbeiten. So verfügen inzwischen insgesamt 83% der Unternehmen über eine Digitalisierungsstrategie. Allerdings gibt ein Drittel der Befragten immer noch an, keine zentrale Strategie für die Digitalisierung zu haben, was sich langfristig auf die Erfolgschancen der Unternehmen auswirken kann. Hauptmotive für die Digitalisierung sind laut einer Studie der DIHK unter etwa 3500 Unternehmen vor allem die strategische Unternehmensentwicklung und Effizienzsteigerungen durch Kostensenkung (jeweils 57 Prozent). Auf Platz zwei liegt die Erhöhung der Kundenbindung (53 Prozent), gefolgt von der Flexibilisierung der Unternehmensprozesse bzw. Workflows (52 Prozent).

Goals of the digital transformation

What is clear, however, is that the need for digital transformation has entered people’s minds and that companies have begun to work on their transformation. Thus, a total of 83% of companies now have a digitalisation strategy. However, one third of respondents still say they do not have a central strategy for digitalisation, which can have an impact on companies’ chances of success in the long term. The main motives for digitalisation, according to a study of around 3,500 companies by the DIHK, are above all strategic corporate development and efficiency increases through cost reduction (57 percent each). In second place is increasing customer loyalty (53 percent), followed by making company processes or workflows more flexible (52 percent).

Main reasons for problems with digitalisation

There are many reasons why digitalisation projects fail or are not tackled at all. According to a survey by the DIHK, small and medium-sized enterprises in particular shy away from the high investment costs. In the first place, however, is the complexity that companies see in the implementation inot existing systems and processes. Of course, human capital also plays a role here. As in the case of the digitalisation index, it can be seen here again that the know-how for the conversion of processes or business models is lacking in the companies and must be purchased or created through further training measures. A study by the d.velop blog looks at other reasons for the failure of many a digitalisation project. The respondents see a major issue in the fact that digitalisation affects every company differently and a clear definition of requirements across all departments and areas of the company is difficult. A good third also stated that they have methodological implementation problems because they are not familiar with the agile way of working, which is important for change, and therefore do not succeed in the transition.

Possible solutions: Use of consultants and nearshoring

As is so often the case, it is difficult to change and make a transition on your own. Especially in the area of digitalisation and agility, it therefore makes sense to hire external consultants and thus buy in the missing know-how. With expert eyes and the necessary distance, they can achieve what internal employees can almost only fail at: a precise analysis of the current situation with a roadmap on how companies can use digitalisation for themselves and gradually adapt their processes. In training and coaching sessions, employees can learn new agile ways of working and adjust their mindset, which is necessary for this new form of collaboration. In order to avoid a cost explosion when adapting processes that require a new technological solution, outsourcing IT projects to nearshoring partners is a good alternative, as communication is guaranteed here due to a common working language and similar mentality . We offer a full service solution in this area. Do you have any questions? Contact us!

Content:

160 Days Sprint - The Lockdown as a Creative Break

Corona Digitalisierung
The Corona Virus - salutary shock for digitalisation or burning glass for societal and social inequalities? One thing is certain. In crisis situations, our values and ideals are put to the test.

A salutary shock for digitalisation or a burning glass for societal and social inequalities?

One thing is certain: in situations of crisis, our values and ideals are put to the test. Actually, it is only in situations of crisis that they become visible and gain in importance, since before they are only lip service and ideas of what we want to be as a society. Political decisions, legitimised by the containment of the pandemic, have to be implemented overnight. People and companies are permanently confronted with new procedures and instructions.

The state of emergency as default mode

In the think tank, too, the working day has changed radically. We now meet every morning at 8:45 in the daily. The cheerful, pleasant sounds of the team app have become a wake-up call to work for all of us and a fixed part of our daily routine. The daily exchange gives us support and structure in a time of volatility.

In a virtual walk & talk, we meet for small talk. What used to happen automatically and without thinking must now be institutionalised. For many, work is a big part of life. Not everyone has a family or a large circle of friends. The “good morning” in the chat is often the only signal from outside. That is why formats of this kind are only the beginning and must be constantly renewed and expanded.

My impressions after 100 days Corona

160 Days Sprint - The Lockdown as a Creative Break

Nevertheless, we used the lockdown as a creative break and completely revised our website.

We reworked the design, the content, the graphics and even the tech stack together. In 160 days. We changed our organisation from a loose working group to Scrum.

I would like to take this opportunity to thank everyone who has tirelessly designed, written and coded.

That’s why this story is a success story for me.

Conclusion

Certainly, Corona is the fuel for digitalisation. Nevertheless, we need to constantly review our actions and their impact. As the pace increases, so does the risk that some will fall by the wayside and be left behind. We need to continuously question what we can do better. How can we bring everyone along? How can humanity and warmth of heart be transported despite distance, masks and isolation?

Do you need a Blockchain?

Blockchain
Blockchain technology has the potential to profoundly change all areas of our society. As a construct of the concepts of the digital signature, proof of work or proof of stake and the consensus algorithm, it combines previously incompatible concepts:

Do you need a Blockchain?

  • Decentralisation,
  • security and
  • trust.

In order to get a better overview of the different areas of application, the categories to which most use cases can be assigned, regardless of the industry, are listed below:

Digital Identity Management: Many people have certainly come up with the idea of managing digital identities. Not least Facebook and Google, which are integrated as registration services in many online services. From the user’s point of view, this is both convenient and questionable, as it is not always obvious when which data is passed on to third parties and for what purpose. The decisive factor in this category is the purpose, namely the storage of personal data that can be validated and thus used for authentication for other services.

Market creation and digital currencies: This category refers to the creation of new markets. Usually, this is a blockchain-based market on which goods or services can be traded. All cryptocurrency applications are examples of this category. Initial Coin Offerings (ICOs) in which investor funds are collected in an initial funding phase are also examples of market development.

Origin and tokenisation: In tokenisation, a real object that represents an asset is converted into a digital asset. The value is transferred to tokens and uniquely assigned to an owner. The tracking mechanism can be used to prove the origin and ownership of an object at any time (provenance).

Meta-consensus: Meta-consensus is one of the fundamental paradigms of the blockchain, as all participants must agree on a “chain”. This use case category is about finding and reaching consensus on a specific issue without being able to manipulate the outcome of the election. Examples are parliamentary elections, referendums or the votes of shareholders or contracts between several parties.

Tracking. Tracking is about the transparent, permanent storage and traceability of information that is relevant for several organisations. A good example is use cases from supply chain management, as data on transport goods is necessary both for individual suppliers and for checking adherence to laws and guidelines (compliance).

IoT – Internet of Things: Machines that interact on the blockchain like we humans do in real life and exchange goods and services via a wallet are part of the IoT category. An example is the automatic payment of tolls or parking fees, which can be paid by the car, which has a unique ID. Smart contracts, which are executed automatically without external intervention, also belong to this category.

Intermediary trust: Due to the characteristics outlined at the beginning, the blockchain has the potential to reduce the participants in a value chain to those that are really necessary, i.e. only those that actually contribute to an increase in value. Services and goods can thus be offered much more cheaply. One example is the energy sector, where it is possible to directly connect producers and consumers thanks to the blockchain.

We don't need a Blockchain!

The use of a blockchain solution should be viewed critically if it involves the storage of large amounts of data, there are many write accesses and a real-time data set is necessary or only a few participants are involved.

Conclusion

The applications of blockchain are as diverse as our lives. Nevertheless, it is often difficult to judge when its use really makes sense. “If trust or robustness are not important, then there is nothing which a blockchain offers that can’t be done with a regular database.” Gideon Greenspan – Founder of Coin Science.

Quellen: Ulrich Gallersdörfer Masterthesis: Analysis of Use Cases of Blockchain Technology in Legal Transactions https://wwwmatthes.in.tum.de/pages/z0tgbukmqlbr/Master-s-Thesis-Ulrich-Gallersdoerfer, zuletzt geprüft am: 05.02.2020

Cathy Mulligan (April 2018) These 11 questions will help you decide if blockchain is right for your Business https://www.weforum.org/agenda/2018/04/questions-blockchain-toolkit-right-for-business, zuletzt geprüft am 05.02.2020

T. Koens & E. Poll 2018 What Blockchain Alternative Do You Need? http://tommykoens.com/wp-content/uploads/2018/09/blockchain-alternative.pdf, zuzletzt geprüft am: 05.02.2020

DHS model (~end 2017) Dylan Yaga Peter Mell Nik Roby Karen Scarfone Blockchain Technology Overview https://nvlpubs.nist.gov/nistpubs/ir/2018/NIST.IR.8202.pdf , zuletzt geprüft am: 05.02.2020