Andrew Michael Miller's Thought Backlog
Writer and working Agile professional. Author of Pancho's Fall.
SAFe, or Scaled Agile Framework, is a popular method for managing large, complex projects. It is designed to help organizations implement agile practices at scale, and it provides a structure for organizing and coordinating work across multiple teams. To be successful with SAFe as an organization, it is essential to have a deep understanding of flow metrics and WSJF (Weighted Shortest Job First).
Scrum, the popular Agile framework widely used in software development, follows a life cycle that is by nature satisfying to work through because of its structure. If you're wondering why it's more satisfying than other pure frameworks for project management, it's because you have been trained from childhood to love a good story. The Sprint cycle, the time-boxed period during which the team works to deliver a potentially releasable product increment, follows a similar structure to one of the most satisfying literary frameworks - the hero's journey.
Scaled Agile Framework (SAFe) is a popular framework for managing and coordinating large-scale software development projects. It is designed to help organizations implement Agile methodologies at an enterprise level, enabling them to improve collaboration, speed up delivery, and increase productivity. However, like any framework, SAFe has its strengths and weaknesses that need to be considered before implementing it. Strengths of SAFe One of the strengths of SAFe is its scalability. The framework is designed to be adaptable to different organizational structures, sizes, and industry sectors. This means that it can be used by small and large organizations alike, and can be tailored to suit the specific needs of each organization. This flexibility makes it a great option for organizations looking… Continue reading Strengths and Weaknesses of SAFe – Scaled Agile Framework
I know what you're thinking. It's almost the new year and that means it's almost the beginning of a new 365 day sprint in your life. We often think of New Years Resolutions for our personal lives, but what about at work? Along with setting those goals for yourself for the new year, why not also resolve to help take your Scrum team to the next level?
With how widespread Scrum is today, it's hard to believe that the first Scrum Guide was only published in 2010. Not only that, but the Agile Manifesto itself was only signed in 2001. With practices this new, there are bound to be hiccups along the way. Let's take a brief look at three controversial terms that are associated with Scrum - one icky term that was in the guide at one point, one unintentionally insensitive term used unofficially by many teams, and one term that I predict will one day be the focus of additional controversy.