Eylean vs. Trello – 5 Ways The Big Player Looses

eylean-vs-trelloWhen it comes down to choosing a project management tool, we always search for the best, the most suitable for our projects and our working habits. Many of these searches come up with Trello as a possible answer at one point or another and many teams end up choosing the online project management platform as their tool. However, I strongly believe, that this is not the sole solution in all cases and therefore want to discuss five instances where Eylean Board actually comes out on top of the industry giant.

Ready? Let’s go.


The first big difference between Eylean Board and Trello is how they are used. Eylean can only be used on premise, via a local or an Eylean server, while Trello is used online. Right from the get go it is clear that the two quite similar tools cater to two different customers. The ones always on the move and in need of data accessibility anywhere are the Trello customers, while the ones working in one place or concerned about their data security are the Eylean Board customers. So if you are concerned or restricted in the way you handle data, the offline tool might be a more attractive solution. In some cases, however, the customers do not really care about whether the tool is online or offline, so let’s see what other differences the two have.



Another big separation between the tools comes out in the board formats. Trello offers standardized boards, with a possibility to have more or less columns. This is good for customers that have simpler processes or are only looking to have a To Do list. Eylean Board on the other hand offers fully customizable boards. The columns can be divided into specific sections with their own sub-columns, allowing to visualize the process with more clarity and to divide large steps into smaller ones. Eylean’s board can also be divided into rows, useful in separating sprints or projects visualized in the same board.



Talking about Agile, Trello is accustomed to fit Kanban users, but other methodologies are a little more challenging or even not possible. Backlog prioritization, WIP limits, Lead & Cycle time diagrams as well as other Agile methods like Scrum and Scrumban can only be found in Eylean Board. Here you can easily define sprints, assign story points, oversee a Burn-Down chart and benefit from other Agile functionalities. Therefore those needing more than a simple Kanban solution, can benefit much more.



Talking about team management, both tools allow working on the projects with several people, assigning tasks to team members, sharing documentation and discussing the progress directly inside the tool. One difference between them is the ability to assign team roles within Eylean Board. With it, the project manager can limit the access certain team members get to information, task management and deletion in order to keep control of the project.



The last big difference is the integrations – the two solutions have entirely different perspectives. Trello offers a developer API, meaning that you can develop an integration you need. We at Eylean have a little different approach with already sorted integrations that our customers can use out of the box. This way you don’t need to be a developer to use the integration and instead can simply enjoy the results. At the moment Eylean Board integrates with MS Project, Outlook, Excel and Team Foundation Server.

Below is the full comparison of the two tools. Enjoy!


Read More

5 Eylean Board Features To Make Project Management Easy

1. Visual board1

No matter if you have just started using Eylean Board or have been doing it for a while, it is always a good time to refresh the memory and improve the processes. That’s why this week I came up with a list of the 5 Eylean Board features that you may have forgotten or discarded, but may actually be able to benefit greatly from. So without any further ado lets dive in.

Custom Task Boards

Now, I am sure you are well aware of the possibility to create custom task boards within Eylean Board. However, did you know that you can modify the predesigned and the ones you are currently using as well? Simply hit ‘Configure’ at the top of the screen and add, delete and rearrange any columns or rows you wish. Just make sure that you remove all tasks from the column or row you wish to delete before and go ahead.

So if your process suddenly changes or the board structure does not satisfy you anymore, change it and keep on enjoying the best setup for your team!

Task details

Visualizing Task Schedule

You are probably already using the task details quite a lot – the descriptions, assignments, due dates, attachments, etc. But did you know that by adding ‘Start date’ and ‘End date’ will visualize the specific task duration in the schedule? This way allowing you to better understand the duration of each process and to plan better.

E-mailing task information

Ever feel the need to share specific task information and documents with a colleague, client or a third party? We got you covered – open the task details and hit ‘Send as email’. All of the task information as well as its attachments will be composed into an e-mail automatically and all you will have to do is enter the recipients address.

time trackDrag & drop time tracking

It is no secret that you can track time spent on tasks, projects or by specific team members with Eylean Board. However, some tend to forget just how easy it actually is. Before starting to work on a task, all you have to do is drag & drop it on the clock at the top right of the screen. The tracking will start immediately and will stop once you drag a different task on the clock or hit a stop button either by the clock or on the task itself.

TFS integration

