Roles on Software Development Projects

Like most industries, the software development community uses loads of industry-specific buzzwords that people outside of our field don’t know. And the software development community is especially good at creating new words to replace perfectly good words just after everyone got used to them. (Who started using the term “endpoint” anyway?)

At DelMar, we use certain titles for the roles on our development projects. Different firms may use different titles but don’t let that confuse you. The tasks these roles perform still need to be done no matter what name you give them.

Also note these names are for roles on a team, and not necessarily job titles or different people. On most projects, multiple roles can be handled by a single person. For example, the business analyst and project manager roles often are handled by one team member, or the system architect and backend developer could be the same person. On very small projects, all roles may even be handled by just one person, but having a single team member who is good at all roles is hard to find.

Roles on the Development Team

Business Analyst – Works closely with domain experts, understands the business needs for the software, and communicates these needs to the development team

Project Manager – Makes sure tasks are completed on time and within budget

System Architect – Designs at a high-level the technical components for the entire system

Frontend (FE)/User Interface (UI) Designer – Designs user interfaces using lo-fidelity mockups (aka, wireframes), hi-fidelity mockups, and minimal functioning prototypes

FE/UI Developer – Codes and tests user interfaces for:

Backend (BE) Developer – Codes and tests application business logic that runs on servers, and defines data storage and database design

Quality Assurance (QA) – Ensures all parts of the system function as designed

Server Administration/DevOps – Deploys applications and monitors backups, OS patches, malware prevention, security audits, etc.

Mentor – Works one-on-one with junior developers to offer advice and insight

Trainer – Works with multiple developers and/or end users at once in a classroom environment with planned lessons, assignments, and feedback

Customer Roles

In addition to the roles on the development team, the people who the software is written for have roles. Again, these roles aren’t necessarily different people.

Domain Expert – Understands the business needs for the software

End User – Eventually uses the software

Champion – Keeps everyone enthused about the project and convinces the financial backer that getting the software built is worth paying for

Financial Backer – Pays for the software to be built

Feel ready to take on a customer role with DelMar? Send us a message to get started with a free consultation.