• Five_reasons
  • Cal2_20220108
  • Hardware-agile-practice
  • 2020-scrum-guide-banner
  • Clp_20220108
  • A-CSM 国际Scrum联盟认证 ScrumMaster
  • 敏捷思维 领导力 企业培训 国际Scrum联盟认证
  • 汽车行业敏捷开发课程
  • CSM A-CSM Scrum敏捷实践
  • 敏捷领导力认证培训  CAL认证培训 CST CSP
  • 30天软件开发 敏捷规模化实践 Scrum精髓 敏捷文化
  • Scrum敏捷培训 Scrum敏捷企业内训
  • Scrum敏捷软件开发管理 企业内训 Scrum转型
Faster, higher, stronger with Agile and Lean
图片无法正常显示?请点击在浏览器中 查看

全国统一客服热线 400 920 0024
Faster, higher, stronger with Agile and Lean
Faster, more efficient and better; there is almost no end to the promises attributed to Agile and Lean product development. Dispite all the promises many teams and organisations are not able to gain the possible benefits.
Those of our customers who are most successful in their implementation of Agile or Lean are able to give a clear answer to the question ”Why do you want to implement Agile or Lean?”. Among the answers you hear ”we want to increase our productivity”, ”we want to increase our product quality”, ”we want to decrease our leadtimes for development” and ”we want to increase our Return on Investment”.

To find a way to reach the defined goals of an implementation of Agile or Lean it is good advice to base the decision on the specific circumstances the company are in right now. The decision need to be based on what kind of reality we are facing. Is it simple, complicated, complex or even chaotic? To apply Agile with it’s values and principles in a simple reality may very well be like sawing with a hammer. Agile is more suited for a complex reality where we are not able, before we start walking, to determine exactly which steps will lead us to success. Instead we need to inspect where we are, how long the rest of the journey is and what is left to be accomplished before we adapt our next step. To inspect and adapt is one of the cornerstones of Scrum and is also a frequent practice in Agile.

Are there any good or bad answers to the question ”Why do you want to implement Agile or Lean”? Yes, in my opinion you can hear both good and bad answers. The answers listed above are among those I consider good. Other answers I consider good, or legitimate, are “We want to increase our ability to deal with changed priorities.”, “We want to increase the transparency and visibility of product development progress.” and “We want to create good conditions for successful team work”. The list is even longer. I will stop here and turn to the answers that I consider to be bad or illegitimate. The answers that send chills down my spine are “Someone in our organization told us to.” and “Company X has been successful after implementing Agile.”

My first advice to companies considering Agile or Lean is: Decide why and decide what goals you want to accomplish by implementing Agile or Lean. After you have analyzed  your situation, identified your answer and possibly decided why you believe Agile or Lean can help you meet your goals, then it’s time to talk business and we can engage in fruitful discussions on how you can do a successful implementation.

To me understanding the underlying principles is the biggest and most clear success factor when implementing Agile or Lean. Let me do a  brief walk through of some important principles and argue how to benefit from applying them.

The first principle listed in the Agile Manifesto is: “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.” This principle tells me that we as suppliers and developers of the product need support from our customer (to me ”customer” in this context is a summary of all possible stakeholders including but not limited to client and end users) primarily within two areas; to choose in what order we should implement the requirements, prioritize, and to receive feedback on what we have developed and delivered to the customer. What we deliver do not necessarily need to be released to end users. What’s important to me is that we demonstrate an increment that is done and that is possible to give feedback on. That way it is possible to use the feedback early during development rather than late. We also get the opportunity to change direction if we are drifting off our main course.

Another interesting principle is: “Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.”

To me, this principle is about me wanting to do all that’s in my power to create the right conditions for my competent coworkers to succeed. It is also about a belief that the people most suited to develop our product are best suited to identify and explain the conditions they need to be fulfilled in order to do a good job. I also believe that the people most suited to develop our product are best suited to make daily decisions on how to develop the product and chose direction for development on a daily basis within the current iteration.

