Agile Hierarchy – How Are The Methods Related?

Agile-Hierarchy for posting

Have your ever got lost between all of the Agile practices and frameworks? With the methods evolving, changing and appearing constantly, it can get difficult to understand, how they evolved and turned into the form of today. Therefore we decided to make this quick cheat sheet for anyone wondering if SoSKanban and XP have anything in common.


For more helpful Agile cheats and tips see The Ultimate Agile Guide.

Read More

5 Agile Rules To Follow Now


Whether you have just started using Agile or have been doing it for years, there are no guarantees that your process is flawless. With a methodology as vaguely described as Agile many teams find themselves repeating mistakes of the past and still lagging in their process or wasting efforts. However, just like with everything else in life, we are here to learn from those mistakes and thus give you 5 rules to ensure you stay on the right path.

1.       Do not design, do.

While most teams simply cannot do without an initial idea and a sketch of what the final result will look like, many forget that with Agile that is all they have to do. Instead of focusing time and efforts on the perfect design, the team should simply start working on the product and perfect it along the way. The Agile process is created exactly for that and will allow to find the best design not only for the team, but for the customers and other involved parties.

2.       Do not micromanage, lead.

After switching to Agile, the change has to be made not only within the organizational process, but also within the mindset. While the team adopts to changes sooner or later, most companies face problems with the managers. They are usually used to being responsible and somewhat controlling of the team results and in order to keep that feeling in Agile, turn to micromanagement. This, however, obstructs the Agile process, prevents the team from finding the right rhythm and should be avoided at all costs.

3.       Do not wait for feedback, ask for it.

Daily scrums, reviews and retrospectives help keep Agile teams on the right track. However, most teams go into these meetings simply looking for approval that their result is okay and not asking any questions on how it could be made better. By doing so, they miss out on crucial information on what the customer actually wants and in the end deliver a mediocre result. To get the result both you and the client is looking for, use these meetings to ask important questions and to define what sort of product your customer wants, instead of simply getting the OK.

4.       Do not discuss, show.

Another big issue when discussing the final product with your client is in fact the discussion itself. Teams tend to waste quite a bit of time discussing what the product is now and what it should be, instead of simply showing the completed result. When you have a chance, always show the result you have thus far, this will give the client an opportunity to see and understand it a lot better. Not even the best description can surpass having the real thing in front of you and this way you will save quite a lot of time and effort you would have spent explaining things.

5.       Always provide a working prototype.

Talking about showing the product, there is one more thing you should know about prototypes. While you might be tempted to create a fake, better looking version of your final product to show to the client, in most cases that is not a great idea. You should always show the real product in the state that it is that day. This way the stakeholders will be able to try it out, evaluate the UX and give feedback for corrections, something they would not be able to do with a fake. So to get the full and honest review, make sure they can press that button and see what happens.

Have any other rules Agile teams should follow? Share in the comments below!

Read More

The Ultimate Agile Guide


As Eylean Board counts its fifth year this summer, we felt the need to not only celebrate, but to also share the experiences and knowledge we gathered over the years. And since we are all about the Agile methods and practices, an Agile guidebook seemed like the logical way to go.

Now we are sure you have read many guides explaining what Agile is and how it works, so instead we focused this guide on our personal experiences and tips about the methodologies and how to apply them. We took our own, our clients and third party experiences into account and came up with tips and observations to help in various Agile transition processes.

We hope you enjoy the tips and have a smooth Agile adoption!

Download The Ultimate Agile Guide


Read More

The Inevitable Search Of A New Agile Mindset

mindsetFor most of us the concept of Agile is nothing new – it has been around for quite some time and we have a good amount of experience with it under our belt. However, Agile is only now reaching its maturity and that means the practices and its methodologies are still changing. There are new methods, innovations and adaptations coming up constantly and the only thing that has remained the same over the years is the Agile Mindset.

The Mindset has been defined by the Agile Manifesto in 2001 and has been barely touched since. Though what has worked effectively for small development teams in the beginning is a far cry from the answer nowadays. As of now there is yet to be an updated version of the Manifesto or anything that could put its values closer to what we need today. However, due to the changed ways we practice Agile, we believe soon there will be.

