Scrum Alliance联盟的认证是国际最权威的Scrum与敏捷认证,分为基础级、专家级和导师级。很多同学在获得基础级的CSM/CSPO/CSD认证后,想要继续深造,但觉得下一级CSP认证很难获得申请所需的SEU(Scrum Educational SEU),或者不知道该如何申请,现在就为大家解读最新的申请攻略。



9 Reasons Why I Decided to Become a CSP


  • 拥有CSM/CSPO/CSD认证之一,且未过期
  • 过去5年内,至少有36个月的时间在组织内成功地应用Scrum
  • 在过去3年内积累70个SEU学分。已经获得的课程认证可以提供了一些学分哦。CSM (16 SEUs), CSD (24 SEUs), CSPO (16 SEUs)


一次性申请费用(申请时支付,不退还)为$100, 认证费(通过评审之后支付)为$150。

你可以在Scrum Alliance网站上找到自己的dashboard页面,点击”Apply for CSP Certification” (在”Actions”按钮下)。填写你的36个月的敏捷经验,以及所扮演的”Scrum Role”。还要提供个人简介和联系方式。



在70个SEU中,分几个类别,几乎每个类别有上限(防止偏科)。你可以在Scrum Alliance网站上找到自己的dashboard页面,点击”Add new SEU” (在”Actions”按钮下)。

  1. A类(不超过45个)。参加各种ScrumAlliance支持的社区大会,例如Scrum Gathering大会。每个小时算作一个SEU。
  2. B类(没有上限哦,至少14个)。参加Scrum Alliance授权的课程,例如CSM等认证课,或者像上海优普丰这种REP合作伙伴提供的非认证课(如进阶敏捷教练课程),还有就是接受CTC认证教练的Coaching辅导也可以哦。
  3. C类(不超过15个)。参加非Scrum Alliance机构举办的敏捷相关课程或活动。
  4. D类(不超过15个)。参与敏捷社区志愿者服务。
  5. E类(不超过15个)。独立学习,如准备一个Scrum相关的演讲,写文章,看视频,读书等。每个小时算作一个SEU。
  6. F类(不超过15个)。其他集体学习,如共同培训(co-train),参与网络课程等。每个小时算作一个SEU。

参见Earn SEUs for your CSP



参见 Renew your CSP

Tips to Certified Team Coach application

This series includes three posts:

  1. How Bright Career Path of ScrumMaster and Agile Coach?
  2. My Agile Coach Journey
  3. Tips to Certified Team Coach application

Tips for applying CTC

The previous two articles shown how bright career it is to be an agile coach, and what I have learned from my jouney of agile coach. If you have the aspiration to achieve the highest level Scrum certification, just follow up this article.
After the experiment of the certification last year, CTC has already opened for public application. As I learnt from the forum, there are many experts in Southeast Asia are applying for this certification, but quite few from China. Hurry up guys, I trust everyone of you, because I believe that in China there are much more professional!


继续阅读 More

My Agile Coach Journey

This series includes three posts:

  1. How Bright Career Path of ScrumMaster and Agile Coach?
  2. My Agile Coach Journey
  3. Tips to Certified Team Coach application

How did I grow up to an agile coach

Beginner to Agile

I joined Nokia Siemens Networks in 2007 when Agile had been promoting in the whold 3G Platform product line. In that period, there was few company dare to do large scale agile promotion globally. I obtained Certified Scrum Master(CSM) certification in 2008. During my career in Nokia Siemens Networks, I have been working in various roles such as Senior Software Specialist, Line Manager, Quality Manager, Project Manager, Scrum Master and Agile Coach, and had luckily worked with a lot experts in Agile. It is notexaggerate to say that Nokia Siemens Networks is like the Whampoa Military Academy of Agile in China. As per myself, I have learned and improve a lot as well in management skills, empowerment, lean concept and system thinking. In technical engineering practice, I had fully understood and adopted the concept of Continuous Integration, which is one of the useful practices in eXtreme Programming(XP). Automation Test and Refactoring was applied in my daily work as I awared the importance of Agile of Engineering Practice. The later LeSS (Large-Scale Scrum) Framework is basically originated and summarized from Nokia Siemens Networks’s experience on Organization level Agile.

继续阅读 More

How Bright Career Path of ScrumMaster and Agile Coach?

This series includes three posts:

  1. How Bright Career Path of ScrumMaster and Agile Coach?
  2. My Agile Coach Journey
  3. Tips to Certified Team Coach application

Don’t worried about the carrer development of agile coach

Agile Coach is a new role, there are some people playing that role in all the company transforming to agile but still staying on their current position. So it is inevitable to produce concerns and doubts.

Some people may doubt: The company ask me do play as agile coach or ScrumMaster, what 's the prospect and How can I develop my career?

继续阅读 More


保持简单、追求简单,我想这就是编码之中的禅,一种回归本真的境界。这种禅意在 Python 的设计哲学中体现的淋漓尽致,在 Python 解释器中输入“import this”,便会出现经典的 Python 之禅。

Beautiful is better than ugly.

Explicit is better than implicit.

Simple is better than complex.

Complex is better than complicated.

Flat is better than nested.

Sparse is better than dense.

Readability counts.

Special cases aren’t special enough to break the rules. Although practicality beats purity.

Errors should never pass silently. Unless explicitly silenced.

In the face of ambiguity, refuse the temptation to guess.

There should be one– and preferably only one –obvious way to do it.

Although that way way not be obvious at first unless you’re Dutch.

Now is better than never. Although never is often better than right now.

If the implementation is hard to explain, it’s a bad idea.

If the implementation is easy to explain, it may be a good idea.

Namespaces are one honking great idea – let’s do more of those!