It's All About the People: Resolving Agile Delivery Uncertainties Through People Interactions by Ruxandra Dariescu
15:102022
Calling people capacity is quietly sinking your agile delivery
About 35% of tech projects fail, as the speaker cited, and every reason on her list comes back to people. Business agility coach Ruxandra Dariescu, with over 25 years in tech, argues that the words teams use, from resources to commitment, carry private meanings that breed uncertainty in every sprint. So what changes when a team swaps the delivery plan for a shared delivery purpose?
Learn to reframe delivery language around purpose, competence and value to cut uncertainty
Ruxandra Dariescu argues that agile project delivery fails mainly because of people interactions, and that those interactions are shaped by the language teams use. She proposes replacing the old vocabulary of capacity, budget and fixed timelines with one built on purpose, competence and value, so teams can align on why they deliver and reduce uncertainty.
“But what's the most important thing is that no word in any language spoken on this planet has a power on its own. We assign the power to words.”
“When that rhythm is established, you have a fluid delivery. When you are outside that rhythm, you don't have a pulse, you have a heart attack.”
What you will learn
Spot project delivery language, such as capacity, FTEs and fixed timelines, that treats people as resources.
Reframe delivery around customer needs, project purpose and value to market rather than time to market.
Recognize how a single word like commitment carries different personal and emotional meanings across a team.
Align a team on a shared delivery purpose before discussing the delivery plan.
Set objectives and processes that fit the project's scope and working cadence, such as two-week sprints.
Details
Level
Intermediate
Format
Talk
Technical depth
Non-technical
For
Mid-career, People manager
Length
15:10
Published
June 2022
Questions this talk answers
Why do so many tech projects fail?
Dariescu finds that the common reasons, from weak executive support to failed collaboration, all come back to people and how they interact.
What is wrong with traditional project delivery language?
It treats people as capacity or FTEs, budget as cost and timelines as fixed, a linear flow that ignores how people actually work together.
Why do words matter so much in team interactions?
Every word carries the personal context, emotions and culture in which it was learned, so the same word, such as commitment, can mean different things to each team member.
How can a team reduce delivery uncertainty?
By aligning on a common purpose, setting clear and meaningful objectives, tailoring processes to the project and recognizing people as competence and value, not resources.
Is DevOps the same as agile?
No. Dariescu describes agile as a methodology and way of thinking, while DevOps is a function.
Ruxandra Dariescu: So I'm Ruxandra Dariescu, and I apologize for a slight delay in my presentation today. I'm a business agility coach, consultant, mentor, speaker, and author. I have over 25 years of experience in the tech world, creating products, platforms, transforming organizations, and coaching people. And this is my passion. And as a result of my work in the tech world, I'm a business coach, consultant, mentor, and author.
Ruxandra Dariescu: Not long ago, I published a book about agile teams and their ability to deliver sustainable projects. Why is this important? And why is it so close to my heart? It's because Ruxandra Dariescu: about 35% of the projects in the tech world are failing. And I look for the reasons why they fail. And some of the reasons I listed here about, you know, executive failure to support the people, Ruxandra Dariescu: disconnected individual objectives, we are agile, it's a talent gap, it's an individual competence need, fail people collaboration. So all these things have in common the idea of Ruxandra Dariescu: people. So clearly, there must be something there around the people that impacts the ability to deliver. And that is about people interaction, as I found.
Ruxandra Dariescu: So in the people interaction is actually governed by the way we talk to each other and we talk through language. Ruxandra Dariescu: So if there is a deep need for us to refresh the language, the narratives we tell ourselves about what makes up a project and how we can eliminate the uncertainty when we look at delivering with a focus on the people.
Ruxandra Dariescu: So for me, it's very, it's a very clear statement, we need to redefine the language and reposition it for the purpose. In an old world of project delivery. Ruxandra Dariescu: People are associated to capacity or resources and the focus is on objectives on budget scope timeline as we do a classical project plan that's not dismissed, but in my new world.
Ruxandra Dariescu: The project it's one dimension that delivery. It's a, it's a form of organizing a purpose and that is supported by processes that are appropriate for the scope of the project, not generic ones that are available. Ruxandra Dariescu: In an organization, but specifically tailored to the scope of the project and then Ruxandra Dariescu: It's a circular flow here between the project, the process and the people to actually meet the purpose.
Ruxandra Dariescu: So the language you learn about project delivery belongs in the past, I strongly believe that and it's about focusing on input as a project objective focusing on budget as a cost. Ruxandra Dariescu: Focusing on capacity rather than people where we put their FTEs, we do we have predefined work. Ruxandra Dariescu: We hold hold information. A timeline talks about fixed timeframes in a world that talks about agility and agile.
Ruxandra Dariescu: And we look at risk management focusing on a budget or capacity or scope and the objective there is to have a shareholder profit or value association. Ruxandra Dariescu: Now, this is a linear flow of information from the business to its operations and to its capacity. Ruxandra Dariescu: What I am stating is that all these information flows are connecting people through the language they use to create a project and language is made of words.
Ruxandra Dariescu: Now, it's a cultural construct when you look at the words and every word or combination of words we use carries with it an individual experience. It's very personal. Ruxandra Dariescu: We pick up words in a linear way. And that's how we make sentences and how you understand me today. And we look at the word itself as the beginning of the experience, not the end of it.
Ruxandra Dariescu: But what's the most important thing is that no word in any language spoken on this planet has a power on its own. We assign the power to words. Ruxandra Dariescu: So we free free free frame the structure of how we look at the language you use in project delivery. Ruxandra Dariescu: We look at customer needs and purpose to create value, we look at the project purpose that drives the commitment for an output, we look at what creates the people value for competence for the roles that are just a temporary identity part of that specific project.
Ruxandra Dariescu: We should look at the people being adaptive learners. We should look at collaborating for solutions and transparently sharing information. Ruxandra Dariescu: We look at the processes for their operational efficiencies, not as blockers or stoppers of our flow of of working together. Ruxandra Dariescu: And from those processes, we derive the risk management, one of the risks being the people risk. We create value to market, not time to market nothing. We create value to market.
Ruxandra Dariescu: And we have a bunch of stakeholders for which we deliver value as people working in a team to deliver for our interaction. We are actually a stakeholder group. Ruxandra Dariescu: That creates value while one of the stakeholders is the shareholder who takes the profit. Ruxandra Dariescu: Now, if we are looking at the words we use, there is it's important to remember that words have flavors and those flavors can be elevating and positive or could be deprecating and negative.
Ruxandra Dariescu: If I take a very simple example of the daily stand up meetings that we are running in our under agile methodologies, we can use positive words, I completed my task or you could use negative words like I feel under control all the time. Ruxandra Dariescu: We can use elevating words like I learned to run demos or deprecating words like I wasted my time in this daily stand up meeting.
Ruxandra Dariescu: So if words have flavors, then I think it's important to understand that those flavor are giving the power to the words they and that power can really push us into breakdowns or into breakthroughs. Ruxandra Dariescu: Now, how are the words unfolding when people interact is very simple, every single word we use actually carries the power of the moment we have learned the word with a definition part of our specialization.
Ruxandra Dariescu: The same word can mean different things in different industries is the context in which we use learned or apply the word the emotions associated with that the environment and the culture. Ruxandra Dariescu: So these are the the way we are looking at the words representing a complete combination and we usually just refer it or express it for one one single statement.
Ruxandra Dariescu: Now, I would like to take the word commitment of one person and go through a little example of how we think about commitment when we interact to deliver something together and how we feel about commitment when we interact to deliver something together. Ruxardia Dariescu: And it's a very simple story, the thinking thing is very, very, very, very simple is the logical part of our mind that is linear and believes it has the answers to everything.
Ruxandra Dariescu: Now, how we feel about the word commitment is a slightly different story, because that feeling when we use the word commitment, it's really dependent on that specific moment of that specific interaction. Ruxardia Dariescu: Not yesterday, not last year, not next month, not in an hour's time, it is in that moment, and that is an entangled network of emotions.
Ruxardia Dariescu: The interesting thing about our emotions is that we describe them through the words we refer to as feelings. Ruxardia Dariescu: And only in the English language, there are over 3000 words that are describing feelings. So you can see when we look at the word as simple as commitment in a linear way, we believe it's logical and we can go to the dictionary and take up a definition of an association of words.
Ruxardia Dariescu: And we think that it is, but how we feel about it. It's a different story. Now, putting context of a feeling what's happening in a team interaction. So each one of the dimensions here I was trying to represent for the green lights, it's one person and they are feeling Ruxardia Dariescu: About the word commitment, make a team of 20 people make a team of five people or a team of two, you may end up with straight lines, or you may end up with a network of lines around the word commitment.
Ruxardia Dariescu: That express how we feel in that specific moment. Now the words we used to talk about our individual narrative, the story of how we understand the commitment generates an interaction efficiency niche. Ruxardia Dariescu: If we manage to get in sync, we are efficient. Interacting outside the niche adds levels of uncertainty in people interactions. And there is a beautiful study by a university in Japan.
Ruxardia Dariescu: That actually identify that people focused on purpose at the same time in the same moment, create brain coherence. So they work well together to deliver. Ruxardia Dariescu: But for that to happen, we have to flip the question from what is the delivery plan to what is the delivery purpose. Ruxardia Dariescu: Remember, when I said we look at the linear flow in business, from a business structure to operation, then these resources. Now I want to flip that to say, we actually look at business.
Ruxardia Dariescu: We look at people and operations in a circular way because each one impact each other and the moment it's impacted, it creates a recursive process there. Ruxardia Dariescu: And for people to connect through purpose for any project delivery, despite uncertainty, people have to come together to discover their sweet spot. Ruxardia Dariescu: In incoming accord come together and have a pulse together. A project team, it's only a unity of a purpose, value, culture, strategy, objectives, processes, methodologies, tools.
Ruxardia Dariescu: They're all in that specific moment, the competence and mindset that is glued together in a circular way to create a pulse of the team that interacts together. Ruxardia Dariescu: When that rhythm is established, you have a fluid delivery. When you are outside that rhythm, you don't have a pulse, you have a heart attack. Ruxardia Dariescu: So that that is is disturbing for the people who try to commit together to something to bring the competence to communicate to organize to build relationships and put together the determination to deliver together.
Ruxardia Dariescu: So this is, this is the story of how words are critical to the way people interact and that criticality brings or removes uncertainty when we deliver together. Ruxardia Dariescu: And if it's anything I would like you to take away today from this story is that we can only work together when we are aligned with a common purpose.
Ruxardia Dariescu: Objectives are ways of measuring how far or how far of how close we are to that purpose, but the purpose itself answer the question why we are doing that and if we cannot agree why we are doing that as a team is very difficult to deliver without creating levels of uncertainty. Ruxardia Dariescu: Now we need to have clarity of objectives as well as meaningful objectives is no point in having objectives that are designed for a year, but we actually work in two weeks sprints.
Ruxardia Dariescu: Now, there is also critical to ensure the sync between the plan and the process generic processes do not support a plan to deliver. Ruxardia Dariescu: It's also important to acknowledge people competence is not the resource is not the capacity it's a competence. Ruxardia Dariescu: And we are in the services industry in tech therefore our competence is packed in our heads, we cannot accelerate our heads, we cannot create more heads to do that we have one competence that applies to that specific moment.
Ruxardia Dariescu: We need to acknowledge that and to acknowledge also that people are the value not the resource not the capacity when we realize that and we all realize it at the same time. Ruxardia Dariescu: We are removing levels of uncertainty for the ability to work together and all those 35% of losses will convert themselves in wins, but we need to start measuring the quality of people interactions.
Ruxardia Dariescu: So be smart choose smart and play well together. Ruxardia Dariescu: I am Ruxandra Dariescu and I would like to thank you for taking this journey with me. Ruxardia Dariescu: I will suggest that if you have time to browse go on bookbone.com, which is the library where my book on sustainable project deliverability for agile teams is published.
Ruxardia Dariescu: I will look to switch off my sharing so I can actually see the chat and if there are any questions I open the floor to that. Ruxardia Dariescu: Are there any questions. Ruxardia Dariescu: Thank you, I appreciate how can you start measuring people interactions where there are many ways you can create your own models or.
Ruxardia Dariescu: You can look me up I can take you through the journey of measuring that it's very simple it does create the pulse of the team. Ruxardia Dariescu: In a very specific way of looking at that and measures the ability to deliver together measures the competence level measures communication in a fully transparent way for the teams to look at that.
Ruxardia Dariescu: To now would you mind dropping me a line on LinkedIn I can share review the study. Ruxardia Dariescu: DevOps and agile are two different things agile it's a methodology it's a way of thinking that puts in puts yourself in a structure DevOps is a function. Ruxardia Dariescu: I guess we're going to get cut off in a moment because my time is up for this session, and I really appreciate you being with me I sorry about the delay in starting it and I look forward to seeing you on next journeys.
Ruxardia Dariescu: Please connect with me on LinkedIn my ID there is Ruxandra D. Ruxardia Dariescu: I'll drop a line here also to everyone to go there to connect with me with the with the LinkedIn link itself. Ruxardia Dariescu: Thank you so much.
Transcribed automatically; names checked against the speaker record. Select a time to jump there.
Article based on this talk
Why agile projects fail on people and language, not plans
Ruxandra Dariescu argues that the words teams use shape their interactions, and that a shared purpose is what removes delivery uncertainty.
In short
Ruxandra Dariescu argues that most project failures in tech trace back to people interactions, and that those interactions are governed by language. Teams that still speak of people as capacity, budgets as cost and timelines as fixed create uncertainty. Teams that align on a shared purpose, and treat people as competence and value, deliver more fluidly.
Key takeaways
Spot project delivery language, such as capacity, FTEs and fixed timelines, that treats people as resources.
Reframe delivery around customer needs, project purpose and value to market rather than time to market.
Recognize how a single word like commitment carries different personal and emotional meanings across a team.
Align a team on a shared delivery purpose before discussing the delivery plan.
Set objectives and processes that fit the project's scope and working cadence, such as two-week sprints.
Failure starts with people
Dariescu opens with a number that motivated her recent book on agile teams and sustainable delivery: about 35% of projects in the tech world fail, as she cited. When she examined the reasons, including executives failing to support people, disconnected individual objectives, talent gaps and failed collaboration, she saw a common thread. Every reason involved people.
From there she makes her central claim: people interaction is governed by the way we talk to each other. "So for me, it's very, it's a very clear statement, we need to redefine the language and reposition it for the purpose." (1:43)
From capacity and timelines to purpose and value
In what Dariescu calls the old world of project delivery, people are counted as capacity or FTEs, budget is a cost, work is predefined and timelines are fixed, even in organizations that call themselves agile. Risk management focuses on budget, capacity and scope, all aimed at shareholder profit. She describes this as a linear flow of information from the business to operations to capacity.
Her alternative is circular. The project, the process and the people continuously influence one another in service of a purpose. Processes should be tailored to the scope of the project rather than borrowed generically from the organization, and they should support efficiency rather than act as blockers. Roles become a temporary identity within a specific project, people are adaptive learners, and information is shared transparently. Even the familiar phrase time to market gets reworked: "We create value to market." (4:31)
In this view, the team itself is a stakeholder group that creates value, with the shareholder as only one of several stakeholders.
Words carry flavors and personal history
The heart of the talk is about how language works between people. Dariescu describes words as cultural constructs, each one carrying the experience, industry, context, emotions and culture in which a person learned it. "But what's the most important thing is that no word in any language spoken on this planet has a power on its own. We assign the power to words." (3:56)
She illustrates this with the daily stand-up. Someone can say they completed a task or learned to run demos, or they can say they feel under control all the time or wasted their time in the meeting. Those flavors, elevating or deprecating, give words the power to push a team toward breakdowns or breakthroughs.
To make this concrete, she takes the word commitment. Thinking about commitment is simple and linear: look it up in a dictionary. Feeling about commitment is different, because it depends on the specific moment of a specific interaction. She notes, as she cited, that English alone has over 3,000 words describing feelings. In a team of two, five or twenty, those feelings can line up neatly or form a tangled network around a single word.
Purpose creates the team's pulse
When team members' individual narratives about a word like commitment fall into sync, Dariescu says they create an interaction efficiency niche. Interacting outside that niche adds uncertainty. She cites a study by a university in Japan which found that people focused on the same purpose at the same moment create brain coherence and work well together. "But for that to happen, we have to flip the question from what is the delivery plan to what is the delivery purpose." (9:17)
A project team, in her framing, is a unity of purpose, value, culture, strategy, objectives, processes, methodologies, tools, competence and mindset, glued together in a circular way. The result is a rhythm. "When that rhythm is established, you have a fluid delivery. When you are outside that rhythm, you don't have a pulse, you have a heart attack." (10:20)
What teams should do differently
Dariescu closes with practical principles. First, a common purpose comes before everything else: "And if it's anything I would like you to take away today from this story is that we can only work together when we are aligned with a common purpose." (10:58) Objectives measure progress toward that purpose, and they must be meaningful at the right scale; yearly objectives make little sense for teams working in two-week sprints. Processes must be in sync with the plan, since generic processes do not support delivery.
She also asks teams to stop treating people as resources. "It's also important to acknowledge people competence is not the resource is not the capacity it's a competence." (11:53) In tech services, competence lives in people's heads and cannot simply be accelerated or multiplied. Her final call is to start measuring the quality of people interactions. In the brief Q&A she adds that teams can build their own models for this, measuring the ability to deliver together, competence and communication transparently, and she distinguishes agile as a methodology and way of thinking from DevOps as a function.
Watch the talk
It's All About the People: Resolving Agile Delivery Uncertainties Through People Interactions, by Ruxandra Dariescu (15 minutes): https://www.womentech.net/video/its-all-about-people-resolving-agile-delivery-uncertainties-through-people-interactions-0
About the speaker
Ruxandra Dariescu introduces herself in the talk as a business agility coach, consultant, mentor, speaker and author with over 25 years of experience in tech, creating products and platforms, transforming organizations and coaching people. The session record did not include her role, company or bio.
Questions this talk answers
Why do so many tech projects fail?
What is wrong with traditional project delivery language?
Why do words matter so much in team interactions?
How can a team reduce delivery uncertainty?
Is DevOps the same as agile?
Drafted with AI from the talk transcript. Editor review pending.
Frameworks and ideas mentioned
Agile
Daily stand-up
Sprints
DevOps
Resources mentioned
Ruxandra Dariescu's book on sustainable project deliverability for agile teams, published on Bookboon (bookboon.com)
Cite this talk
WomenTech Network. "It's All About the People: Resolving Agile Delivery Uncertainties Through People Interactions by Ruxandra Dariescu." WomenTech Network, 2022. https://www.womentech.net/video/its-all-about-people-resolving-agile-delivery-uncertainties-through-people-interactions-0