History: Introduction

Source of version: 24 (current)

First of all you might want to set up some things to organize your work.

!!Set up your internal communication tools
Every useful information about the company should live in a single place allowing everyone to know where to find it.
This information can live in your CRM as a project called of the name of your company:
* [company_internal_technical_information|Company internal handy information]
* [company_tools|Company tools]
* [backup_policy|Backup policy]
* [password_policy|Password policy]
* Internal and external contact database (should be in your CRM)
You should use a shared calendar for [organize_meeting|meetings]. 
Your team should only uses company account for email and other things as it will facilitate the take over by someone else.

!!Set up your team 
- [new_it_employees|Hiring employee].
- [hiring_contractor|Hiring contractor]. 

!!Set up your [resources#CRM|CRM] (Customer Relationship Management)
You should set up all the information needed by the client in one single place as there can be multiple users, the contact person can change (quit, be replaced...) or client can just loose the information. And you don't want to re-explain things each time. 
Your CRM should also include a case tracker to allow a collaborative process for the specification gathering process and bug/feature report as it allows multiple persons to comment and be notified. 
Documentation provided to client should include:
* Company contacts,
* Project specification,
* Project Documentation,
* Production specification.
See [client_documentation|client documentation template].
You should have a unique number per project across all your software from quote to final invoice. It will allow everyone to track everything against the same project. 

!!Set up your [resources#Bugtracker|Bugtracker] 
It should contain all the information needed by your internal team and/or external contractor in terms of:
* What is the company and contacts,
* How to communicate,
* Best practice development,
* Used tools,
* Development process,
* Reporting,
* invoicing (for contractor).
See [developer_documentation|developer information template].

SourceHistory

- A simple and Open process for web team management - Find Register Log in Username: Password: I forgot my password Register
	Sidebar Menu Home Search Categories Wiki Wiki Home Last Changes List Pages Orphan Pages Sandbox Multiple Print Structures Articles Articles Home List Articles Forums List Forums File Galleries List Galleries	History: Introduction View page Source of version: 24 (current) First of all you might want to set up some things to organize your work. !!Set up your internal communication tools Every useful information about the company should live in a single place allowing everyone to know where to find it. This information can live in your CRM as a project called of the name of your company: * [company_internal_technical_information\|Company internal handy information] * [company_tools\|Company tools] * [backup_policy\|Backup policy] * [password_policy\|Password policy] * Internal and external contact database (should be in your CRM) You should use a shared calendar for [organize_meeting\|meetings]. Your team should only uses company account for email and other things as it will facilitate the take over by someone else. !!Set up your team - [new_it_employees\|Hiring employee]. - [hiring_contractor\|Hiring contractor]. !!Set up your [resources#CRM\|CRM] (Customer Relationship Management) You should set up all the information needed by the client in one single place as there can be multiple users, the contact person can change (quit, be replaced...) or client can just loose the information. And you don't want to re-explain things each time. Your CRM should also include a case tracker to allow a collaborative process for the specification gathering process and bug/feature report as it allows multiple persons to comment and be notified. Documentation provided to client should include: * Company contacts, * Project specification, * Project Documentation, * Production specification. See [client_documentation\|client documentation template]. You should have a unique number per project across all your software from quote to final invoice. It will allow everyone to track everything against the same project. !!Set up your [resources#Bugtracker\|Bugtracker] It should contain all the information needed by your internal team and/or external contractor in terms of: * What is the company and contacts, * How to communicate, * Best practice development, * Used tools, * Development process, * Reporting, * invoicing (for contractor). See [developer_documentation\|developer information template]. SourceHistory
RSS: Wiki Articles File Galleries Forums This content is licensed under a Creative Commons Attribution 3.0 Unported License offered by Pierre Doleans and sponsored by Collabforge - Website powered by Tiki Wiki

Sidebar

Menu

History: Introduction

Source of version: 24 (current)