\n– Vaiko Hansson<\/strong><\/p>\n
Since the Agile Manifesto<\/a> was first published in 2001, companies have sought to become agile, and Scrum<\/a> has become the most applied framework for agile software development<\/a>. Over a thousand books have been published about Scrum, leading many to believe it\u2019s the fast track to agile.<\/p>\n But Scrum is no silver bullet. Focusing too much on the processes can lead developers to create solutions to problems that never existed.<\/p>\n When we build something, we always believe that we\u2019re building the right solution to our problem. But environments where problems exist are always changing, and problems themselves are usually complex. Have we truly understood them? The only way to know is to constantly validate and update our understanding of the problem at hand.<\/p>\n To be certain of a solution, we need to take the solution to the end users as fast as possible. And here\u2019s where agile comes in. Agile is a mindset and collection of practices to help you build something usable extremely fast so that you can test it in the real world. Only then the feedback loop is closed properly and some validated learning can happen.<\/p>\n At its worst, too much Scrum can cause a minimum viable product to be drawn out years, when it should be brought to the market in weeks or months.<\/p>\n One organization I was a part of decided to force Scrum processes on everyone throughout the value chain. This meant simultaneous updates of everything from the core systems to the organization’s brand. It took a massive amount of time and was of no actual value to the users. Millions of euros were spent only to end up in a train wreck when the interests of investors collided with the reality of the product release (or the absence a product release). Key people hadn\u2019t understood the true nature of the word Agile – fast. They started with the process, not the mindset.<\/p>\n A second company wanted to build a file sharing platform and used Scrum to construct it with the ultimate security features \u2013 something even Dr. Evil could not breach. The company was so sure they knew the problem inside out that they decided that little to no interaction with actual users was necessary. It took a year before it was tested on the end users, and only then was it discovered the customer\u2019s problem was communication, not security. The team had a solution for a problem that didn\u2019t really exist, and one entire year went down the drain.<\/p>\n Common misconception about Scrum is that you need to start developing as fast as possible and build it in small iterations. Instead we need to start offering value as soon as possible.<\/p>\n Say you\u2019re building a car and getting fast from point A to point B is the goal. Scrum will make it iterative and spread development into small pieces. You might make the body, then add the chassis, wheels, and motor. But Scrum can lead you to the body alone, which by itself can\u2019t get you to B.<\/p>\n What is really needed is to iteratively carry people from A to B. Don\u2019t iterate the building. Instead, iterate the problem solving. In this example each iteration should carry humans from A to B a bit faster. With each iteration you\u2019ll learn something new. Maybe you don\u2019t need an engine \u2013 perhaps a chassis on wheels pulled by people will suffice. Or maybe you\u2019ll learn people don\u2019t even want to get to B.<\/p>\n Scrum advocates building as fast as possible in an iterative fashion. A popular criticism is that with Scrum you don\u2019t know what you\u2019re building. But this is simply a misunderstanding of agile. Agile doesn\u2019t say \u201cDon\u2019t do pre-analysis\u201d or \u201cnever have a product vision.\u201d In fact, those statements are what agile is all about.<\/p>\n Don\u2019t iterate how to build a car. If you\u2019re doing that you\u2019ve already failed on the business side. Iterate the solution of moving from A to B. The assumption that the problem is going from A to B, and that the solution is a car \u2013 all this gets crammed into Scrum.<\/p>\n What can a business leader do to avoid these problems? A good start is reading The Lean Startup<\/a> by Eric Ries, who makes a great argument for doing everything to understand the real problem. You can also bring in consultants with proven track records of building products the agile way.<\/p>\n But perhaps the best way to learn agile is to create a startup inside your own company. Together with your clients, choose a small problem, separate it from your normal processes, and solve it with an agile approach. When you do it, be sure to involve people or partners from outside who have actually experienced building things in an agile way. After all, if you want to innovate, you need to do new and innovative things.<\/p>\n If you try to solve the problem with big systems already in place, there\u2019ll be the constant worry about how it affects usability and how people perceive your brand and service. Applying agile principles in tiny modules is easier than doing it across an entire organization, and you can later use what you\u2019ve learned to introduce agile practices to your larger organization.<\/p>\n Whatever you do, get the mindset right, and then let altering the processes follow.<\/p>\n Moving towards agile, and not merely using Scrum, has many benefits.<\/p>\n Proekspert<\/a> was once an organization where workdays were packed with Dilbert moments. Frustration was created by trying to impose agile in a production-based culture. It made employees feel schizophrenic. The solution was to change the organization structure and cut middle management out of the picture. Now, Proekspert has gone bossless, and it\u2019s able to focus on its core mission: improving people’s lives by making machines and devices smart.<\/p>\n My experience working with Proekspert over two years has been a miraculous journey. Their bossless culture without mindless hierarchy has allowed me to focus on what they actually need. Thanks to that, our partnership has evolved in ways I could never have planned, and together we strive to change the world every day.<\/p>\n If we can see those around us and focus on what they need, we actually create value while in the service of others. And creating value is what agile is all about.<\/p>\n Let us focus on serving our customers and their customers who will use what we build. Did they want to get from A to B? Are they now at B? And are they happy?<\/p>\n Vaiko Hansson is a consultant to Proekspert helping to develop the Agile mindset in all fields of business.<\/p>\n If you would like to discuss it further, contact us<\/a> or join our newsletter<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" Agile Coach: Scrum is Not the Messiah Scrum too often provides answers to the wrong question, says our agile coach Vaiko Hansson. If you want to be agile, set aside Scrum for a moment and consider the bigger picture. – Vaiko Hansson Since the Agile Manifesto was first published in 2001, companies have sought to become agile, and Scrum has become the most applied framework for agile software development. Over a thousand books have been published about Scrum, leading many to believe it\u2019s the fast track to agile. But Scrum is no silver bullet. Focusing too much on the processes can lead developers to create solutions to problems that never existed. Understanding agile When we build something, we always believe that we\u2019re building the right solution to our problem. But environments where problems exist are always changing, and problems themselves are usually complex. Have we truly understood them? The only way to know is to constantly validate and update our understanding of the problem at hand. To be certain of a solution, we need to take the solution to the end users as fast as possible. And here\u2019s where agile comes in. Agile is a mindset and collection of practices<\/p>\n","protected":false},"author":10,"featured_media":201,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[49],"tags":[],"class_list":["post-21","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-organizational-change"],"acf":[],"_links":{"self":[{"href":"https:\/\/clients.triloogia.ee\/proekspert\/wp-new\/wp-json\/wp\/v2\/posts\/21","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/clients.triloogia.ee\/proekspert\/wp-new\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/clients.triloogia.ee\/proekspert\/wp-new\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/clients.triloogia.ee\/proekspert\/wp-new\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/clients.triloogia.ee\/proekspert\/wp-new\/wp-json\/wp\/v2\/comments?post=21"}],"version-history":[{"count":7,"href":"https:\/\/clients.triloogia.ee\/proekspert\/wp-new\/wp-json\/wp\/v2\/posts\/21\/revisions"}],"predecessor-version":[{"id":2866,"href":"https:\/\/clients.triloogia.ee\/proekspert\/wp-new\/wp-json\/wp\/v2\/posts\/21\/revisions\/2866"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/clients.triloogia.ee\/proekspert\/wp-new\/wp-json\/wp\/v2\/media\/201"}],"wp:attachment":[{"href":"https:\/\/clients.triloogia.ee\/proekspert\/wp-new\/wp-json\/wp\/v2\/media?parent=21"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/clients.triloogia.ee\/proekspert\/wp-new\/wp-json\/wp\/v2\/categories?post=21"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/clients.triloogia.ee\/proekspert\/wp-new\/wp-json\/wp\/v2\/tags?post=21"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"\"](\"https:\/\/clients.triloogia.ee\/proekspert\/wp-new\/wp-content\/uploads\/2017\/10\/problem-solution.jpg\")
<\/p>\nUnderstanding agile<\/h3>\n
Months not years<\/h3>\n
![\"\"](\"https:\/\/clients.triloogia.ee\/proekspert\/wp-new\/wp-content\/uploads\/2017\/09\/months-not-years.jpg\")
<\/p>\nThe Scrum fallacy<\/h3>\n
So what\u2019s the solution?<\/h3>\n
![\"\"](\"https:\/\/clients.triloogia.ee\/proekspert\/wp-new\/wp-content\/uploads\/2017\/09\/lean-startup.png\")
<\/p>\nServe yourself by serving others<\/h3>\n
Contact Us<\/h3>\n