For Martin Seibert’s newest book – We Run on Agile – he had the opportunity to speak with Richard Wilson. With over 20 years of implementing Agile at scale, Richard co-founded the company with Mark Richards – a SAFe fellow who probably has launched between 30-50 trains over the last 10 years.
The journey of SAFe implementation for your business can seem daunting. Knowing where to start and then actually using the tools may seem like a process fraught with complexity. But it doesn’t have to be because we’ve got you covered! Today we’re starting our SAFe Implementation Roadmap series in which we will take a look at each of the 12 steps in the SAFe Implementation Roadmap.
SAFe helps businesses enable their agile practices at scale. But what does scaling involve and how can you improve your business agility with SAFe? Read on to learn about the seven core competencies of Lean Enterprise to get you on the right track.
When companies are looking into implementing SAFe, more often than not, they are faced with SAFe resistance from within. To make the initial process as painless as possible for your organization, we’ve put together a plan to help you tackle SAFe resistance within your company.
To successfully drive your organizational change, you need to have a team. At first, this team might be external consultants, but over the long term, this will be your “Lean-Agile Change Agents.” This is the team that will provide the knowledge and engine to power your change. It is important that, organization-wide, everyone knows who the Lean-Agile Change Agents are to use this team as a resource when implementing SAFe and continue to use them as a resource after implementation.
While SAFe is a great starting point to kick off your agile journey, it can be quite complicated to find your way through at the beginning. Anyone getting familiar with SAFe® processes for the first time might feel overwhelmed by the abundance of terms and components. In practice, all these elements should fit together and mesh to ensure an optimal process. Today we’re talking all about Essential SAFe and its benefits.
How should you approach a SAFe implementation as a company? Who should be on the team? The software engineering industry …
Why do organizations use SAFe? Ultimately for the same reasons that they introduced Scrum at the team level: to increase productivity, improve product quality, shorter, market-oriented release intervals, a higher customer focus, and higher employee satisfaction. Only on a much larger scale.
There are several models that can help organizations tackle scaling in an effective and structured way. One of the most well-known and proven approaches is the Scaled Agile Framework: SAFe.
The larger the company, the more complex and multifaceted its structure becomes. Thanks to software solutions such as Scrum or Kanban, we can now scale planning and management processes, but they no longer cut it if you want to implement a comprehensive approach for all of your teams. Introducing: Agile Hive, our own SAFe with Atlassian tools, which made us a certified Scaled Agile Platform Partner and was developed together with our partner, KEGON.