When considering implementing Lean it is a good idea to reflect upon the principle ”Deliver fast”. At first it may be totally obvious that product delivery should be fast. When we take a closer look it shows that many times the principle is not fulfilled. Recently a good friend of mine told me how important it was in his organization to be ready to act and respond quickly to requests. It was obvious for everyone to deliver answers fast when a request came up. What often happened, though, was that requests did not turn up one at a time. In addition to many fast deliveries, decisions on what request was most important to finish could change on a daily basis. The result was sometimes definitely not in accordance with deliver fast. In my opinion the principle ”deliver fast” needs to be elaborated upon. It becomes easier to grasp and implement if we add that all activities, big as well as small, should be addressed in a way that they can be finished as soon as possible. By putting focus on finishing activities we will increase the probability to deliver fast. When limiting the amount of activities or request we start it is possible to deliver fast. Some call this to do one thing at a time. Taken to its extrem that is exactly what it is about. By doing one thing at the time we can focus heavily on finishing it. To limit work to only one piece can be to take things to the absurd. Limiting the amount of work in process is often a wise decision.

With my reasoning on some of the principles behind Agile and Lean I want to give advice on possible steps forward and also point out the fact that contributions by many individuals and parts of an organization are needed in order to satisfy the these principles. In order to create successful implementations of Agile and Lean we need to have an understanding of how the implementation can help us to reach our overall goals. That is not always enough. We need to decide upon which road to take, we need to make prioritization’s, we need feedback and we need to collaborate with many parts within our organization. A successful implementation of Agile or Lean requires actions by developers, testers, architects, business analysts, stakeholders and definitely by managers.

A successful implementation requires everyone involved to follow up, continuously make decisions and to understand the underlying principles. If we don’t have a full understanding it is easy to get trapped and perhaps say as Groucho Marx: “Those are my principles, and if you don’t like them…well I have others.”

Author: Arne Ahlander
Article source: http://aqqurite.se/ 
        About the author  Arne Ahlander
World-famous CST, Member of Scrum Alliance Trainer Approval Community, First-class Agile Product Management Master and Expert

Arne Åhlander is a Senior Consultant using Agile and Lean methodologies to improve management and product development for several larger software organizations.
Arne has experience from the software industry since 1994, to a great part in the area of product management where he have held several senior positions. Arne has managed Scrum projects, helped customers start Scrum initatives. Arne is a CSM, CSPO, CSP and he became a Certified Scrum Trainer (CST) in November, 2008.

Mr Åhlander is a TBR (Training From The BACK Of The Room) Certified Trainer.

Arne is based in Lund, Sweden, employed by Aqqurite and an active member of the SW Business Improvement efforts in Scandinavia. He holds a Master of Science in Electrical Engineering at Lund University, Sweden. Special interests of Arne, are:

◈  The Product Owner role
◈ Business Value calculations
◈ Prioritization of projects based on Business Value
◈ Extending Scrum within organizations
◈ Scaling of Scrum

English delivered CSM and CSPO courses are available this March in Shanghai and Shenzhen by Arne Ahlander. Till the year of 2019, Arne Ahlander already has more than 1,000 students in China, which makes him being the NO.1 foreign CST who owns the most students in China.
3月15-16日  上海
Arne Ahlander安儒宣(国际Scrum认证大师)

3月17-18日  上海
Arne Ahlander安儒宣(国际Scrum认证大师)

3月20-21日  深圳
Arne Ahlander安儒宣(国际Scrum认证大师)
8月21-22日  北京
Kiro Harada原田骑郎
(Scrum Patterns专家)
♦ Scrum Alliance颁发的ScrumMaster/ Scrum Product Owner认证证书,成为一名认证的ScrumMaster/ Scrum Product Owner
♦ Scrum Alliance的两年会员会费及会员资格
♦ ShineScrum捷行终身荣誉会员资格,可免费参加ShineScrum捷行主办的各种活动
♦ 一副价值30元的估算扑克
♦ 一份CSM/ CSPO课程纸质版中英文讲义
♦ Scrum实施模板及大量参考资料推荐
♦ 美国项目管理协会(PMI)学分 16PDUs