6 “Facts” About Agile That May Not Be True
Scrum Masters

6 “Facts” About Agile That May Not Be True

Every occupation has their misconceptions and things that are accepted as real, and the Agile and task management world is prevalent with all sorts of them. Here we will take a look at a couple of things in Agile that might be accepted by some to be a recognized reality within Agile, however in truth they might be misconceptions and definitely arguable.

1. You need to reside in a Nimble world in order to practice Agile

Pedro: We are both fans of Agile, however to state that a person need to reside in a nimble world and practice Agile are 2 various things and the very first appears to be associated to the modifications and individuals analysis. It might look like Agile takes control of whatever. Practicing Agile can be extremely intricate, however it is not constantly suitable to all of your work.

In my case particularly, there is a concern of the business culture and education that misguide you in particular cases with the reality that they have excessive pressure put on day-to-day work. Choices continued fast judgement lead one to neglect a number of various techniques due to the fact that they are thought about time squandered. In this method, often a Nimble technique is selected quickly and without idea.

Joshua: Stating that a person need to reside in a Nimble world in order to practice Agile might not constantly make one of the most sense. While it holds true that you must embrace this state of mind of modification, partnership, and constant enhancement to be efficient at Agile, you need to likewise acknowledge when to use the tools you have. Going all in on a procedure due to the fact that “that’s what the guidelines of Scrum are” (utilizing Scrum as an example), right away makes you less Agile.

From my own experience operating in Robotic Processing Automation (RPA), the huge bulk of my tasks would not fit into what one would usually identify Agile. There is great factor for that, RPA tends to be a number of smaller sized and low intricacy tasks. It’s more of an entire program with individuals operating in different phases of various bots as they go through the bot advancement lifecycle. Agile is made to decrease intricacy of a job, however going complete Agile in my experience in fact increases the intricacy when it pertains to numerous RPA tasks.

We can still generate things from Agile that might not usually be used within the conventional waterfall technique. This concept of putting in feedback loops to guarantee our task is on the best track, for instance. We make efforts as we move through the bot advancement lifecycle to work together with business systems by revealing them what we have actually achieved and making it an indicate ask if things are going as they anticipated. This can, and has, conserved me great deals of time squandered through misconception of their objectives with automating a procedure.

The point is, stopping working to look beyond the Agile box can make you less Agile. Every practice within a Nimble technique is not constantly the very best technique for every single provided circumstance that you might experience. There can be an advantage to sticking to a structure in some scenarios, in others you might discover things work much better beyond what is generally considered Agile.

2. Agile is not a job management technique

Pedro: It is not unusual to hear business state that they do not require task management due to the fact that they deal with Agile. Then we simply ask … “So what would you categorize Agile as? What is the function of using Agile?”

And once again often the response we get is “It’s make it easier”, “it applies to make business running quicker rather of going deep on administration” or “it’s sufficient for designers to arrange in to groups, and we do not require any management to deal with tasks other than for some services and outcomes”.

The fact is that Agile is an incremental iterative advancement life process of task management! Think it or not, it’s a branch, not an option. It indicates that when choosing through a job which type of advancement technique must the group usage, Agile is an alternative which is typically utilized when the group does not have much info on what their task can end up being.

Joshua: Many individuals in Agile do not like the term “management.” I can’t declare to understand their complete reasoning behind the dislike of the word, however it appears to be connected to this concept that we have an employer determining to us what we require to do and how we need to do it. That design of management does not need to exist, even in a conventional waterfall technique. That would fall in line with a more authoritarian kind of management design.

Showing where Agile and waterfall exist under the umbrella of Project Management
Simply as Scrum fits under the Nimble umbrella, Agile fits under the Task Management umbrella

The reality is, somebody, someplace, requires to handle the task and Agile is definitely one technique that can be utilized to handle a job. There are responsibilities that need to happen for a job to move on, and these responsibilities fall under the management umbrella. You might just have an unclear sense of what you wish to achieve and how you wish to arrive, however you still require to direct the group to arrive. That might not always be a function of simply someone, however those “management” functions still require to happen.

I explored this concept a while back with Scrum (Who is the Task Supervisor in Scrum? ). My conclusion is that everybody on a Scrum group is carrying out some task that results in the task being handled. You quite require task management with Agile, you simply do not require that authoritarian design of management. You do not truly require that design of management anywhere.

3. Agile can’t collaborate with other task management tools

Pedro: Nimble deal with nearly all task management techniques and tools I can think about. We might state, possibly, that some tools can be more secondhand then others however nevertheless, not any particularly.

Let’s make a particular example. Agile or any other advancement cycle, more predictive or more adaptive, require to keep track of development. For that reason time management, schedule management, and/or expense management are as essential as any other.

Joshua: Yes. No. Possibly. It depends upon the tool and the existing circumstance.

I would state that numerous typically utilized Nimble tools obtain greatly from conventional task methods. Some tools work much better than others within Agile, and numerous require customized. As Pedro discusses, we can bring with time management tools, schedule management, and expense management– however I believe most wind up customized when utilized within Agile.

