We are happy to announce that as off last week, Eylean Board has been published on Windows 10 Download page and is now accessible to all of its users.
In creating Eylean Board, we strive to make the lives of our clients easier and go step in step with the latest trends. We make sure to stay up to date to the changing project management practices, evolving methodologies and the changing technology. Therefore, as long time Windows users ourselves, we are excited to have our product now available for all versions of Windows – Windows XP, Vista, 7, 8 and the newest addition of Windows 10.
As a project management software company, we are often asked, which of the PM methods are the most popular and most commonly used today. To find the answer to this question, there is no better way but to ask or look into the market itself. So today we take a look into boards, reports and task actions that Eylean users choose the most.
Looking at the top boards, we find a variety of them at the disposal of Eyleaners. There are Kanban, Scrum and Scrumban boards being used by some, TFS template boards, used by others, but the overall winner, however, is the Basic board. This might seem strange with the overwhelming popularity of Agile methods today, however, there is quite a few reasons behind this choice, such as a complicated process, transition between methods, adoption of a new method and so on. Choosing a basic board option, allows the team to start using the tool quickly and to develop the exact process on the go, by modifying the board to suit their needs.
Over the years we have witnessed a definite progression in Agile practices. The method that was first aimed to help small teams, was later scaled to change processes in companies and is now starting to affect the overall understanding of business management practices. The natural next question is – when will Agile spread beyond business and into other parts of our life? Will it reach the government and will it eventually become imbedded in our culture?
There is a long standing tradition of taking the best practices from the private sector and adapting them to the government. This usually takes time, while the practice effectiveness is proven and the right way to adopt it into the goals of a government office is found. However the implementation almost always leads to more efficiency, reduced spending or other significant changes and improvements of how the officials operate. With Agile gaining great traction all over the private sector more and more wonder – can it be the time for the government to consider it as well?
With Agile gaining bigger and bigger traction each day, there is no wonder why many companies are starting to adopt it and claim to be Agile. The change, however, is not overnight – it takes time and effort to implement. Due to this, many corporations choose to adopt Agile incrementally with a method that is now being called Water-scrum-fall. However, can it actually be better to use the transition method?
To answer this question, let us first explore what hides behind the term Water-scrum-fall. This definition appeared in Agile circles not too long ago striving to describe a process in which large companies choose to practice both Waterfall and Scrum methodologies at the same time. This is usually done to introduce a more efficient Agile process into some phases of the project, while leaving other phases untouched and managed in the traditional way.
Such a solution has become a great option for large companies in which some teams are pushing for change and a more flexible way to complete projects, while others are holding on to the established processes and refuse the necessity of change altogether. With Water-scrum-fall, the teams get to decide which of the two management methods is the most suitable for each situation and use it to gain the best results.
As recently discussed in the 2015 review, more and more Agile teams are starting to sway away from Scrum and lean towards a different methodology – Kanban. While this may be surprising at first, there actually is good reasoning behind this switch and possibility of this trend continuing into the 2016. Will you be switching as well? Let’s see.
The need for order
For most companies, Scrum has come at a time, when there was a need for a more flexible and at the same time a clearer approach to project management. This was especially true in the case of software development teams that lacked processes and often produced results, just not the ones management was looking for.
As the holiday season ends, we find ourselves looking onto the New Year and making promises to be better, to achieve new goals and to get rid of old habits. The sad truth however is that as the days of the new year start rolling by, we tend to minimize, put off or even forget our resolutions altogether. For most of us the New Year resolutions never come true. But is it really impossible to make sure you stick to them? We say no – all it takes is a little effort and determination on your side.
The main problem we encounter when trying to fulfill our goals is the lack of understanding of our own capabilities. When these resolutions are made, we often forget to think about how it will be us that will have to make them come true and instead we just envision the best possible version of ourselves for the following year. To make sure this imagination is dosed with some reality, there are three little tips you can follow.
A little while back, we covered our top 5 project management plugins for TFS. Since TFS is not just about project management, but also about Agile, this week, we thought of taking a look at the best 5 Agile plugins for the Team Foundation Server. Before you are our picks for the most beneficial plugins.
In the fast moving office life, we crave for some information to be as concise and precise as possible, unfortunately, TFS lacks such overview. Here is where Sprint Monitor from Pedro Pombeiro comes in. designed to be displayed on a LCD screen in an areas where teams meet up to discuss process of the project, it provides key information such as latest build status, remaining workload, average time spent on a backlog item and more. It will help you quickly oversee the project status without getting stuck on the small details.
Another year nears its end and before the holidays take over our mind completely, we thought it would be interesting to take some time and look back. Every year we analyze data from Eylean to see how our clients have used it and how can we improve in the next year. Most of this data is quite technical, but just like last year, we want to share some of the more interesting findings with you.
Country of origin. Over the years, we have been enjoying a steady growth of interest into project management software. Last year we were happy with an 81% growth of Eylean users and this year we are even more excited with a doubled 156% growth. Most of the new users came from our biggest market – the United States (31%), however, this year we also have new markets in our portfolio, such as China, France and others, proving that agile project management practices are becoming more popular all over the world. While there is some movement in the new markets, the top 5 have retained their strong positions with only some slight changes in the numbers.
Finding out about and covering various Kanban approaches is always very interesting – we want to stay on top of innovation that you are creating in the market. So when a creator of the Arrow Kanban board, Tomas Rybing, reached out to us with his new invention, we were both eager and excited to check it out. This time, he presented the Volcano – another interesting take on the traditional Kanban board.
According to Tomas, the Volcano was born out of the bugging need to combine multiple teams and multiple projects into one space. Unfortunately, the traditional Kanban board layout was not ideal for such a situation as everything ended up being mixed up and hard to separate. To achieve a clearer and more comfortable Kanban setting, he decided to separate the board into specific sections – one dedicated for the multiple product backlog and one section for each team involved in the project. This separation allowed to plan and prioritize the work globally, while at the same keeping the process of each team away from each other.
Quest for the best mix of project management tools is known to new and veteran managers both. While the supply of such solutions has grown immensely over the years, instead of making the decision easier it actually made it much more difficult. Choosing the right tool for the job, not getting influenced and derailed from your actual needs is what we seek to do, but often fail simply because of the overwhelming information available. To make this decision a little easier, we decided to narrow things down to five categories of tools you will need for your next project.
Few projects can happen with no project management, we need to have order and known when the things are supposed to be done. To make this goal as easy as possible, you will need some sort of project management tool or software. Choose what fits your style and the team you are working with – some will do just fine with a whiteboard and markers, while others will feel more comfortable with a specified software like Eylean Board designed to handle large projects. In any case, this will be crucial to your progress as you will plan, monitor and execute the work ahead according to this tool.