Collaboration
Collaboration is the coordinated work of multiple participants who contribute toward a shared goal or outcome.
Lead Developer Career Guide
The practice of working jointly with others toward a shared outcome.
- How it is used
- Positions collaboration as how lead developers align project teams, draw on colleagues’ expertise, and work with clients toward successful delivery.
- How deep it goes
- Develops practical habits for communication, delegation, feedback, and conflict response through workplace scenarios rather than a formal collaboration framework.
- Examples
- Uses open-source contributions, developer–designer pairing, and a coding exercise with interdependent features and changing requirements.
- What you can do after
- Practice/perform it by connecting colleagues, sharing progress, inviting feedback, asking for help, and addressing conflict without judgment.
Read how Lead Developer Career Guide explains collaboration →
Think Like a Software Engineering Manager
Collaboration is coordinated work in which multiple people contribute to a shared outcome.
- How it is used
- Coordinates engineering teams and cross-functional partners around shared project goals despite dependencies, competing priorities, and differing expectations.
- How deep it goes
- Provides procedural checklists for goals, roles, communication, feedback, conflict, and measurement rather than a technical implementation.
- Examples
- Uses a delayed profile-page launch, an overwhelmed engineer, and frontend–backend timeline negotiations to show coordination problems and responses.
- What you can do after
- Practice/perform it by aligning goals, assigning ownership, gathering feedback, addressing conflicts, and checking delivery and team signals.
Read how Think Like a Software Engineering Manager explains collaboration →
The Creative Programmer
Collaboration is the social process of working with other people to develop, refine, and improve ideas.
- How it is used
- Frames creativity as social refinement through feedback, teamwork, and discussion of software solutions.
- How deep it goes
- Explains collaboration through feedback, collective-creativity history, and contrasting novice and experienced perspectives rather than team-process mechanics.
- Examples
- Uses the Peripatetics and Camerata, programming teams, student responses, experienced-programmer responses, and an academia-industry figure.
- What you can do after
- Evaluate/understand how feedback and discussion can refine ideas and broaden software-solution exploration.
Designing AI Agents
An agent capability for coordinating information or activity with other agents or humans.
- How it is used
- Coordinates bounded contributions and independent evidence across agent or human boundaries toward a shared goal.
- How deep it goes
- Sets out three adoption gates and four responsibility-splitting patterns without detailing their implementations.
- Examples
- Illustrates independent checking in a controlled rollout and reports a multi-agent research evaluation with higher token use.
- What you can do after
- Evaluate whether to split a task and compare a multi-agent approach with a single-agent baseline.
Effective Behavior-Driven Development
Collaboration is a cooperative working relationship in which relevant participants jointly discover, formulate, and refine software behavior.
- How it is used
- Uses collaboration as BDD’s core way for business and delivery roles to jointly shape working software.
- How deep it goes
- Defines meaningful collaboration, contrasts one-way communication, and offers participation and adoption guidance without prescribing a fixed recipe.
- Examples
- Contrasts a product owner reading a story with meaningful exchange, and compares BDD workload with classic agile activities.
- What you can do after
- Practice inclusive, direct collaboration by improving role interactions and making discussions accessible to participants.
Read how Effective Behavior-Driven Development explains collaboration →
Effective Platform Engineering
Collaboration is the coordinated work of multiple people or teams toward shared objectives.
- How it is used
- Coordinates organizational structure, communication, ownership, and platform support to improve software delivery and shared outcomes.
- How deep it goes
- Explains team structures, platform responsibilities, communication practices, and a process-mapping exercise with delivery metrics.
- Examples
- Uses Epetech’s e-commerce, mobile app, inventory, and platform teams plus process diagrams and delivery-metric scripts.
- What you can do after
- Apply it by modeling workflows, locating collaboration barriers, measuring delivery performance, and organizing teams around business streams.
Read how Effective Platform Engineering explains collaboration →
Collaborative Software Design: How to facilitate domain modeling decisions
Collaboration is the joint performance of design or development work by multiple participants who share knowledge and decisions.
- How it is used
- Improves software design by connecting stakeholders and developers around user needs, architecture, and decisions.
- How deep it goes
- Explains hand-offs, changing requirements, and power dynamics, then offers facilitation prompts rather than implementation detail.
- Examples
- Uses BigScreen’s requirement hand-offs, changing user needs, process diagrams, and a ranking continuum exercise.
- What you can do after
- Apply collaboration by planning participation, managing ranking effects, and eliciting perspectives through structured facilitation.
Interview Speak
The process of working jointly with other people toward a shared objective.
- How it is used
- Frames collaboration as evidence of influence, adaptability, relationship-building, and effective work across organizational boundaries.
- How deep it goes
- Develops interview-answer procedures through question listening, personal attribution, concrete actions, involved parties, and results.
- Examples
- Uses cross-department projects, finance partnerships, change implementation, collaborative planning, negotiation, and humility-at-work examples.
- What you can do after
- Practice/perform interview answers that demonstrate personal contribution, teamwork, adaptability, influence, and successful results.
Architecture Modernization: Socio-technical alignment of software, strategy, and structure
Collaboration is an interaction mode in which two teams work together through ongoing synchronization toward a shared outcome.
- How it is used
- Coordinates two teams when shared alignment matters more than each team’s maximum independent output.
- How deep it goes
- Defines collaboration, explains its coordination mechanisms and cognitive-load cost, and diagnoses overload through an industry topology example.
- Examples
- Uses shared rituals, joint decisions, communication, topology mapping, custom endpoints, and an overloaded integration platform team.
- What you can do after
- Diagnoses coordination overload, visualizes team dependencies, and chooses whether to continue collaboration or change responsibilities and interaction modes.
Also covered in
- The Coder CafeIn early access (MEAP)
- First-Party Data Activation
- "Looks Good to Me"
- Test Driven: Practical TDD and Acceptance TDD for Java Developers
- Writing for Developers: Blogs that get read
- Shipping Go: Develop, deliver, discuss, design, and go again
- The Well-Grounded Python Developer: How the pros use Python and Flask
- Contract Testing in Action
- BDD in Action, Second Edition
What to know first
- requirementsA requirement is a stated need, capability, quality, condition, or constraint that a system, product, solution, or project is expected to satisfy.
- goalA goal is a desired outcome or state that guides actions and decisions or provides a basis for evaluating progress.
- clientA client is a person, organization, device, or software component that receives or uses a product, service, resource, or functionality provided by another party or system.
- innovationInnovation is the creation or adoption of a novel idea, method, product, or practice that produces meaningful change or value.
Related concepts
- handoffuses · A handoff is the transfer of work, responsibility, or relevant information from one person, agent, team, or process to another.
- memorycontrasts with · Memory is a storage capability or mechanism for retaining information or computational state for later access or use.
- behavior-driven developmentused by · Behavior-driven development is a collaborative software development practice that specifies and verifies desired behavior through examples expressed in terms understandable to stakeholders.
- communicationkind of · Communication is the exchange of information, meaning, or signals between people, groups, agents, devices, or software components.
Questions about collaboration
What is collaboration?
Collaboration is the coordinated work of multiple participants who contribute toward a shared goal or outcome.
Which Manning books explain collaboration?
Lead Developer Career Guide, Think Like a Software Engineering Manager, The Creative Programmer, Designing AI Agents, Effective Behavior-Driven Development, Effective Platform Engineering, Collaborative Software Design: How to facilitate domain modeling decisions, Interview Speak and 1 more.
What should I know before learning collaboration?
Manning books that teach collaboration usually introduce requirements, goal, client and innovation first.
What is the difference between collaboration and memory?
Collaboration is the coordinated work of multiple participants who contribute toward a shared goal or outcome. Memory is a storage capability or mechanism for retaining information or computational state for later access or use.
What kinds of collaboration are there?
Kinds of collaboration include asynchronous collaboration and human-machine collaboration.
What is collaboration a kind of?
Collaboration is a kind of communication. Communication is the exchange of information, meaning, or signals between people, groups, agents, devices, or software components.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.








