Category Archives for : SAFe Resources
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.
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.
Here is the fifth video in our series designed to jump-start your understanding of the core practices and principles of Agile Software Engineering (ASE). In this installment, Lean-Agile thought leader Ken Pugh talks about the significant advantages of an ‘always-think-testing’ approach. By thinking about testing early in the development process (‘shifting testing left’), we can avoid the exponentially higher costs of finding defects late in the timeline from requirements definition to production. Shifting testing left.
Here’s video four in our series designed to jump-start your understanding of the core principles and practices of Agile Software Engineering (ASE). In this video, Ken Pugh, one of Lean-Agile thought leaders, talks about the principle of ‘testability.’ Testability is a key quality attribute of code. We want tests that are fast, repeatable, and that can be automated. To design the right tests, we need to consider context of the system (state) and identify the.
Video number three in our series designed to jump-start your understanding of the core practices and principles of Agile software engineering (ASE) is live—and all about flow. Flow is how we deliver value to the customer, and in the video, Lean-Agile thought leader Ken Pugh discusses how to accelerate flow in the Value Stream. The flow in delivering a feature to a customer involves several phases—decide to deliver the feature, analyze the feature’s requirements, design,.
Great news! We’ve launched the second video in our series designed to jump-start your understanding of the core practices and principles of Agile software engineering (ASE). Lean-Agile thought leader Ken Pugh discusses why and how to build in quality from the start. Namely, how to build the right thing and build the thing right using a test-first approach. Ken describes the two important concepts behind building the right thing. The first is the minimum marketable.
Gone are the days when companies had the luxury of long delivery cycles to get everything right. Now, organizations have to predictably and quickly get new functionality in customers’ hands, or risk not being able to adapt to changing markets. This is true for all businesses, including those building the world’s biggest and most complex systems. And they’re turning to Lean systems Engineering practices to take advantage of frequent product release cycles that provide fast.
Hello, When we recently announced SAFe® 4.6, we introduced the Five Core Competencies of the Lean Enterprise. These are: Lean-Agile Leadership Team and Technical Agility DevOps and Release on Demand Business Solutions and Lean Systems Engineering Lean Portfolio Management These competencies describe the knowledge, skills, and mindset that enable an organization to operate in a truly Lean fashion and better navigate the complex challenges of digital disruption. You can read about each competency in more.
We’re very excited to announce a new SAFe for Government page on this website! When we released SAFe 4.6, we recognized that state, federal, and international government agencies have unique and specific challenges to Lean-Agile adoption that warranted the special government guidance we included in the 4.6 knowledge base. We have since enhanced that guidance substantially in our SAFe® for Government course. But we wanted to do more. In the course, we cite many great references.
Global markets and customer needs shift in the blink of an eye. Digital disruptors are invading your market. To survive, your organization must quickly innovate to get high-quality solutions into customers’ hands faster and more predictably. Maybe you’re headed toward those goals by adopting SAFe®, and maybe you have buy-in from leadership to embark on a SAFe journey. But if your architects aren’t on board, the business can’t execute on its vision and objectives. Architects.