Organizational agility for technology companies
Better delivery starts with how the organization works.
I help technology leaders turn ambitious strategy into focused, sustainable delivery. Every engagement draws on proven playbooks, but the solution is shaped around the company’s culture, people, products, and goals.
Experience across organizations including
How I help
Change the system.
Unlock the teams.
Choose the challenge that sounds most familiar.
Agility that works
Move beyond ceremonies to meaningful organizational change.
I help organizations keep what is useful, remove what has become performative, and create a model suited to their culture, people, products, and business—not someone else’s framework.
- Agile transformation reset
- Advanced product owner and scrum master training
- Hands-on team and leadership coaching
Focus & alignment
Connect company priorities to the work teams actually do.
I work with leaders and teams to make priorities explicit, shape coherent backlogs, and create planning practices that support real choices—not an ever-growing list of commitments.
- Organizational and delivery assessment
- Operating-model and portfolio design
- Practical planning and prioritization
Flow & delivery
Find what is really slowing delivery—and address it at the right level.
Slow delivery is rarely a motivation problem. Together, we examine dependencies, team design, decision latency, work in progress, and the incentives that keep familiar problems in place.
- Value-stream and dependency analysis
- Team topology and ways of working
- Leadership coaching through implementation
Training
Build alignment—not just agile vocabulary.
Effective training gives people across an organization a shared understanding of how they will work together and why. It builds the values behind agility—collaboration, transparency, focus, feedback, and adaptability—so teams can be both high-performing and happy while delivering meaningful customer value.
Discuss training for your organizationDesigned for the people leading and doing the work
Whole teams
Create common expectations for collaboration, planning, incremental delivery, feedback, and continuous improvement.
Leaders
Understand how priorities, structures, incentives, and leadership behavior shape the teams’ ability to deliver.
Scrum masters & product owners
Build the judgment and practical skills to lead teams, shape valuable work, and remove obstacles.
Founder, Purple Agility
About Nicola
Two decades of making agile useful in the real world.
Nicola Dourambeis is an experienced technology executive with a background in innovative technology delivery, organizational strategy, and large-scale change.
She began working with agile methods in 2004 at ThoughtWorks, managing early extreme programming programs for complex software delivery. As industry interest grew, she helped establish the company’s US agile enablement practice.
Nicola later built one of the industry’s strongest enterprise agile programs at Salesforce, supporting more than 200 software and infrastructure teams while the company tripled in size and expanded its product lines five-fold.
Her work combines an executive’s understanding of organizational systems with a practitioner’s respect for what it takes to deliver. Deep experience provides the playbooks, patterns, and judgment; close attention to each client’s culture determines how they are applied.
The best solution is not the one that follows a framework most closely. It is the one people can embrace, sustain, and use to deliver better outcomes for their customers.
Silicon Valley Bank · Medium · L.L.Bean · British Telecom · Siemens Medical · athenahealth
Selected assessments
Look beyond the ceremonies.
Change the conditions around the work.
Agile problems rarely begin with a chart or a tool. They emerge from how priorities are set, teams are structured, decisions are made, work crosses boundaries, and people learn from feedback. These anonymized examples show different problems—and different recommendations—under the agile umbrella.
01 High-growth software organization Scaling autonomy without creating fragmentation Modern technology and energetic teams were not enough to overcome tiny team structures, functional handoffs, competing priorities, and inconsistent boundaries.
What the assessment revealed
- Small teams and functional handoffs limited collaboration and created single points of failure.
- Too much work was spread across concurrent priorities.
- Technical standards were difficult to find or inconsistently understood.
- Legacy systems and unreliable automation created drag and risk.
What was recommended
- Build larger, more capable cross-functional teams with embedded leadership and design.
- Force-rank priorities and make completed, end-to-end delivery visible.
- Clarify supported tools, frameworks, and technical constraints.
- Strengthen team leadership through targeted training and coaching.
02 Established financial institution Moving from heroics and consensus to shared execution A collaborative, client-centered culture had also produced too many one-off solutions, slow decisions, organizational silos, and work spread across unclear priorities.
What the assessment revealed
- Cross-functional work was difficult to execute from end to end.
- A desire for inclusion brought too many people into decisions and left ownership unclear.
- Heroics and bespoke solutions had become difficult to scale.
- Underinvestment in technology, tools, people, and basic standards increased risk.
What was recommended
- Align teams around shared priorities and complete customer outcomes.
- Clarify decision rights and push appropriate decisions deeper into the organization.
- Use incremental delivery to create credible examples of success.
- Invest in the organizational and technical foundations required for sustainable delivery.
03 Complex product organization Replacing false precision with focused delivery Strong people and customer commitment were constrained by long-range certainty demands, excessive commitments, cross-team dependencies, and accumulated complexity.
What the assessment revealed
- Confidence targets encouraged conservative estimates and too much planning far into the future.
- Unclear priorities led teams to start too much and finish too little.
- Dependencies, consensus-heavy decisions, and excessive process created long wait times.
- Product complexity and technical debt made customer-facing change increasingly difficult.
What was recommended
- Replace false precision with bottom-up planning, ranges, and regular recalibration.
- Establish genuine organization-level priorities and make trade-offs explicit.
- Organize reviews around incremental, end-to-end customer outcomes.
- Examine the full value stream and remove processes that add delay without value.
04 Large technology organization Turning a collection of specialists into a team Agile activities were present, but planning, estimates, and assignments optimized individuals while important decisions remained with a layer above the people doing the work.
What the assessment revealed
- Scrum mechanics sat inside a largely waterfall operating model.
- Teams behaved as collections of assigned specialists rather than shared owners.
- Planning was administrative, with little discussion of customer or technical context.
- Demos and retrospectives generated energy and feedback but were not yet driving adaptation.
What was recommended
- Pilot a whole-team model with shared goals, bottom-up planning, and incremental delivery.
- Reconsider team boundaries and sizes to reduce dependency management.
- Track work in progress, interruptions, and cycle time to understand flow—not judge individuals.
- Remove duplicated process and use training and coaching to support the structural changes.
These examples describe assessment findings and recommendations, not claimed implementation results. Client identities and identifying details have been removed.
Selected thinking
Practical ideas for people doing the work.
Agile Planning & Delivery: Five Common Mistakes
Patterns that undermine delivery, with direct ways to address them.
Read on Medium Medium · PlanningHow—and Why—to Do Bottom-Up Release Planning
A practical approach to engaging teams in building credible, aligned release plans.
Read on Medium Medium · LeadershipPractical Tips for Speaking to Executives
How to make the value of an initiative clear to senior leaders—and avoid losing the room.
Read on MediumStart a conversation
What would be possible if your organization could reach its full potential?
If your organization is growing, changing, or struggling to turn priorities into results, let’s talk.
Email Nicola