Since Eylean Board is more than just a standalone project management software, this time the webinar will focus on the two way integration with Team Foundation Server.
We will discuss:
- Introduction to TFS and Eylean integration;
- TFS and Eylean mapping tricks;
- Shifting TFS process with Eylean templates;
- Integration with TFS online (www.visualstudio.com);
- Multiple workspaces in Eylean for only one on TFS;
- Your questions.
Register now and find out everything you wanted to know about integrating TFS and Eylean Board.
It is becoming more and more evident that the future of Agile lies in large companies and scaled approaches. It may be hard to believe at first, but the data of Agile usage in 2015 proves this is where the methodology is going next. One of the most popular ways to scale Agile today is Scrum of Scrums. And while many companies have adopted this practice already, we thought it might be interesting for others to know just how exactly it works.
Scrum of Scrums has been originally defined by Jeff Sutherland and is designed to deliver working software of all teams to the Definition of Done at the end of the Sprint. To make sure this happens, the Scrum of Scrums Master is held accountable and has to be able to ensure that all the processes works. But before getting into the details, let us step back to the beginning.
The recently released State of Agile Report has not only brought great statistics, but also raised a few questions about just where Agile might be heading next. How will it look like in a couple of years, which interest groups will shape it and how much of what we today call Agile will actually change?
To get a better grip on these and other questions, we took another hard look at the stats and came up with what we think the answers will be. Check out the info-graphic below to find our predictions for the future of Agile.
There is no more surprise that large companies are adopting Agile practices. They have to be more flexible, need to adapt to the changing market and simply want to benefit from the various positive sides of Agile. However, this method is created for small teams of a few people and thus scaling up can prove to be difficult. Especially when wanting to stay true to the practices of Agile. One way to achieve this successfully within a large organization is SAFe.
SAFe stands for Scaled Agile Framework and has been around for some time as a way to scale up the small team Agile practices. SAFe 4.0 reforms the traditional organizational thinking based on managerial levels and instead divides the company into 4 levels of self-organizing teams – Team, Program, Value Stream and Portfolio.
As any project manager would tell you, having a great team is one of the key factors in project success. They will help you face the challenges, look for solutions and deliver a result that you are looking for. Agile teams are no exception and can either help you to achieve goals or be a destructive force for the whole project. So how do you form an Agile team that will bring the success you are looking for?
The most important thing you have to understand is that the traditional teams and Agile teams are two quite different things. Simply slapping new titles on the old team does not an Agile team make. The key difference between a traditional and an Agile team is that the latter has to be completely self-sufficient. In other words, it has to be diverse and independent enough to produce a working, tested increment of a product. To make sure your new Agile team can do that, there are a few things you should be aware of.
While for the traditional teams it might be perfectly fine to have five designers and no developers, this will be nowhere near okay for Agile. By definition itself, Agile teams have to be diverse enough to produce a working part of the product. This means that an Agile team has to be made of just the people that are needed to do that.
When starting to adopt agile, most of us have some misconceptions about the practice. Some think the amount of work will go down greatly, others throw out all the documentation and even suffer through the first stand-up meetings. Eventually this passes, but we thought it would be fun to remember those first days with a few of our favorite Agile comic strips.
- Is anything actually changing?
- Why are we standing again?
There is no doubt Agile is no longer just a practice for developers. It has moved past only serving the small teams, past the specific types of teams and past the specific industries. While that is all widely known, sometimes it is still tough to grasp just how far Agile methods have come. That is until you hear that the methodology is now being adopted to sports training. Yes, you have read it right, Agile methods are now being adopted to organizing sports.
The first time we have heard about this new exciting development was from a Serbian physical coach Mladen Jovanović. He has been involved in various sports activities his whole life and has recently heard about Agile practices and Eylean Board.
Being an innovator he naturally got interested in how this may be adopted to his field and how it can benefit the parties involved. By creating several boards and dividing the process into clear steps, he managed to translate the Agile practices into sports seamlessly. To know more about his process and findings, watch this short video.
We at Eylean strongly believe in organizations that work hard to help others. Whether it is an NGO that aims their efforts at the biggest problems out there or educational institutions that are raising and enlightening the next generation, their contribution to the society is invaluable.
To express our support to such organizations, we offer a 30% discount to all non-profit and educational organizations for any of our subscription plans. We hope that Eylean Board will become an invaluable asset in managing projects, teams and time, just like it already has in many organizations before.
To apply for the nonprofit discount or to get more information, follow the link on our pricing page: http://www.eylean.com/en/Planning-board-pricing.
After looking into Lithuanian startups and their views on Agile we wanted to compare them with startups from other countries. This time we took on Germany and surveyed startups from various fields asking them what they knew about project management and agile.
While the two surveys yielded similar results in that Agile practices are well known and practiced, there were some key differences as well. Within Lithuanian startups Scrum and Kanban were used by an overall majority of Agile practitioners, while in German startups, they only racked up half of the votes, leaving more space for Scrumban and other methods.
Lithuanian and German startups also found disagreement in the positives and negatives of Agile. One party said that the practice increases team motivation, while other stated the opposite. Time planning, process control and result evaluation were also mentioned – see the full infographic to see how they compared.
For teams that have successfully adopted Agile, the next logical question is – what will follow? While in some cases there is no next step and the adopted practice suits perfectly, for others further modification brings in better results and more value. So what should you do if you want to innovate further?
Take a look at these 5 options.
One of the most popular Agile modifications at the moment is scaling up. It is only natural that companies want to extend successful methods from small teams onto the whole organization. However, since the method in itself is built for a small singular team, some adoption and changes are inevitable. For that scaled practices such as DAD, SAFe and LeSS have been developed. So if you want to convince your CEO, see how these approaches can fit your case.