As an example, time is typically handled in a different way in Agile, however it isn’t so various that we can’t obtain concepts that operated in a conventional technique. We might simply customize it some. We generally aren’t planning every action for a complete year, and as such a conventional Gantt chart might not work (not to state I have not seen individuals get annoyed attempting to utilize one). What we can do is generate other tools to assist us manage this, or we can customize how the Gantt chart works. In the end we might wind up obtaining things from conventional task management, it simply might not constantly be able function the specific very same.

4. Agile is easier and faster than conventional task management

Pedro: This one is rather enjoyable because, as metaphor, we would believe that Agile resembles a Ferrari and task management is the old conventional Cadillac. When we believe like that, it sounds type of funny and this remains in reality the sensation when we hear remarks like this.

Agile can end up being intricate as “hell.” In addition, what some individuals call as conventional, they suggest predictive, and whatever that it is predictive is for certain more noticeable, for that reason easier. The simpleness that we can comprehend in Agile comes often from some structures that decrease a few of the tools, however that occurs with or with no structure by the hand of the task supervisor. Any task supervisor needs to pick the technique according to the business culture or the task measurement and constantly separately of which advancement technique we are utilizing

Joshua: Easier? No. It’s objective is to decrease intricacy of the work you require to carry out, however doing that isn’t an easy “one and done” kind of procedure. This might make the intricacy of the work easier, however the techniques to do so more intricate. The intricacy that it minimizes remains in our understanding of the work, not in our technique to the work. Calling Agile “Easier” I simply do not think is a precise description of Agile.

Faster? That isn’t its intent and it effectively might not be– which’s not a bad thing. Although, in extremely intricate tasks it might decrease the requirement for rework, therefore making it quicker in the long run. However I would not embrace Agile if your objective is speed. I would embrace it if your objective is precision of your output throughout unpredictability and intricacy. Completion result COULD be quicker, however not always.

5. Task management tools are dead, long live nimble

Pedro: A couple of years ago I became aware of a business promoting a job management software application by stating “task management tools are dead.” This is type of inconsistent, which may be the factor they even altered the brand later on. After all they supplied a fantastic user interface however it was not something to change task management tools. The intriguing thing though, they kept a great deal of terrific traction for that concept of task management tools being dead. About that time, I got some criticism stating that I must think of brand-new tools like them. Nevertheless, the option is not about having brand-new tools, it has to do with developing brand-new manner ins which are much easier to comprehend and easier to follow. These tools existed previously, they exist now, and they will exist in the future.

Agile needs essentially the very same tools as any other task management advancement procedure, they will never ever pass away and definitely not due to the fact that of the development of Agile neighborhood.

Joshua: Whether you are a co-located group utilizing sticky notes on a white board with a video camera to maintain the status, or you are utilizing a piece software application in a dispersed group– Task Management tools will constantly have a location in Agile. The objective ought to be to decrease the knowing curve on those tools and not have them take control of the task.

* Personally, I believe taking an image of the Scrum board everyday and keeping those pictures results in that tool taking control of the task (I have actually seen this done). I discover it Paradoxical that Agile followers typically look for automated methods to release to production or test the complex software application they are constructing to assist improve their procedure– however promote this Scrum board technique as the very best technique. I have actually constantly disliked this technique as it is much more involved than a perfectly developed piece of software application that can do a much better task. I can simply look for the info I desire, you can arrange through your pictures for hours looking for what you desire.

6. Agile minimizes the requirement for techniques and tools

Pedro: If Nimble minimized techniques and tools, it would not be called “nimble” however more like reckless. The only method the techniques and tools are minimized will depend upon task measurement and business culture. Agile can be exceptionally intricate when we go to a number of other structures, making this very hybrid techniques filled with quality treatments for preparation, screening or recognition like normal DevOps systems.

Joshua: As I specified in # 5, the tools will constantly exist. Agile will not amazingly eliminate them, or amazingly decrease their requirement. You need to actively attempt to decrease that requirement, which might even be beyond your power. In some cases, the tools you utilize are more determined by the business you are working for. In some cases those tools have spaces, and you need to patch an Excel file together to fill those spaces. You can grumble about it or handle it– in the end you are going to need to do it in any case unless you can encourage somebody to take pity on your requirements.


So, possibly at the end, the majority of the readers would merely ask “In what methods is Agile various and why is everyone a fan of it?”

We absolutely can’t promote everyone, however Agile remains in reality a technique that can be utilized for tasks which means to decrease failure when the task has lots of unknowns. For that reason, as an easy example, we can simply start initially with a little model, we checked and confirmed, then we transfer to another variation more total. It might still be a model, however we would evaluate it once again. Given that there remains in some tasks a great deal of unknowns, Agile may be the very best technique to look after these unknowns.

Agile isn’t a magic wand that will eliminate tools or the requirement to handle your business’s tasks. If those are your objectives, then by all methods make them your objectives– however do not anticipate rigorous adherence to a Nimble structure to immediately accomplish that. You need to actively work towards your objectives.

Be “task” oriented, be well, and under scope


Header Image from Pexels.com Yan Krukov:

Umbrella icons from Pixabay.com (customized by me): and

Tools image from Pexels.com:

Source link