All posts by : Harry Koehnemann
Hi folks. I wanted to inform everyone that we have just released new Big Picture Glossary functionality with integrated translations. While the Glossary terms themselves have not changed, we now have better translations created by native language translators with SAFe experience. All new translations are on the site except German, which should be up in a few months. We also changed the way we manage glossary items and their translations. Formerly, users would download a.
Many organizations applying SAFe build large systems that include hardware. Yet there is little guidance on how DevOps’ software-centric practices can be used by the people who build significant cyber-physical systems, those containing computers, mechanical devices, electronics, optics, fluidics, motors, propulsion, and more. I wanted to update everyone on two activities underway that are helping to address this need. The first is the Industrial DevOps work going on at IT Revolutions within their DevOps Enterprise.
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.
Enabling technical agility in the Lean enterprise vlog series: the rest of the Agile software engineering story
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.
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.
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.