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.
4th place – Finding The Best Project Management Tool
Just like finding the perfect method, choosing the right tool can be tricky. Forget the popularity and third party opinions focus on the 5 actually important things instead.
3rd place – Scrum vs. Kanban vs. Scrumban – What’s the difference?
The never ending question – Scrum or Kanban, Kanban or Scrumban, Scrumban or Scrum? To help you make your decision, we compare all three based on the work processes and rules that go along with them.
2nd place – Adopting Agile to Sports Training
Agile is a versatile method and there is no surprise it has moved and grown past software development. See just how far it actually went with this application in sports training.
1st place – Entering Life After Scrum
It is just our human nature to always look for the next best thing and as Scrum is becoming ever more popular it is only natural to ask – what’s next? Here is our take on what will be the next shift in the Agile community as Scrum runs its course.
Have a favorite of your own? Share with us in the comments!
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!
We all strive to be the most effective in both our professional and business lives and there are plenty of ways to get there. To do lists, sticky notes, a constant flow of e-mails as well as methods to reduce our stress levels and increase productivity. Getting Things Done is a method that does just that and aims to create a work pace that frees up the mind and lets you focus on what is actually important instead of just being stressed. And while the original GTD talks about a filing system and physical lists, it is hard to miss the similarities to Kanban approach and wonder if it could enhance this process.
Getting Things Done or GTD is a concept introduced by David Allen in the early 2000s. In his quest to minimize the stress levels created by the constant flow of work, projects and emails, Allen developed a system to get us concentrated on just one thing at a time instead of keeping a running tab of things to do. To achieve this, he suggests one simple thing – taking the tasks out of your head and writing them down.
Most of the stress in our lives comes from uncertainty of the outcome and having a running list of things to do in our heads is the epithamy of that. Therefore GTD says you should get rid of that and instead write all of your tasks down, understand the desired outcome and then write down the next step that is going to help you achieve the end goal. This way, you can focus on one thing at a time, while knowing nothing will be forgotten.
Taking on Agile can be a tough challenge, especially if you have no previous experience with it and have no one to coach you. The good news, however, are that all it takes is time and determination to take over and understand. To make that process more smooth for both you and your team, we came up 17 tips and tricks. Use them to reach your goals sooner and more easily.
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 start.
For more helpful Agile cheats and tips see The Ultimate Agile Guide.
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 posts explaining and answering some of the questions most new Agile users have.
To practice any methodology, first you have to know what it actually is and we find that there is still a lot of confusion out there about what exactly can be called Agile. So is Agile equivalent to Scrum as many out there believe? Or is Agile an ancestor of Extreme Programming? Let us try and explain everything.
Agile is a term that describes an effective way of working. It was introduced to the mass public by the release of the Agile Manifesto in 2001 and while it does specifically outline 4 values and 11 principles to be followed by the Agile teams, it does not include any particular methodology or recommendations of a methodology to be followed. So in itself, Agile is simply a framework to be followed.
Naturally, after the creation of the Manifesto, the practitioners felt a need of a clear method to be followed and thus the search has begun. Some looked into existing project management tools and though how they could be made to fit the Agile framework, others created whole new concepts and methods completely from scratch. Thus today we have a wide variety of Agile methods to choose from and new ones coming up every single day. Check out our Agile method genealogy tree.
So to answer the questions we have posed in the beginning, Agile is not Scrum, not XP and not any other method in particular, but all of the methods that comply with the Agile Manifesto are Agile. And as long as you are practicing one of them, your team is Agile too.
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.
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.
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.