Managing development

Reporting

Reporting from developer

On a internal team configuration mode, 1 meeting every morning of 10-15mn should be organized to ensure team coordination, review the effort of the day before, talk about eventual problems, assign the tasks and fix the daily objectives.

With a distant team, writing reports is essential as the communication is not such efficient as the internal mode.
Developer need to report each they work on the case they're assign to by a comment even if the case is not finish. They should explain where are they and talk about eventual problems.
See: developer_documentation#Reporting.

Reporting to client

Organize weekly meeting to reassure the client.

Reporting to account manager

Deadline

Reporting to CFO

Look after the deadline and budget
Reporting to CFO
Broke down income and cost of sale by type of work:
outcome: hosting, salary, contractors, sysadmin, office computers, cap (monitoring, domain nane, internet), software
income: website sales, ongoing dev, iphone dev, maintenance, requirement specs, training
+ break down the IT different tasks to see where the time is going

Deal with specifications changes

Keep client in spec and avoid dev/client contact

Developer communication

Case process

Code review