Last and one of the best features Eylean Board has to offer is the integration with Team Foundation Server. Granted, it may not be for everyone, but if your team or some of your team members use TFS, it is a great one. Why? Because it is a two-way integration. So instead of having two tools and two versions of the information, you have the same information in both places. Therefore not only expanding the TFS capabilities of project management, but also making sure there are no mix-ups and miscommunications between the two tools.

Have you seen something you like? Give us a shout in the comments!


Read More

Make Your Agile Resolutions Stick

new year

We are all guilty of failing to keep up with our New Year resolutions as soon as the first few weeks pass by. Whether it’s taking up a sport, quitting smoking or anything else, we often find we have too little will to keep on with the changes. Our business transformations are just the same in a lot of ways and after starting with a new and exciting Agile method we need true commitment to actually make it stick for good.

Sounds hard? Well, change is never easy, but it can be made easier if you know how to make sure you and your team accept it.

Proactively form new habits

Starting something new is always fun. The first day of not smoking you feel motivated and eager to prove yourself, however, as the time goes by the excitement fades. And here is where most of us start failing in our new goals. Taking up Agile feels just the same and soon the team will forget the shiny new toy and revert to the old ways if new habits are not reinforced. So instead of starting Agile and letting it go, make sure to proactively form new rituals within your teams for at least a few months or even longer to actually make them stick.

Put in the effort

Just as you can’t expect new habits to form on their own, you cannot hope that the change will just happen. Instead it will require time and effort from both you and your team. You will have to try, fail and repeat this cycle until you find a way that works best for you. This is where the iterations and retrospectives will become your best tool so remember to use them and make according changes every time. Without some effort from yourself, the changes might never come.

Think about what can prevent the change

Just like with your New Year diet, slip ups will happen. However, instead of going to your first reaction and punishing that behavior, you should take some time and realize why did it occur? Does your team prefer working the old way? Is it faster? Why? Do they fail to see the long term benefits of the new method? Get to the bottom of the reasoning and communicate the importance of change to make sure it does not happen again.

Enable change

With a change of method, there will inevitably be a change in the team’s behavior. Starting from the small stuff as the need for task boards and space for daily standups to restructuring teams and collocating them to get the best result. Whatever your team needs give it to them, thus enabling and not blocking the changes. It will make the transition easier and the risk of reverting back smaller.

Get support

Finally, most of us need a little push to achieve greatness and so will you. Get a coach to guide you through the transition, to set up the best practices and to navigate arising issues. It will make it easier on both you and the team and will ensure your investment pays off.

Have your own tips on keeping up with New Year resolutions? Share in the comments!


Read More

Season’s Greetings from Eylean

Eylean Christmas (small)Thanks to You it has been a great year and we hope the next one will be even better. We hope your holiday season is full of joy and that you greet 2017 with new ideas and replenished energy!

Eylean Team



Eylean Christmas

Read More

The Best Agile Articles Of 2016 (Part 2)


This is the second part of the favorite Eylean articles of 2016. The top 5 brings us back to the beginning of Agile application, a lot of great advice on how to make sure you succeed as well and a nice example that it is not for software developers alone.

Keep on reading to find out more!


5th place – Choose The Right Agile Method

Agile methodologies might seem tricky, especially if you are choosing one for the first time. See what the key differences between the different options are and choose the right one based on the type of work you do.

Choose-Agile-method for posting


4th place – Finding The Best Project Management Tool

Just like finding the perfect method, choosing the right tool can be tricky. Forget the popularity and third party opinions focus on the 5 actually important things instead.

1. Visual board1


3rd place – Scrum vs. Kanban vs. Scrumban – What’s the difference?

The never ending question – Scrum or Kanban, Kanban or Scrumban, Scrumban or Scrum? To help you make your decision, we compare all three based on the work processes and rules that go along with them.

Scrum-Kanban-Scrumban for posting


2nd place – Adopting Agile to Sports Training

Agile is a versatile method and there is no surprise it has moved and grown past software development. See just how far it actually went with this application in sports training.



1st place – Entering Life After Scrum

It is just our human nature to always look for the next best thing and as Scrum is becoming ever more popular it is only natural to ask – what’s next? Here is our take on what will be the next shift in the Agile community as Scrum runs its course.


Have a favorite of your own? Share with us in the comments!


Read More

Get 3 Months For Free


The holiday season is almost here and we want to help spread some joy!

