Work organization

Introduction

The development team uses a kanban-like process, inspired by SCRUM. All members should know the main points, see the official guide.

Using a well-know process should help into:

reduce external interference (like support request)
promote group work to increase the performance. See From storming to performing
respect release dates
create periodic release for products to gather feedback for new releases and better activity pianification

Every sprint lasts for about 2 work weeks (8 days)
On Friday, the sprint can be paused and the developer can pick items from his own todo list, schedule activities with the support team, develop customization or even research on new topics. If customization activity can't be fit in a single day, the development must be part of a dedicated sprint.
Every day, the team should meet for a "daily scrum": team members should already know what info need to be shared with other team members
When a new sprint starts, the PO (Product Owner) should be available for the planning (about 2 hrs)
Team composition should be stable to 3 or 4 people. Every member must be active
The last Friday of the sprint, the team will present the work to the global meeting

The PO must keep the backlog up to date
The team should review the backlog with the PO to evaluate the development effort
Sprints are scheduling ahead and the scheduling time shouldn't be changed