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.Read More
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.
Ah, meetings.. The thing we all hate, yet cannot live without. No matter what project management method your team is using, meetings are always a part of it one way or another. And while most of us associate these gatherings with long and strenuous activities that often yield little to no actual results, when transitioning to Agile you should keep an open mind.
The whole idea of Agile is being effective and eliminating practices that create waste. So when talking about meetings there is no surprise, the same rules apply. No matter the chosen method, all meetings have to have a clear purpose, duration and must yield a result. So to get the Agile meetings right from the start, you should understand that contrary to other practices every single meeting has a very specific value to add to the table.
- Understand the reason of the meeting
Depending on your chosen Agile method, the number, complexity and scheduling of these meetings will differ. Scrum meetings are planned based on the length of iterations, while Kanban meetings are held once the team feels the need for them. However, no matter which method you have chosen, the first thing you will have to do is to understand the purpose behind each of the accompanying meetings.
More often than not, the meetings will be very distinctive and specific – sprint planning is only held for planning tasks of that one sprint. Daily standup only discusses the results and plans and so on. While at first, it may seem hard to keep track of all the different rituals, it is understanding the reason behind them that will help pull you out of the dark. Ultimately this will not only help you, but will also make your teams transition a lot smoother.
- Go by the rules
Another thing that might be difficult to do at first and will possibly slip your mind later, is that the meeting rules and rituals are there for a good reason. It might seem silly to be standing during daily Scrum for the first few times, but this will help to keep the meeting short and on point. And while planning the work for only a two week iteration could seem very irresponsible and short sighted, you will later realize this way of working cuts a lot of planning time in the long run.
Therefore make sure to stay along the lines of the meeting rituals, especially in the beginning. They will create right practices and rituals within your organization and that will help you avoid overcrowded, extended and useless gatherings. And if you still feel that some rituals don’t work for you after you’ve completed a good number of iterations, you can change them. Only then you will have experience and will actually understand what will work for you.
- Have a clear goal to be achieved
Lastly, before going into any meeting, make sure to have a very clear goal and a plan to achieve it. It may be to show your client the results of a sprint and to get an informative feedback in a review meeting or it might be as simple as catching up with the team and logging the progress in the daily Scrum. No matter the type of meeting, without understanding what you are trying to get out of it, you chances of success are slim.
In order to avoid the possibility of making your meetings redundant and fruitless, take some time beforehand and draw a mini plan to understand what you are trying to achieve, who should be involved and how long it might take. By doing that you will save your team a great deal of time and frustration as well as will achieve your goals faster.
Agile meetings and meetings from any other project management practice are not much different – they are all set up to improve project success. However, as with anything else, Agile tries to eliminate as much waste as possible. So to make you do just that, take note of why those meetings were set up and fulfill their requirements as best as you can.
Happy meeting!Read More
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 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.
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 SoS, Kanban and XP have anything in common.
For more helpful Agile cheats and tips see The Ultimate Agile Guide.Read More
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
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
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.Read More
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.Read More