Littlefish Project Team Roles and Responsibilities
|
I think it
important to try and identify the roles of contributors even if they are
performed formally or informally. Some will wear different "hats" as the
need arises. As always comments and constructive ideas are always welcome. |
| Project Manager | Orchestrates the the detailed technical work of the project including development , quality assurance and user documentation |
| Architect | Responsible for the conceptual integrity of the software at design and implementation level |
| User Interface Designer | Responsible for the conceptual integrity of the software at the level visible to the user. |
| Developers | Responsible for the the detailed design and implementation of the software. They are responsible for making the software work |
| QA /Testers | They are responsible for finding all the ways to make the software break. They plan and manage test activities, create detailed test plans and perform tests |
| Tool Smith | Responsible for developing build scripts, maintaining source code control system developing any specialised utilities needed by the project |
| Build co-ordinator | Responsible for maintaining and running the daily build and for notifying developers when their source code breaks the build |
| Risk Officer | Watches for emerging risks .Maintains the top 10 risks list. Basically plays the devils advocate |
| Documentation Writers & Proof readers | Responsible for generating and checking help files, printed documentation and other instructional materials for the end user |
| End Users | People who test out the programme and report any problems, bugs with the software and documentation etc |
| Translators | Those who are able to translate the programme and documentation into other languages |