Join the Discussion

Related learning

Provide Feedback

The Lean-Agile Framework reflects Net Objectives’ experience of what companies must do to deliver value effectively. We believe the aim is business agility – having the ability to realize value quickly with high quality, predictability and sustainability. The framework is based on our distillation of the laws of Lean-Agile Software Development. It represents an evolving understanding in how both software development and IT organizations work and how they should be driven by and be integrated with business. It is based on an integration of the Lean and Agile mindset with proven practices that we have consistently found to enhance effectiveness of an organizations’ efforts.

The Lean-Agile Framework was created and continues to evolve by attending to what works and what doesn’t work. This scientific approach is in stark contrast to the common approach of defining a set of values and practices that one sticks to until the desired results are achieved. Instead the Lean-Agile Framework provides a method for organizations to transform themselves while they learn better methods to realize value. The Lean-Agile Framework can be used as a context for implementing existing methods in order to extend the learning that has already taken place.

The picture illustrates the overall value stream / flow of work from vision conceptualization to vision realization and the roles and practices involved at each level of this value stream. The resources on the portal fit within this overall framework.

Levels and roles

Roles Library

The Topic Landing Page for roles. The delivery of value involves the effort of people from all across the value stream: executive, management, and front line teams. People from the Business and technology work together to discover and deliver work that customers can use and can realize value from it. Lean-Agile groups roles into three levels: Portfolio, Product, and Team. The portal offers Learning Paths to guide you through the critical roles of Lean-Agile.

Portfolio Level

The Topic Landing Page for the Portfolio Level which includes a diverse group of stakeholders working across organizational boundaries. The Portfolio Level is responsible for priority, the order of work, and deciding what is active. Roles involved in the Portfolio Level include the Value Stream Owners and the sponsors. The Business engages with the technology organization at the Portfolio Level.

Program Level

The Topic Landing Page for the Program Level which is the center of responsibility that is focused on an application area. Work is comprised of releases, enhancements, production support, and maintenance requests. This level also is responsible for program ecosystem and operational metrics.

Team Level

The Topic Landing Page for the Team Level which is composed of development teams and shared services. Each development team is composed of the developers, testers, analysts and SMEs required to produce and implement a Business value increment, for quality assurance, and continuous incremental improvement. A team's work is composed of the stories and tasks for a specific release, enhancements, production support, and maintenance requests.


Disciplines and Practices Library

The Page for Disciplines and Practices. Lean-Agile looks across multiple software methods to discern fit to purpose and to apply practices thoughtfully. It does not insist on purely following one approach when that means being limited in using good practices from others. This page describes core practices, the practices involved in decomposing requirements, and meetings and checklists.


The Topic Landing Page for Leanban. Leanban is a team-level offering that makes higher level Lean-Agile tenets actionable on a day-by-day basis. Leanban helps Agile teams select and use Agile approaches that best fit their situation and needs. It uses Lean principles to guide them. Leanban is focused at the team level.

Acceptance Test-Driven Development

Acceptance Test-Driven Development (ATDD) defines acceptance tests for requirements prior to implementing those requirements. The acceptance tests represent the specific details of the capability that will be delivered. Defining these tests up-front gives a high confidence that the system will meet the expectations of the customer.


What Design Method Will Be Used?

Team Level (Technical) Supportive Inflection Point: Design can be done in many different ways. What should we migrate to?

DevOps Library

The Topic Landing Page for DevOps. DevOps can be a distributed set of practices, or be collected into a role. “DevOps” is a software development method that emphasizes communication, collaboration (information sharing and web service usage), integration, automation, and measurement of cooperation between software developers and other IT professionals. The method acknowledges the interdependence of software development, quality assurance, and IT operations, and aims to help an organization rapidly produce software products and services and to improve operations performance.

Emergent Design

For software to consistently deliver promised results, software development must mature into a true profession. Emergent Design: The Evolutionary Nature of Professional Software Development points the way. As software continues to evolve and mature, software development processes become more complicated, relying on a variety of methodologies and approaches. This book illuminates the path to building the next generation of software. Scott L. Bain integrates the best of today’s most important development disciplines into a unified, streamlined, realistic, and fully actionable approach to developing software. Drawing on patterns, refactoring, and test-driven development, Bain offers a blueprint for moving efficiently through the entire software life-cycle, smoothly managing change, and consistently delivering systems that are robust, reliable, and cost-effective.


Inflection Point System

Leading transformations with Inflection Points provides guidance for a lower-risk, simpler path to realizing organizational transformation. Businesses routinely ask their software and service organizations to produce more for less, and more predictably. People tasked to lead these efforts find themselves in a challenging position. The first challenge is identifying the best way to do it. The second is getting people to change to the chosen way. The Inflection Point system offers a step-by-step approach for an organization to move from its current reality towards increasing performance and satisfaction, with a reasonable certainty of success and minimized stress on leaders and workers.


The Guardrails for creating business agility (the quick realization of business value predictably, sustainably and with high quality) are a set of agreements different roles in the organization make with each other to facilitate working together. The guardrail system helps people in an organization work together towards their common goals. They also provide a series of questions that people can use to ensure they are keeping their agreements.