Author Archives: clalar

In the previous posts we have been talking about how to work in an agile way with software development and implementations, and this is natural since the Agile framework was developed for digital projects. However, there are huge benefits of introducing Agile methodologies also to administrative and operational teams. In this post I will shareContinue reading “Part 9: Agile for non-tech teams”

As mentioned in previous posts in this series, Agile teams should have a high level of autonomy. This autonomy has in some cases gone so far, that it has become impossible to steer the efforts in a good way. This happens because the teams have the impression that no one except the team members canContinue reading “Part 8: Autonomy and Alignment”

In the previous posts in this series we have been looking at problems with the traditional project methodology (Waterfall), looked at how to organize your company for best results in digital projects and given tools to in practice work agile. What we have not discussed, is the role leads have in Agile organizations, and howContinue reading “Part 7: Leadership and Feedback Culture”

In the last post in this series, we looked at some of the tools and rituals used when working agile, and I mentioned Road-Maps as a way to visualize the progress and development of a digital product. In this post I will dig deeper into the Road-Maps and how they are used As described inContinue reading “Part 6: How to set a course and visualize your progress”

In the previous chapters (found here) we have touched upon the false security in the most commonly used project methodology among traditional companies, a way of thinking that focuses on the benefits of a digitalization project, how you should organize your company for successful execution of your digitalization initiatives and why system owners are normallyContinue reading “Part 5: The Agile Toolbox 101”

In the last post we discussed why the stakeholders should not run their own digitalization projects, and why we need Digital Product Owners to do it instead. In this post we go a step further and will discuss why the way traditional companies divide the responsibility regarding digital investments is inefficient. This ties neatly intoContinue reading “Part 4: Why Product Owners aren’t System Owners, and some about eco-system-thinking”

This is the third post in my series about Agility for traditional companies. In the other two we discussed a) what waterfall projects often fail to deliver, and b) a mind-frame for how to think when implementing software. In this post we will discuss why the structure of working of traditional companies often gives poorContinue reading “Part 3: Why the stakeholders should not run their digital projects”

This is the second post in a series, aimed to give some Do-It-Yourself tips and guidance to traditional companies, when they want to go in a more agile direction. Since agile is not a rule book, but more of a mindset and framework, the order of the posts may seem a bit irrational, but thereContinue reading “Part 2: How to think when developing software or implementing an Off-The-Shelf system”

Since this is supposed to be an introduction to Agile methods for more “old fashioned” or traditionally minded companies, we need to start from the beginning.  Therefore, let’s first look at benefits and flaws in the most commonly used project methodology for this kind of companies; the Waterfall Model. Please note that there certainly areContinue reading “Part 1: The false security of Waterfall Projects”