Hi all. As you know, the DevSecOps mindset, culture, and technical practices are critical for business agility and overall organizational success. SAFe provides guidance to organize around value, improve quality, build a continuous delivery pipeline, and reduce lead time. Now Peter Vollmer, SAFe SPCT and Distinguished Technologist at Micro Focus, has provided a new advanced topic article with deep, practical advice on how to succeed with your DevOps implementation at enterprise scale with a ‘software.

Hi folks. As you all know, Agile principles and practices originated in software decades ago. And as software teams began to see success with these practices, others within their organization, including hardware teams, took notice and started applying them in their specific context. Cindy VanEpps (SAFe SPCT) and the rest of the team at 321 Gang have spent many years with organizations in aerospace, defense, automotive, medical devices, and others helping them apply Lean-Agile practices.

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.

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.

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.

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).