Our sprints

Organization of the sprints

We have project-wide sprints. Sprints in our project will have a default duration of 1 month, so as to allow for an easier assignment and control of the tasks that are being performed by our distributed set of partners.

Here you are a brief description of how the sprints are organised:

• Week 1: decisions on epics to be handled and setting up the scene for the sprint
• Week 2-3: development
• Week 4: wrapping up and demo generation

Steps to follow creating sprints:

• Define the goal of each sprint & sprint planning
• Assemble their team
• Issue management (open, close and update issues)
• Coordinate their sprint team (daily stand-up etc.)

Milestones

We should have milestones to guide our medium term and long term goals.

Organization of the projects

Each project should last no longer than two months. Projects are scheduled and prioritized according to milestone plans.

Responsibilities

Responsibility of project leader

• Lead the project-wise sprint planning (Review progress of projects, Review issues, Design new projects)
• Define milestones
• Schedule and prioritize projects together with sprint master

Responsibility of project leaders

• Equivalent to conventional sprint leader or group leader
• Design sprint of individual project/epic (Define the goal of the sprint, Define the scope of the sprint (issues to be addressed))
• Assemble team and manage team (Who doing what, How long of each task)
• Manage issue tracking
• Report progress and outcome of each project

Responsibility of sprint master

• The auditor
• Facilitate the scheduling and prioritization of projects
• Make sure each project/epic lasts no longer than 2 sprints