Introduction
Although value stream is a Lean Six Sigma concept, value stream thinking is gaining traction in Agile organisations as more organisations seek ways to accelerate delivery, reduce waste, and focus on customer outcomes. From the Agile perspective, an important question is asked by project management practitioners: does value stream thinking make sense in organizations structured around projects? Many professionals, especially those in traditional project environments, wonder how to apply value stream concepts when teams remain siloed by function, phase, or expertise. This post explores the relevance of value streams in project-oriented organisations, common challenges, some practical recommendations, and why this perspective is transforming how organisations deliver value.
Challenges
Organizational Structure and Siloes
A common challenge is that many organizations are still structured around projects, with teams grouped by function (such as engineering, sales, or marketing) or by delivery phase (broker, build, test). This can make it difficult to visualize the end-to-end flow of value. Ron Jeffries, one of the authors of Extreme Programming, the framework that dominated Agile software delivery before the publication of the Manifesto for Agile Software Development, noted that “functional silos create local optimizations but often at the expense of the overall system.” The PMI Code of Ethics and Professional Conduct mandate responsibility and respect, yet traditional structures sometimes hinder the collaboration needed for holistic improvement.
Identifying Value Streams
Project teams want to know how value streams are defined and identified in a project-driven organization. When teams are organized by function, it’s harder to see how value moves from idea or request to customer. Value stream mapping will reveal how work really flows across departments, phases, and handoffs regardless of org chart boundaries. Mapping value streams exposes the real pathways and interactions that drive (or block) customer outcomes.
Project Versus Value Stream: Replacement or Complement?
Some project managers are concerned that value streams may replace projects. Practitioners know that projects and value streams can coexist. Projects may still be the vehicle for major initiatives, but value streams provide a better lens for improving flow and customer focus. Value streams help organizations see work as a continuum rather than a series of disconnected efforts.
Shared Services and Bottlenecks
Project environments often rely on shared services (like finance, HR, IT, procurement, or governance and compliance) that serve multiple teams. These shared services frequently become bottlenecks, creating queues, handoffs, and delays. Value stream mapping is especially useful here, making visible the queues, rework, approval delays, and hidden waits that sap productivity and morale. In Agile, cross-functional visibility is critical for addressing systemic delays.
PMO Engagement and Metrics
Traditionally, PMOs are focused on schedule, scope, and budget tracking. In a value stream context, their role shifts toward supporting cross-functional coordination, removing roadblocks, and reporting on outcomes rather than just timelines. Measuring value stream performance is also a shift: instead of just tracking milestones, organizations monitor lead time, flow efficiency, customer impact, and quality trends.
Organizational Resistance
Functional leaders may resist value stream thinking, fearing a loss of control or relevance. Resistance to change is natural, especially when value stream mapping exposes inefficiencies or challenges the status quo. The PMI Code of Ethics encourages fairness and honesty, and these values can guide conversations as organizations navigate change.
Recommendations
Start with One Value Stream
Don’t try to boil the ocean. Begin by mapping one high-impact value stream, ideally one that cuts across multiple functions and has clear relevance to business outcomes. Use data from this stream to demonstrate benefits and build momentum for broader change.
Involve Cross-Functional Teams
Involve representatives from all functions in the value stream mapping process. This promotes shared understanding and surfaces issues that may be invisible within silos. The best insights come when everyone can see the whole system.
Use Data to Drive Conversations
Collect data on lead times, handoffs, rework rates, and customer impact. Use this information to focus improvement efforts and make the case for change. Objective data helps depersonalize challenges and builds a culture of continuous improvement.
Redefine the PMO’s Role
Encourage the PMO to shift from schedule policing to facilitating flow and outcome tracking. Support PMOs in adopting new metrics like flow efficiency and customer satisfaction, and in championing cross-functional collaboration.
Address Shared Services Proactively
Bring shared services into the value stream mapping process. Identify recurring bottlenecks and collaborate on solutions. Consider service-level agreements that align with value stream goals rather than just functional targets.
Communicate the Why
Clearly communicate why value stream thinking matters, to leadership, teams, and stakeholders. Link improvements to business goals, customer satisfaction, and professional ethics as outlined by PMI: “We make decisions and take actions based on the best interests of society, public safety, and the environment.”
Leverage Success Stories
Share early successes and lessons learned from initial value stream mapping efforts. Use these stories to inspire others and reduce resistance.
The Bottom Line
Value stream thinking doesn’t require abandoning projects; instead, it gives project-heavy organizations a powerful lens to see systemic waste, improve end-to-end delivery, and focus on what truly matters: delivering value to customers. By making work visible, encouraging cross-functional collaboration, and shifting metrics toward outcomes, organizations can break through traditional barriers and thrive in today’s fast-paced environment. As the PMI Code of Ethics reminds us, our responsibility is to act in the best interests of our stakeholders, and value stream thinking is a key enabler.
Questions for Readers
·What challenges have you faced in mapping value streams in a project-based environment?
·How has your PMO adapted (or resisted) value stream thinking?
·What metrics have you found most useful for tracking value stream performance?
