敏捷环境中的业务分析师

In this episode, author Lynda Girvan discusses how BAs can succeed in Agile environments by applying a lean and adaptive approach.

After listening to this episode, you’ll understand:

  • How to make your BA process more Agile
  • The three ways of thinking that lead to success in Agile
  • The difference between real Agile and a series of small waterfalls

音频下载:http://traffic.libsyn.com/masteringbusinessanalysis/MBA124.mp3

Do we need Business Analysts in Agile?  It depends.

The skill of analysis is certainly needed in Agile product development.  Either the people within the team need to develop their business analysis skills or the Business Analyst needs to become more “T” shaped.

摘自《BABOK3线上公开课》讲义

Outside of product development, specialized Business Analysts can contribute even in Agile environments.

The Agile Business Analyst

Business Analysts in an agile environment do many of the same things that they do in a traditional waterfall environment, just with a different mindset.

You still create models, but do just enough just in time instead of creating everything upfront.  You still document information, but do so with a service thinking approach.

The skills that you’ve developed as a traditional BA are still valuable in Agile if you apply an Agile mindset.  The Agile mindset includes Lean thinking, service thinking, and systems thinking.

Lean Thinking

Lean is about reducing waste to deliver value.  There can be a lot of waste in traditional business analysis activities and Lean thinking seeks to reduce that waste.

One form of waste is overproduction.  When we create monolithic requirements documents (many features of which are never used), that’s a form of overproduction.

Over processing is another form of waste.  This is seen when we provide more detail that is needed.

Partially done work (e.g., incomplete models or those that don’t provide value) is another form of waste because this becomes inventory that we now need to store and maintain.

Service Thinking

Service thinking is the concept that we can’t deliver value.  We can only propose value.  Once we deliver something, we can get feedback from the customer to determine if it was of value to them.

If we understand that concept, we can get into value co-creation.   This is when we understand who the customer is and understand what their needs are and what’s valuable to them.

Value co-creation involves tight collaboration between the team and customers.

Systems Thinking

Systems thinking is about being able to see all of the interrelated parts.  These parts need to work together.

This approach helps you to avoid silos.  Systems thinking also helps you to understand how changes to one part of the system affect other parts.

Agile teams often focus on one product and fail to see the wider implications across the organization.

All of these concepts lead to one thing: Shortening the loop between concept and delivery.  Requirements are just a means to an end.  We need to figure out how to analyze just enough to deliver something and get feedback so we can learn and adapt.

Listen to the full episode for more on how to prioritize work, the difference between Agile and a series of small waterfall efforts, how to make your requirements more agile, and how to succeed in an Agile environment.

Start being Agile

Apply Agile as a mindset.  Think about how you can apply Lean thinking, service thinking, and systems thinking to your work.  Forget about frameworks and start being agile.

摘自《BABOK3线上公开课》讲义

转:https://masteringbusinessanalysis.com/mba124-business-analyst-agile-environment/

更多文章

星球资料

业务分析卓越中心.pdf

竞争激烈的二十一世纪商业环境在每一个角落都会带来挑战。公共和营利组织都必须具有灵活性和适应性,以保持竞争力。正是通过成功的项目,组织才能管理变革,提供新的业务解决方案,并最终实现其战略。然而,我们仍在努力管理复杂的业务变革计划。全球各地的企业都在努力提高其业务分析能力,以推动战略目标的变化,投资于最有价值的项目,这些项目以最低的成本和风险实现最高价值,并以最佳方式执行项目,以尽快从新解决方案中获得业务利益。本文探讨了我们令人失望的项目绩效记录、21世纪项目的性质、将业务分析作为组织转型的关键组成部分的必要性,以及卓越业务分析中心在组织中的作用。

阅读更多»
业务架构学习群资料

D5.1 业务架构-将组织转变为敏捷企业

组织很难实现业务战略,特别是当这些战略跨越业务单元、产品和外部业务领域边界时。问题是为什么?研究表明,很多时候,没有实现业务战略并不是因为这些战略考虑不周。相反,这些失败往往是因为这些战略的范围和影响是模糊或未知的。当战略指令的影响超出规划团队的视线范围,需要跨业务协调和协作时,这个问题会被放大。换言之,无法实现业务战略往往是由于在错误的地方做了正确的事情,在正确的地方做了错误的事情,把好的想法变成失败的项目,失去了机会,浪费了投资。

阅读更多»