The document outlines the different roles in a software design project team, including the project manager who oversees the team and ensures deadlines are met, the test manager who plans testing tasks, and the quality manager who defines and monitors quality standards. Other roles discussed are the configuration manager, documentation manager, software architect, usability engineer, domain expert, developer, and tester, each with specific responsibilities for their area of expertise.

1. Software design project
The different roles in a team
Department of Information Technology (INTEC) - IBCN

2. The different roles

Project manager (PM)

Test manager (TM)

Quality manager (QM)

Configuration manager (CM) / Sysadmin

Documentation manager (DM)

Usability engineer

Developer

Tester

Software architect

Domain expert

…
Department of Information Technology (INTEC) - IBCN
2

3. Project manager (PM)
= keep the team together
= verify performance against plan
= delegate the work amongst the team members
= keep an eye on the deadlines & commitments
= do some administration (time sheets, meeting, …)
= contact point for assistants
= follow the ‘Project management’ learning path
≠ do everything yourself
≠ doing nothing
≠ being a dictator
Department of Information Technology (INTEC) - IBCN
3

4. Quality manager (QM)
= define the desired quality of the product before
release
= monitor quality during project
= report quality issues to PM
≠ only person who is responsible for the quality of the
product
Department of Information Technology (INTEC) - IBCN
4

5. Test manager (TM)
= determine the testing tasks
= delegate the testing tasks amongst the team
= create a test plan
= follow the ‘Testing (advanced)’ learning path
≠ do all the testing on your own
Department of Information Technology (INTEC) - IBCN
5

6. Configuration manager (CM)
= responsible for hardware / server
= choose necessary tools
= set up server / build tools / testing tools
= manage security on server
= set up Git braching strategy / build strategy / …
= follow the ‘Configuration management (advanced)’
learning path
≠ the guy who can solve everything
Department of Information Technology (INTEC) - IBCN
6

7. Documentation manager (DM)
= make sure the desired level of documentation is
reached
= make sure the required documents are updated
= meet document deadlines
≠ write all the documentation on your own
Department of Information Technology (INTEC) - IBCN
7

8. Software architect
= create / adapt architecture (together with team)!
= make sure architecture is respected
= adapt architecture if needed
Department of Information Technology (INTEC) - IBCN
8

9. Usability engineer
= keep an eye on the usability of the product
= study some best practices about usability
= talk with some potential users about their expectations
Department of Information Technology (INTEC) - IBCN
9

10. Domain expert
= first-line when there are domain-specific questions
= monitors changes in the domain of the product (new
companies, products, techniques, …)
= knows a lot about the domain of the product, where
and how it can be used, …
Department of Information Technology (INTEC) - IBCN
10

11. Developer
= developing code
= doing the assigned tasks
Department of Information Technology (INTEC) - IBCN
11

12. Tester
= writing tests
= doing the assigned tasks
Department of Information Technology (INTEC) - IBCN
12