Hello, As you know, Built-in Quality is one of SAFe’s four core values. Without it, ‘scaling Agile’ by any means is a house of cards with no true agile foundation that will fall the first time users put weight on our big, new, important system. That’s why SAFe provides significant guidance around the current and evolving technical software engineering practices. One element of that is Ken Pugh’s Video Blog series on Agile Software Engineering.  In.

Hello Folks, While it was a bit behind the scenes in SAFe 5.0, (you had to click to see it!) we added the Objective and Key Result (OKR) technique to Strategic Themes as a way to add some more specificity to the connection between enterprise strategy and portfolio vision. I’m a fan of OKRs because “the more alignment you have the more autonomy you can grant” (Stephen Bungay). But up to now, our treatment of.

Hi Folks, As we are all aware, the recent outbreak of the coronavirus (COVID-19) is affecting many people around the world. In order to contain the spread of the virus, many governments and some enterprises have started putting policies in place to restrict travel in order to limit exposure. These restrictions can be challenging for Agile teams and ARTs who, as stated in the Agile principles, greatly value face-to-face communication. In SAFe we embrace and.

Those of you who have been with us for awhile know that the launch of SAFe 5.0 represented a significant evolution in thinking when it expanded its focus to enabling full business agility. The imperative was clear. It was time to go beyond IT to align the entire enterprise on strategy and execution; to empower companies to undertake company-wide initiatives that are critical for the company’s future. Of course, we need our business partners to .

In this, the age of digital, it’s abundantly clear that business survival is highly dependent on the IT organization’s ability to evolve technological infrastructure to keep pace with the rapidly changing demands on the business. After all, seemingly all new business capabilities are dependent on new initiatives that are realized by digital systems and services. Simply, there can be no true business agility without an adaptive enterprise architecture. This is why we are so excited to.

Welcome back! In this final video in our series designed to jump-start your understanding of the core principles and practices of Agile software engineering (ASE), one of our Lean-Agile thought leaders, Ken Pugh, wraps up with some additional key concepts: Systems thinking—the big-picture view Kinds of testing  Continuous testing pipeline Separation of concerns Common design patterns  Methods for refactoring code Click on a topic below to check out any of the earlier videos in the.

Hi Folks, It probably goes without saying that the release of SAFe 5.0 was a pretty big deal. Expanding from technical agility to Business Agility was no small feat. It required the addition of new competencies for Organizational Agility and Continuous Learning Culture. All the competency articles were either written from scratch or largely rewritten and ‘mob reviewed’ by the entire Framework team. 30 – 40 other articles were written, rewritten, or extensively edited. 80.

Good news! Here’s video 11 in our series designed to jump-start your understanding of the core principles and practices of Agile Software Engineering (ASE). In this installment, one of our Lean-Agile thought leaders, Ken Pugh, talks about test-driven design. As we learned in video seven, Behavior-Driven Development (BDD) is about the triad of customer, developer, and tester writing story tests from a point of view external to the application. Test-Driven Development (TDD) is about figuring.

We’re back with video 10 in our series designed to jump-start your understanding of the core principles and practices of Agile software engineering (ASE). This time, one of our Lean-Agile thought leaders, Ken Pugh, talks about aspects of design quality that are critical for maintainability. Ken introduces Interface-Oriented Design by discussing one of the most important guiding principles—design to interfaces not implementations—from Design Patterns by Gamma et al. Next, he draws from another classic book.