Hello, For over two decades now, proponents of Agile have had to contend with the myth that “you can’t use Agile for X,” where X represents high-assurance systems, systems subject to rigorous regulatory requirements, cyber-physical systems, systems with known and fixed requirements, systems for national defense and security, big data systems, and so on. I’ve been around long enough to have a sense of why these perceptions arise, so I always respond by simplifying Agile.
Video nine in our series designed to jump-start your understanding of the core principles and practices of Agile software engineering (ASE) is all about code quality. Ken Pugh, one of our Lean-Agile thought leaders, shares wisdom about what makes good code and how to avoid some common pitfalls. The goal is maintainability—the ease with which you can go from the as-is to the to-be state. So, what makes for easily maintainable code? Ken talks about.
Hi all, At Scaled Agile, we’ve experienced firsthand the benefits of creating a physical working environment that supports Agile practices, and many of you have shared similar experiences with us. Our new advanced topic article on Agile Workspaces (located on the SAFe 5.0 Preview site) brings together these learnings and provides recommendations for creating spaces where Agile teams, ARTs, and innovation can flourish—including considerations for remote working. We’ve also seen many organizations effectively use workspaces.
As one of our core competencies, Lean-Agile Leadership describes the mindset and behaviors that can guide organizations down the path to business agility and better outcomes. For the past four years, I’ve been a presenter at the DevOps Enterprise Summit, educating attendees about one specific set of leader behaviors known as transformational leadership. Each year at the end of my talk, I would explain how these leadership traits are teachable and that organizations can adopt.
Hello folks: The upcoming release of SAFe 5.0 and the recent updates to the Lean Portfolio Management (LPM) class have advanced our thinking around establishing and documenting the Portfolio Vision, which is a new artifact in V5.0. Since we are supporting the current version (4.6) of SAFe for another year, we thought it would be helpful to update the portfolio canvas and guidance in 4.6 to reflect our latest thinking. To that end, we’ve just.
Welcome to video eight in our series designed to jump-start your understanding of the core principles and practices of Agile Software Engineering (ASE). In this vlog, Ken Pugh, one of our Lean-Agile thought leaders, talks about effective communication with models. Models create common understanding and alignment on what a system will do, primarily by providing a common vocabulary, overall architecture, and domain terminology. In this video, Ken introduces two kinds of models (static models and.
Since we announced the SAFe 5.0 preview at the Global SAFe® Summit, a lot of people have asked us for a presentation outlining what the new version is all about and the changes from version 4.6 to 5.0. Well, we heard you and we’re excited to announce that our What’s New in SAFe 5.0 presentation is now available to download. Use the deck to inform yourself, your organization, colleagues, and customers about the newest version of.
Enabling technical agility in the Lean enterprise vlog series: creating a shared understanding with Behavior-Driven Development
Welcome back to our video series designed to jump-start your understanding of the core principles and practices of Agile software engineering. In this seventh installment, Lean-Agile thought leader Ken Pugh tackles the question of how to create a shared understanding of code behavior. Customers, developers, and testers think about behavior from multiple perspectives. So, how can you avoid problems that arise when people in this triad of roles think about behavior differently? Behavior-Driven Development (BDD).
Hello Folks, On behalf of the entire Scaled Agile team and the SAFe Contributors, we are delighted to announce a preview of SAFe® 5.0 for Lean Enterprises. Why is this update important? Globalization, fast-moving markets, disruption, the unprecedented pace of technological innovation. Organizations know that they need to transform—now—to compete. But their existing business models, organizational hierarchy, and technology infrastructure simply can’t keep up with how quickly the company needs to adapt. Agile product delivery isn’t enough. You need business agility..
Now for video six in our series designed to jump-start your understanding of the core practices and principles of Agile software engineering (ASE). Here, one of our Lean-Agile thought leaders, Ken Pugh, talks about discovering story details with scenarios. A scenario defines a system behavior from an external point of view. A story, a short description of a small piece of desired functionality, can have many scenarios. Watch as Ken breaks a story down into.