When 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.
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!
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.
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!
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.
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!
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.
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.
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.
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!
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.
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.
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.