> For the complete documentation index, see [llms.txt](https://guide.techfleet.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.techfleet.org/team-portal/new-teammate-handbook/project-training-teams/supported-team-functions-in-project-training/development-function.md).

# Development Function

{% hint style="info" %}
A role is not a person! [Learn more about Function vs. Commitment vs. Person here.](/team-portal/new-teammate-handbook/expectations-for-teammates/commitment-vs.-job-function-vs.-people-on-teams.md)
{% endhint %}

## How to Train for the Development Function

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><a href="/pages/KQKcYjQiAbU5Dk5Apfqo"><strong>Read The Agile Handbook</strong></a></td><td><a href="/files/L2LNqgZd6cZIwgtrihsR">/files/L2LNqgZd6cZIwgtrihsR</a></td><td><a href="/pages/KQKcYjQiAbU5Dk5Apfqo">/pages/KQKcYjQiAbU5Dk5Apfqo</a></td></tr><tr><td><a href="/pages/xcsmL02kztCtzMSY8n63"><strong>Read the Service Leadership Handbook</strong></a></td><td><a href="/files/XdBoKj76kX65jvYnHfP3">/files/XdBoKj76kX65jvYnHfP3</a></td><td><a href="/pages/xcsmL02kztCtzMSY8n63">/pages/xcsmL02kztCtzMSY8n63</a></td></tr><tr><td><a href="/pages/kO2YMnaroOAEFvjOdYfY"><strong>Take the Servant Leadership Masterclass</strong></a></td><td><a href="/files/pAgtqjxNq7akz3A1Vf7p">/files/pAgtqjxNq7akz3A1Vf7p</a></td><td><a href="/pages/kO2YMnaroOAEFvjOdYfY">/pages/kO2YMnaroOAEFvjOdYfY</a></td></tr><tr><td><a href="/pages/kO2YMnaroOAEFvjOdYfY"><strong>Take the</strong></a> <a href="/pages/kO2YMnaroOAEFvjOdYfY"><strong>Agile UX Masterclass</strong></a></td><td><a href="/files/4yy8oHaUAPZQBjhJsgfh">/files/4yy8oHaUAPZQBjhJsgfh</a></td><td><a href="/pages/kO2YMnaroOAEFvjOdYfY">/pages/kO2YMnaroOAEFvjOdYfY</a></td></tr><tr><td><a href="/pages/kO2YMnaroOAEFvjOdYfY"><strong>Take the Product Requirements Masterclass</strong></a></td><td><a href="/files/ewD1sjobmvHxgtDGYTgx">/files/ewD1sjobmvHxgtDGYTgx</a></td><td><a href="/pages/kO2YMnaroOAEFvjOdYfY">/pages/kO2YMnaroOAEFvjOdYfY</a></td></tr><tr><td><a href="/pages/kO2YMnaroOAEFvjOdYfY"><strong>Take the Product Operations Masterclass</strong></a></td><td><a href="/files/hQ0bziMJPsHOl5czL8Ow">/files/hQ0bziMJPsHOl5czL8Ow</a></td><td><a href="/pages/kO2YMnaroOAEFvjOdYfY">/pages/kO2YMnaroOAEFvjOdYfY</a></td></tr></tbody></table>

## What is it?&#x20;

Development deals with making designs a reality through technology. It may involve many different aspects and programming languages based on what's being built. A development professional often knows many programming languages.

## Development Function in Tech Fleet vs. Other Companies

Who "Wears the Hats" at companies in the Development function? It depends!

Here's a visual breakdown of roles:&#x20;

<figure><img src="/files/GsApZ6zbs0AYdt6DSLRx" alt=""><figcaption><p>A breakdown of how the development and solutions architecture functions work at different companies. Credit: Tech Fleet.</p></figcaption></figure>

1. There could be one person playing the front-end development function, one person playing the back-end development function, and one person playing the solutions architecture function.&#x20;
2. There could be one person playing the front-end development function and another one person playing the back-end development function plus solutions architecture function.&#x20;
3. There could be one person playing all functions: the front-end development function, back-end development function, and  solutions architecture function.&#x20;

In Tech Fleet, development function is a a combination of the front-end development and back-end development functions.

## Daily Responsibilities

{% hint style="info" %}
[Here's a Tech Fleet Figjam template anyone can use showing cross-functional Agile team responsibilities](https://www.figma.com/community/file/1475625041866413630).
{% endhint %}

The development function typically owns a combination of 2 [commitments](/team-portal/new-teammate-handbook/expectations-for-teammates/commitment-vs.-job-function-vs.-people-on-teams.md):

1. Front-end development
2. Back-end development

### What They Own

1. Developing code
2. Documentation of code
3. Deployment of code
4. Reviewing upcoming work to ensure it's feasible and technically possible to do

### Daily Tasks

* Coding front-end languages
* Coding back-end languages
* Developing databases
* Developing server-side scripts
* Deploying code into repositories
* Testing code that was deployed
* Documenting the coding decisions that have been made

### Breakdown of Responsibilities

Here are some RACI charts depicting the daily tasks that a development function is responsible for, and how they work with other teams:&#x20;

#### RACI for Development Operations

<figure><img src="/files/h6wkNMIETmFVZ9g5MGL1" alt=""><figcaption><p>This is a RACI chart showing the development activities on teams. Credit: Tech Fleet.</p></figcaption></figure>

## You might be a Developer if&#x20;

1. You like logic
2. You like systems thinking
3. You like coding
4. You like technical functions

## Cross-functional Collaboration

1. **With the Client** - facilitate requirements discussions; gather insight and feedback about the solutions being delivered&#x20;
2. **With UX Research** - drive the priorities of research based on the product roadmap / plans
3. **With the Project Management** - facilitate meetings and discussions; pair up to work together on deliverables
4. **With UX Design** - drive the priorities and requirements of UX design based on the product roadmap / plans&#x20;
5. **With UX Writing** - drive the priorities of UX writing based on the product roadmap / plans&#x20;

## Role Expectations

* Work with the product strategy team to refine requirements based on planned work&#x20;
* Collaborate with solutions architecture team to design the system that’s being built based on project needs&#x20;
* Code either front-end, back-end, or middle layer code as described with the project needs&#x20;
* Deploy code once finished Document code as written&#x20;
* Collaborate with the product strategy, UX research, and UX design teams to ensure that the user experience is delivered properly based on product requirements

## Common Deliverables

1. Deployed code
2. Coding documentation

## Head to the Next Lesson


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guide.techfleet.org/team-portal/new-teammate-handbook/project-training-teams/supported-team-functions-in-project-training/development-function.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.