News-Feeds:
The truth about TYPO3 and Agile
During the last two years I participated T3CON the TYPO3 conference in Gemany two times. It was really great events. I met great people inspired by the TYPO3 project and TYPO3 community. I talked to many people and I was wondering how many of them were interested in Agile (SCRUM, Kanban) methodologies. Most of people I met knew what Agile is (at least heard words like SCRUM or Kanban). Nearly half of them told me that they would like to use Agile in their work or going to look at it in future. Nearly 10% of people I talked said that their companies use some of Agile artifacts (e.g. SCRUM board, daily standup meetings, sprints, etc.). And only few people told me that their company used SCRUM or Kanban as a main development methodology.
I clearly understood that everything described above is only my own impression. So I decided to check how much truth in my impression is. I was wondering how many TYPO3 agencies use Agile in their development process. I decided to measure this by number of vacancies which require Agile knowledge. I took three job web sites and investigated number of vacancies on them with the keyword TYPO3. Also I measured number of vacancies that had both keywords TYPO3 and SCRUM, TYPO3 and Kanban, TYPO3 and Agile. Ofcause numbers can be a bit different from day to day, but the whole picture is the same. You can see results of my research in table below.
Job site | TYPO3 | TYPO3 SCRUM | TYPO3 Kanban | TYPO3 Agile | Share, % |
21 | 1 | 0 | 2 | 4.7/0/9.5 | |
www.linkedin.com (in Gemany) | 60 | 3 | 0 | 1 | 5/0/0.17 |
104 | 5 | 2 | 2 | 4.8/1.9/1.9 | |
Avg. share %: | 4.83% | 0.63% | 3.8% |
From this table I made conclusion that less than 10% of companies want their employee know Agile. That means that other 90% of companies don’t use Agile (even partly) as their development methodology. So my previous impression from T3CONs that only 10% of TYPO3 agencies use Agile (at least partly) was more or less true.
I cannot say that it was a pleasant surprise for me because during the last years more and more software development companies use Agile. Now in software development Agile is a real trend. So I decided to investigate this issue.
In most cases when people are faced with modern technology or trend, before they use it in production they need to learn more about it. So to start using Agile in production people require more information about Agile. I decided to investigate the informational background on Agile in TYPO3 community. I used search engines and measured number of results (especially how many pages were found for appropriate search request). Please find results of my researches in table below. For search I used same keywords as previously.
Search engine | TYPO3 | TYPO3 SCRUM | TYPO3 Kanban | TYPO3 Agile | Share, % |
1.2/0.2/1.7 | |||||
0.3/0.1/0.4 | |||||
2.6/0.9/2.7 | |||||
Avg. share %: | 1.4% | 0.4% | 1.6% |
According to this statistics less than 3.5% of information in TYPO3 information flow is related to Agile (SCRUM, Kanban) methods. To show you how dramatic is the situation with Agile information in TYPO3 community I compared numbers from the last table with the same results for other web-development tools. In table below you can find statistics for TYPO3 and three other web-development tools: Drupal, Magento and .Net. This table contains only search results from google.de since google has more accurate search results (more close to average results number among other search engines, see previouse table).
TOTAL results | With SCRUM | With Kanban | With Agile | SCRUM Share (%) | Kanban Share (%) | Agile Share (%) | |
.Net | 244000K | 7470K | 649K | 49100K | 3.06 | 0.27 | 20.12 |
Drupal | 131000K | 2140K | 165K | 12600K | 1.63 | 0.13 | 9.62 |
Magento | 47900K | 806K | 1370K | 2480K | 1.68 | 2.86 | 5.18 |
TYPO3 | 12400K | 153K | 26.3K | 216K | 1.23 | 0.21 | 1.74 |
According to this table among four web-development tools I checked the winner is .Net. This means that .Net community has much more information about Agile methods in Internet than others. Unfortunately TYPO3 community has the least information flow about Agile in Internet. This is unpleasant news. On the other hand always there is place for improvements.
Conclusion: TYPO3 community needs more information and education about Agile methods. T3SCRUM is a free educational project about Agile methods and especially about SCRUM and Kanban. As a part of T3SCRUM project during the T3CON12 in Stuttgart, we provided a one day SCRUM training. In future we are planning more online and live activities e.g. webinars, trainings, blogging and others.
At the moment we are planning a free webinar goo.gl/7sO6V and we need your support. Please help us to make this webinar interesting for community. How can you help?
Go to our facebook page and like us: http://www.facebook.com/T3SCRUM
Go to twitter and follow us: @t3scrum (use hashtag #T3SCRUM for your tweets about us)
Leave your comments and propositions on fb: goo.gl/7sO6V.
Share this post among your friends who might be interested in Agile development and education (e.g. your manager :-)
comments
January 5, 2013
16:07
i had exactly the same thoughts like Tolleiv. Your method to get the data is wrong.
Anyway i like the project and will attend your webinar.
Regards,
Joscha
January 5, 2013
22:32
cheers
sacha
Buzz is the official blog resource of the TYPO3 project. You can be part of Buzz too. If you want to blog about the achievements of your team or your personal involvement please check out our HELP section.
thanks for the initiative - you might be right, but please don't use these numbers to draw any conclusions from it the way you did it.
Looking at the "job websites" examples. When looking for POs or Scrum Masters I don't necessarily see why some agency should search from specifically for TYPO3 POs / SCMs. For developers I'm pretty sure that "Agile" isn't even needed as prerequisite for a job because this is something the developers pick up quickly.
In order to be able to compare the "agility share" for "web tools" you'd have to assume that the "normal" content related to the different tools is equal in it's distribution. But that can't be the case when you compare such different tools.
Imho both measures are somewhat polluted and aren't worth to be used as metric. Why is that important enough for a comment? You initiative might be a success, but with such a weak metrics you won't be able to prove it and loose motivation in the worst case.
My suggestion would be to make a proper survey amongst the TA members and check how many of them applied *Agile/Scrum/Kanban* already. Once you have this, you can repeat it on a regular basis and check whether numbers improve or not.
Cheers,
Tolleiv