Don’t think so? Here are our top 5 reasons why the Mindset will in fact be updated and soon.

Read More

5 Tips For A Smooth Agile Transition


Whether you are taking Agile on for the very first time, coming back to it after a previous attempt or simply going from one Agile method to another, there are some key things to remember if you want to keep the transition smooth. Check out our 5 key tips on a smooth Agile transition to end up on the right side of change.

  • Understand what is ahead

As with any change in life, first and foremost, you have to take some time and understand what is ahead. We are sure you have not chosen your new method impulsively and put in time and thought making sure it was the right fit. So do not cheat yourself and take some time aside to really understand how this change is going to affect your processes, your team and your company. It may seem silly but having a clear future vision in your head will help you better understand and guide the transition once it takes place.

Read More

The Many Hats of a Project Manager: Daily Struggles and Solutions


It is no secret, that project management is more than just following deadlines and overseeing work. No matter the size of the company, managers have to take on various roles to make sure their team reaches the desired result. This role juggling may be well known to the experienced project managers, but for those still ranking up their expertise, multiple hurdles await.

Check out our list of the most common project management daily struggles and their solutions.

  • The lack of motivation within the team

When managing a group of people all in pursuit of the same results, you will inevitably find yourself dealing with team members that seem to have lost their drive. It will put your project behind and influence the rest of the team in a negative way. When faced with such a situation, it is important to remember that it is your job, not to only create the plans for the future, but to also make sure the team is motivated to complete them.

Read More

Top 5 Most Interesting Scrumban Boards

scrumbanAs most of you know, Scrumban is a mixture of Scrum and Kanban methodologies made in search of a stricter Kanban or a looser Scrum. While there are not many companies that go to Scrumban straight out of the gate, many find their way into it after a while and settle in a comfortable balance between strict and loose that this approach brings.

Just as you might expect, every team strikes this balance a little differently and this is very clear looking into their boards. To compare, lets take a look at just a few of the most interesting Scrumban boards.

Back office manager

scrumban 1

The board used by Wibas, is a great example of Scrumban. It is a nice mix of the two methodologies that allows the company to manage their back office efficiently and with ease, while keeping the priorities straight.

Read More

Maximize TFS Potential With Eylean


Last week we hosted a webinar on integrating and driving value from the merge of Eylean Board and Team Foundation Server. The webinar was focused on integration details, expanding of functionality, advantages of the integrated solution, compatibility, driving value and application possibilities . 


For those of you that have not been able to join us or simply want to remember the details, here is the recording of the webinar. We hope you will find it valuable and we will be waiting for any questions you might have regarding.


Read More

Scale Agile with DAD


Keeping up with our previous coverage of scaled Agile approaches, this time we want to bring Disciplined Agile Delivery otherwise known as DAD to your attention. Like other similar frameworks it focuses on bringing the small scale practices into the big leagues and on shaping them to fit the new rules. Compared to previously discussed SoS, LeSS and SAFe, DAD is less descriptive and requires more Agile knowledge, however it allows for far greater flexibility within the team. So will you be scaling with DAD?

The framework known as DAD was first mentioned by Scott Ambler and Mark Lines in their book by the same name – Disciplined Agile Delivery. It was designed as a way to move past Scrum while the wholesome view and approach allowed teams to grow from small independent groups into large organizations.

Read More

SoS vs LeSS vs SAFe – Which One Is Right For You?


As the need for scaling Agile practices grows, there is also a growing confusion about which of them are the best and which will actually fit your needs. At the first glance, most of the scaled approaches may look the same but in reality picking the right one is key for successful application. To help you choose your framework, we decided to take a look at Scrum of Scrums (SoS), Large Scale Scrum (LeSS) and Scaled Agile Framework (SAFe) and to write down the key differences as well as similarities between them to help you see how they stack up.

Interested? Let’s dive in!

  • Agile Methodologies In Usemethod

Both SoS and LeSS rely solely on Scrum, applying its practices and roles at a larger scale. This makes these approaches ideal for teams that are already using Scrum and want to scale up without having to go through a large reorganization for it.

Read More