We will give 3 Eylean Board months for free for all 1 year subscriptions made before the 31st of December. Choose your plan, your team number and order – the additional 3 months will be on us!

Place your order here.

Get ready for the New Year by making sure your team is taken care of!


Read More

The Best Agile Articles Of 2016 (Part 1)


As the holiday season and the New Year approach, I wanted to take some time and review your favorite Agile articles of 2016. Maybe you’ve read them all already or maybe there is still something new and exciting to learn.

Without any further ado lets dive in.


10th place – Top 5 Most interesting Scrumban Boards

Learn all about the creative and clever ways to organize your Scrumban boards. These teams are certainly doing it right.

Source: Drew

Source: Drew


9th place – The Ultimate Agile Guide

The inside look into the way Agile functions, how to choose the right approach and not to fail during the first week. Enjoy the tips & tricks gathered from our experience.



8th place – Agile Hierarchy – How Are The Methods Related?

Ever wondered how all of the Agile methods relate to each other? From which method, did another evolve? We have all of your answers in one nice Agile family tree.

Agile-Hierarchy for posting


7th place – Transitioning to Agile: Running Effective Meetings

When transitioning to Agile it may be difficult to grasp what counts as an effective meeting. Instead of wondering if you are doing a good job, take a look here and know for sure.

Startup Stock Photos


6th place – The SAFe Way To Scale Agile

Is your company ready to move Agile from small teams and into the company mindset? Learn all about scaling Agile with the SAFe method and see if it could be a solution for you.


To be continued with the top 5 articles next week – keep on reading the year is not over yet!


Read More

Using MoSCoW in Agile to Prioritize Better


One of the key ideas in Agile is prioritization – a team needs to understand which features must be done and which can be left behind in order to produce the best result. However, the concept can be quite difficult to grasp when moving from a different project management approach. A prioritization technique called MoSCoW brings great help and clarity in such cases.

First used with Dynamic Systems Development Method, MoSCoW is a technique developed by Dai Clegg. The sole purpose of this prioritization approach is to help understand the importance that the stakeholders put on each of the features and requirements they pose. Thus being able to focus on the exact most important ones first and tacking on the rest only if the team has time left.

The technique requires to divide all of the features into four categories – Must, Should, Could and Won’t. Thus forming the MSCW acronym from which the name MoSCoW appears. In order to know which of the features are crucial, the team has to categorize them into the four groups.

Read More

Agile For Legal Teams – Are There Any Benefits?


It is long past the days where Agile was only about software development and coding. We now have financial, marketing, sales and many other teams successfully adopting the practices in their day to day activities. However, there are some more specific industries that still doubt the benefits and use of Agile in their line of work. One of such cases is the legal industry and those in it often wonder – are there really no benefits of having an Agile process?

Before answering this question, let’s talk about the Agile process adoption in the legal field overall. While some of you might be questioning the application possibility, there is no doubt that Agile could be fitted into the process. Legal firms would be able to treat their clients as projects and gather their needs as user stories which would later be broken up into tasks and performed over a series of iterations.

As we have seen from applications in other fields, some changes to the methodology might need to be made, but in general there is no question that legal teams would be able to use the Agile process. However, just being able to do something doesn’t mean that you would actually benefit from it. So let’s see why would the legal companies actually consider switching to Agile project management.

Read More

Becoming A True Agile Leader


As the world keeps talking about the results of the US presidential election, I thought there could be no better time to talk about leadership. However, this blog is not about politics and is not about to become one. Instead, I am taking a look into what it means to be a leader in the Agile community and what does the term Agile leadership actually stands for.

Want to know more? Here is your chance.

Contrary to most terms, there is no one clear definition of what Agile leadership is. In fact, some even argue that this concept on its own is foul and should not even be discussed. While it is natural that Agile community rejects the idea of a traditional leader making orders at a Scrum team, it is important to understand that the concept of Agile leadership is quite different from this traditional one.

The concept of Agile leadership was not created to rule the team or the process, but instead to make the said process run more smoothly. While any small team is perfectly capable of getting customer requirements, prioritizing and dividing tasks and presenting the results to the client, as Agile grows the organization is becoming more and more difficult. Larger companies are stepping into the Agile game and the industry is moving away from one team companies and one project teams, therefore an undeniable need for clear goals and inter-team organization appears. This is where Agile leadership comes in.

Read More