Finding the right Agile practice for your team can mean long hours and rigorous research. That’s why after finally deciding on a way to go most teams want to get the implementation over with as soon as possible. No matter what you will have to go through the adjustment period and make sure the new practice sticks, but there is no such thing as this process having to be difficult and we at Eylean believe…
Agile implementation never happens instantly. There are various steps to take and hurdles to defeat before your team gets to the end and starts enjoying the benefits. This, however, doesn’t mean you have to struggle. And we at Eylean want to aid your efforts with this starter pack.
This blog is full of various tips, tricks, application examples and other helpful stuff. But you are probably too busy running your teams and businesses to go looking. That’s why instead we prepared one stop helpful resources for you and your team.
The last of my cheat sheets (so far) comes in the form of Scrumban. A mixed Agile approach that aims to merge the two most popular practices Scrum and Kanban. While some say that this is the most unstable and changing approaches of the three, there are still some things that stay the same no matter the application.
So dig in, enjoy and let me know if you think anything else should be added!
This week I continue with our article roundup – an effort to provide you with all our knowledge in one convenient place. After the two previous posts on project management and agile, I thought it would be time to go a little deeper and this time we are talking about Scrum. Yup, the basics, roles, estimations and anything else you might be looking for, I’ve got it right here.
No Scrum project can be started without knowing what you are doing and while you may have already read all that goes into the practice, actually doing it is different. Check out Getting Started With Scrum Task Board to set up your first board, read Frequent dilemma: what sprint duration is best for your team to figure out what sort of a sprint duration to choose and pick out the scrum cards for you with The 4 Scrum Cards To Consider.
Once you are all set up and the actual work begins, learn how to write your first user stories with the help of Writing Effective User Stories for Scrum and choose the best way to estimate work by Estimating in story points compared to hours.
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.
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.…
The next big question after deciding to go Agile is deciding which of the methods is right for you- will you go with Scrum, SoS or SAFe? While this decision is not an easy one and will take careful considerations, there are some aspects to each of the method that can help you along the way. Below you will find our easy 3 step process that will guarantee you consider the right options from the…
Understanding how do Agile methodologies differ can be a daunting task. Some get confused with the overwhelming amount of information, others are disappointed with the lack of clarity. Ideal way is to have everything at single glance and compare pros and cons in each framework. To make sure it is easy enough, we present a short and clear table listing the main differences and similarities between Scrum, Kanban and Scrumban. For more helpful…
Agile is not a new concept in the business world by any means – it is being adopted to more and more various fields, innovated and even discarded by some teams that feel they have had enough and are ready to move on. However, as the Agile reign continues, we find some of the practitioners are still trying to figure out how exactly to be Agile. For this, we are launching a series of blog…
As 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
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.