Differences between revisions 4 and 5
Revision 4 as of 2008-08-06 16:25:06
Size: 1692
Editor: localhost
Comment: converted to 1.6 markup
Revision 5 as of 2008-11-05 02:13:27
Size: 1690
Editor: crlspr-24
Comment: Fixed menu bar
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Line 2: Line 4:


Team Reporting

As the Ubuntu project continues to grow at a ferocious pace, it can often be quite difficult for teams to get an idea of what is going on in different parts of the project. As we continue to grow, it is essential that we know what we are all working on and keep a good level of communication between different parts of the project. This will help us stay abreast of what we are all working on in our different teams, prevent duplication of work and help identify new areas of potential.

To help keep these communication channels open we have developed a simple team reporting procedure. This process will only take a few minutes for each team every month, but will help everyone stay up to date with what is going on.

Getting your team ready for reporting

To hot-rod your team for reporting, follow these steps:

  • Nominate one or more people to overlook the team reporting process for your team.
  • For your team you should create a page on your wiki where reporting notes can be stored each month. For a sample page click here.

  • Alternatively, feel free to edit the report page directly and add your report items there.

Gathering the reports

Gathering the reports is simple. Just follow these steps:

  • Send out a few mails to your team to encourage them to put notes of their work on the team report page. These reports should be collated for your team by the 22nd of each month.

  • When the 22nd comes, take the content from your team's report page and add it to the next month on the Team Reports page.

BuildingCommunity/TeamReporting (last edited 2009-10-11 16:25:48 by 99-21-107-94)