<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Achiel Volckaert on Medium]]></title>
        <description><![CDATA[Stories by Achiel Volckaert on Medium]]></description>
        <link>https://medium.com/@achiel.volckaert?source=rss-a30cc002c772------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*OPvfDfCVKFjN5P1gogvixg.jpeg</url>
            <title>Stories by Achiel Volckaert on Medium</title>
            <link>https://medium.com/@achiel.volckaert?source=rss-a30cc002c772------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 14:35:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@achiel.volckaert/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Finding the right Scrum toolkit]]></title>
            <link>https://medium.com/wegroup/scrumtools-6e10b7577c83?source=rss-a30cc002c772------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e10b7577c83</guid>
            <category><![CDATA[tools]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[team]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Achiel Volckaert]]></dc:creator>
            <pubDate>Mon, 06 May 2019 15:44:08 GMT</pubDate>
            <atom:updated>2019-05-07T14:50:50.175Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wuVFOGCPtCs5qJ6NQ4f1Hw.png" /></figure><p>At WeGroup, we are scrum-enthusiasts and eager to start exploring the possibilities of the framework. Scrum is an agile process that allows us to focus on delivering the business value in the shortest time. It rapidly and repeatedly inspects actual working software. It emphasizes accountability, teamwork, and iterative progress toward a well-defined goal. However, in order to do so, we need to find the right toolkit that suits our needs.</p><p>The Scrum Framework usually deals with the fact that the requirements are likely to change or most of the time not known at the start of the project.</p><p>For us to be able to work easily with scrum, the chosen toolkit needs to meet some requirements:</p><ul><li>A mobile application, so the progress of the sprints can be checked wherever you are.</li><li>A list view of tasks is also a necessity, so that one quickly has an overview of all tasks.</li><li>Next to the list view, there needs to be some form of metrics, so the performance can be tracked and deadlines can be predicted.</li><li>We also want to group users in teams, so their individual burn rate and user stories can be assigned.</li><li>Lastly, it needs to be able to integrate with some of our used tools like Bitbucket.</li></ul><h3>Jira</h3><p>For our use, Jira did not meet all requirements. It had no calendar for a global overview, and there was no function to generate a task list for each user. Although very complete in configuration, it is quite hectic and not that user friendly.</p><h3>Scrumwise</h3><p>For us, Scrumwise feels quite complicated in comparison with other platforms. It also lacks a calendar, and it only integrates with GitHub, which we don’t use.</p><h3>Axosoft</h3><p>Axosoft checks almost all of our requirements, but it lacks the app and calendar functionality. It also seems cluttered and quite busy, but it’s a slight improvement on Scrumwise.</p><h3>Clickup</h3><p>Clickup seems to meet all of our requirements, and it feels pretty good and intuitive while using it. The front-end team seems to love the design. Clickup also is one of the cheaper ones from this list, at only 5$ per user per month.</p><h3>Zenkit</h3><p>Up until now, we were using Zenkit for task handling. Although it has most of the requirements we demand, it lacks metrics, burndown and gant charts. Because of this, we are not able to track the performance of the team (which is kind off the whole reason this blog post came to be). The user interface and feel of the platform is amazing though.</p><h3>Aputime</h3><p>Aputime seems to be lacking most of requirements, as it has no app, calendar and functionality to create teams. Also, the integrations are a bit weak, where only Slack support is provided.</p><h3>Monday</h3><p>Monday seems like quite a nice platform. It does not have a calendar built-in, but covers that field by providing integration with Google calendar. The biggest issue is the lack of team creation.</p><h3>Wrike</h3><p>Wrike checks all the boxes from our requirements list, just like Clickup, and feels good to use. However, this amazing functionality comes at a price, at 5x that of Clickup to be precise.</p><h3>Asana</h3><p>Asana is another platform that checks all the boxes for us. In use, it looks great, but it does not feel good in usage. The issue is also in the pricing, which comes at almost 4x the price of a Clickup license.</p><h3>Taskworld</h3><p>The last one we compared is Taskworld. From our requirements list, it lacks the team functionality. It is possible to assign yourself to a department, but not to link a task to a department.</p><p>In conclusion, from the ten scrum toolkits we compared, only three candidates are left: Asana, Wrike and Clickup. Since the feeling of Asana wasn’t that great, and Wrike is quite expensive, we went along with giving Clickup a try!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/516/1*TAWutqCnK4CdwoegPIqY6w.png" /><figcaption>Table comparison of compared features of the scrum toolkits</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e10b7577c83" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wegroup/scrumtools-6e10b7577c83">Finding the right Scrum toolkit</a> was originally published in <a href="https://medium.com/wegroup">WeGroup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chatbots - A comparison]]></title>
            <link>https://medium.com/wegroup/chatbots-a-comparison-d70a2392a8f2?source=rss-a30cc002c772------2</link>
            <guid isPermaLink="false">https://medium.com/p/d70a2392a8f2</guid>
            <category><![CDATA[support]]></category>
            <category><![CDATA[bots]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[chatbots]]></category>
            <dc:creator><![CDATA[Achiel Volckaert]]></dc:creator>
            <pubDate>Wed, 27 Feb 2019 16:14:46 GMT</pubDate>
            <atom:updated>2019-04-02T08:11:37.790Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nb3rrMMVk5T6TgM3wwh7FA.png" /></figure><h4>Chatbots are programs that can handle an intelligent conversation. They should be able to aid people by understanding the user’s input. On our journey to find the best platform for our needs, we compared multiple chatbot platforms and services. Our main goal is to create a personalized assistant that can help customers with their general questions.</h4><h3>Rasa</h3><p>Rasa is an open-source chatbot system. Development started in 2017 by two Germans in Berlin. The part that makes Rasa unique is that it is open-source. By hosting your own chatbot, you’re far more flexible and you are in full control of your data.</p><p><strong>Rasa consists of two major components among which </strong><a href="https://rasa.com/docs/nlu/"><strong>Rasa NLU</strong></a><strong> and </strong><a href="https://rasa.com/docs/core/"><strong>Rasa Core</strong></a><strong>.</strong></p><p>NLU is the <em>Natural Language Understanding</em>, this part predicts the <em>intent </em>of the user’s input and the entity as well. Suppose the user says: “Who is WeGroup?”. The intent is <em>companyinfo</em> and the entity is <em>WeGroup</em>.</p><p>The job of Rasa Core is to take the output of Rasa NLU and respond with an action or an appropriate answer.</p><blockquote>more: <a href="https://rasa.com/">Rasa</a></blockquote><h3>Dialogflow</h3><p>Dialogflow is a conversational chatbot from Google, previously called api.ai. Dialogflow has great support for multiple languages or dialects (30+) and programming languages such as Node.js, Python, Java, … This makes it easier to start using it. Next, to the standard setup entity and intent it has a (beta)feature ‘Knowledge’ where you can submit articles and FAQ-pages which it will analyze and make its own intents.</p><blockquote>more: <a href="https://dialogflow.com/">Dialogflow</a></blockquote><h3>Oswald</h3><p>Oswald.ai is another conversational chatbot from a Belgium based company. when using the platform you can’t feel or see that it is made by a smaller company. It still supports over 16 languages or dialects but there’s only Python as programming language available. A pretty neat feature that is included is that it can detect typo’s (if you enable it). Let’s say you type “My name is Louise”, Oswald should understand “My name is Louise”.</p><blockquote>more: <a href="https://help.oswald.ai/hc/en-be">Oswald</a></blockquote><h3>Flow XO</h3><p>Flow XO is a UK based company, they provide a really low threshold solution. The setup can be done with almost zero coding knowledge since there are some pretty good template flows available. they support up to 17 languages and have an SDK in Javascript. If you have no coding skills but the knowledge to build a chatbot you can use and modify one of the available templates.</p><blockquote>more: <a href="https://support.flowxo.com/">Flow</a></blockquote><h3>Microsoft LUIS</h3><p>Microsoft Luis (Language Understanding Intelligent Service) is part of the bot service that Microsoft provides on Azure. they provide up to 13 languages and coding solutions in Node.js and C#.</p><blockquote>more: <a href="https://docs.microsoft.com/en-us/azure/cognitive-services/luis/">LUIS</a></blockquote><h3>Comparison</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*pNLOPtgo4-6mhxMxRBsD3A.png" /><figcaption>Chatbot comparison chart</figcaption></figure><h3>Conclusion</h3><p>For our use case and requirements: content must be easily editable and we want to support our current languages (Dutch, English and Polish).</p><p>Our top picks are Rasa and Dialogflow. Rasa because it is open-source, we can easily customize it to our liking to create a seamless integration. It runs on top of Python. We want to host most of our services in-house, Rasa is a perfect example because the repository is well documented with appropriate Docker images. At WeGroup we have a great number of developers that can handle a steep learning curve as Rasa is difficult to master.</p><p>At last, we want to implement Dialogflow because it is easy to set-up and to maintain. We can export the chatbot of Dialogflow and import it into Rasa. There is also a lot of information with examples available and the integration with other services is superb.</p><p>Both of these platforms are supported by a great community which makes programming a breeze.</p><p>We chose to use Rasa as top-level and Dialogflow as a fallback since Dialogflow has great documentation and there is the possibility to export the entities from Dialogflow straight to Rasa.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d70a2392a8f2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wegroup/chatbots-a-comparison-d70a2392a8f2">Chatbots - A comparison</a> was originally published in <a href="https://medium.com/wegroup">WeGroup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>