Common project team members

 

The following lists, in no participant order, the major players and what they do. The most common names are given, but expect CT variations and additions:

·Project managers, program managers, Or producersDrive the project from beginning to end. They're usually responsible for writing the product spec, managing the schedule, and making the critical decisions and trade-offs.

Project Manager

 

·ArchitectsOr System EngineersAre the technical experts on the product team. They're usually very experienced and therefore are qualified to design the overall systems architecture or design for the software. They work very closely with the programmers.

Architect

 

·Programmers, developers, Or codersDesign and write software and fix the bugs that are found. they work closely with the corresponding TS and project managers to create the software. then, they work closely with the project managers and testers to get the bugs fixed.

Programmers and developers

 

·TestersOr QA (Quality Assurance)Staff are responsible for finding and reporting problems in the software product. They work very closely with all members of the team as they develop and run their tests, and report the problems they find.

Testers, QA

 

·Technical writers, user authentication ance, user education, manual writers, Or extends stratorsCreate the paper and online documentation that comes with a software product.

Document Engineer

 

·Configuration ManagementOr BuilderHandles the process of pulling together all the software written by the programmers and all the documentation created by the writers and putting it together into a single package.

Configuration Administrator

 

As you can see, several groups of people contribute to a software product. on large teams there may be dozens or hundreds working together. to successfully communicate and organize their approach, they need a plan, a method for getting from point A to point B.