Category

Agile

Category

After deciding to go Agile, we change many things about our process and structure. However, many fail to understand that the people in our projects have to change as well. Whether it is adopting to new roles or accepting new people into the team, without these changes there is no chance to have a successful transition. I have already talked about the details of going from a project manager to a scrum master. Thus this time…

Kanban is by far not a novelty in the Agile world. It is a well-practiced and known method amongst those that seek to optimize their efforts and improve results. However, up until now it has been seen as more of a loose approach, only offering vague guidance to its user. This resulted in many teams preferring other Agile methods that are more structured and thus missing out on what Kanban has to offer. However, a…

A couple weeks back, I have written about an alternative viewpoint that is gaining traction in the Agile world. It is commonly known as Agile at scale and talks about reinventing the practice instead of trying to fit the small team canvas onto the large organizations. Today I would like to dive in a little deeper and talk about one of its practices – the Product Forum. To put it simply Product Forum is a…

As Agile becomes more and more popular across companies and industries, there are bound to be some changes to the way it is done. It has long left the realm of software development teams and has since been applied to various fields such as marketing, finance, sales, you name it. However, as the popularity grew, one issue has become more and more prevalent – Agile in large organizations. To which Agile community has seemed to prepared…

We all know and love Agile boards. Whether they are a simple three column progress indicator or a complex design representing our whole process, there is no doubt how much easier they make our projects. However, when starting out or wanting to innovate the form of the board can also seem constricting. That’s why this week i want to take a look at some more innovative ways of interpreting the Agile board. Hopefully giving you…

When introducing any sort of an organizational change, it is normal to face fear, distrust and even anger. Agile is no different and we tend to have specific reactions to hearing the news of it coming into our processes. In fact, the reactions are so specific, they can actually be named. Thus this week i break down the 5 most common reactions to taking on an Agile transformation. Take a break and have some fun…

Today project management community is buzzing about Agile. Since its move from small developer groups into the large corporate field, everyone seems to want a piece. And really I am not one to blame them. Agile has proved to improve productivity, make processes more efficient and have an outcome that is more likely to be what your client wanted in the first place. Having this in mind and with the new applications allowing to scale…

In the growing popularity of Agile, there have been numerous attempts to scale the practice and make it fit the large company structure. SoS, LeSS, SAFe, DAD and many more attempts to modify Scrum, Kanban and other methods. However, when doing so it becomes easy to lose their essence. Thus coming up with practices that carry only some of the original points and benefits. The question is – should we actually be scaling Agile up?…

Making an Agile transition is a full on organizational change. Workflows, processes and even team roles need to be adjusted. However, all of it can be tricky as well. Understanding the key roles of Scrum often has a direct effect on the methodology succeeding or failing. And one of the most common misconceptions is that the Project manager and the Scrum master roles are pretty much the same.

Coming from the traditional project management point of view it could seem simple. You have a team in both cases, then a project manager to oversee the team which is renamed into Scrum master and then you have the senior management which in this case is the Product Owner. Seems right? Well, it isn’t.

Agile-habits

We are all creatures of habit. Taking the same road to work, drinking our morning coffee and mostly having a time proven routine for anything and everything we do. However as there are good habits, there are also bad ones that can put us at a disadvantage in the long run. 

Agile or work environment is no different and you can fall into practices that seem fine, but actually are hurting you instead. What are they? Have you become a victim? Here are our top 8 bad Agile habits.

#1 No backlog refinement

Eylean - Efficient Visual Task Management SoftwareDownload for Free