Difference between revisions of "MNE-CPP's Agile Development Cycle"
From MNE-CPP Wiki
| Line 2: | Line 2: | ||
== SCRUM concept == | == SCRUM concept == | ||
The MNE-CPP project is maintained by an agile management approach based on the SCRUM concept. Throughout the MNE-CPP project we have three participating groups: | The MNE-CPP project is maintained by an agile management approach based on the SCRUM concept. Throughout the MNE-CPP project we have three participating groups: | ||
| − | * Developer team: This group includes all developers currently working on a MNE-CPP related project. You can find a list of all active developers [http://www.mne-cpp.org/index.php/team/ here]. | + | * '''Developer team:''' This group includes all developers currently working on a MNE-CPP related project. You can find a list of all active developers [http://www.mne-cpp.org/index.php/team/ here]. |
| − | * Product owner: The product owners can be seen as the senior supervisors of the project. In contrast to the developers the product owners are not directly contributing code to the project. They are in charge of mentoring the project with their long background of industrial and scientific expertise. Furthermore, they are responsible for providing the basic financial backbone of the project. MNE-CPP's product owners are listed [http://www.mne-cpp.org/index.php/team/ here] (last on the list). | + | * '''Product owner:''' The product owners can be seen as the senior supervisors of the project. In contrast to the developers the product owners are not directly contributing code to the project. They are in charge of mentoring the project with their long background of industrial and scientific expertise. Furthermore, they are responsible for providing the basic financial backbone of the project. MNE-CPP's product owners are listed [http://www.mne-cpp.org/index.php/team/ here] (last on the list). |
| − | * SCRUM master: The scrum master is organizing all project management related tasks throughout the MNE-CPP project. He takes care of organizing and moderating all project meetings. Also, he is in charge of communicating results, problems and all other issues between the developers and product owners. Furthermore, the SCRUM master is responsible for creating and maintaining a productive work environment for all particiapting members of the project. If developers or product owners are facing problems or any issues The SCRUM master is the person to contact. The current SCRUM master of the MNE-CPP project is Lorenz Esch. | + | * '''SCRUM master:''' The scrum master is organizing all project management related tasks throughout the MNE-CPP project. He takes care of organizing and moderating all project meetings. Also, he is in charge of communicating results, problems and all other issues between the developers and product owners. This communication takes place weekly in form of a short E-Mail, including a task table and status of all tasks. A more detailed overview of all tasks is send on a monthly basis. Furthermore, the SCRUM master is responsible for creating and maintaining a productive work environment for all particiapting members of the project. If developers or product owners are facing problems or any issues The SCRUM master is the person to contact. The current SCRUM master of the MNE-CPP project is Lorenz Esch. |
| + | |||
| + | A transparent and team oriented workflow is a key concept of the MNE-CPP project. Therefore, we are endorsing the following types of meetings: | ||
| + | * '''Monthly iteration meetings:''' We define a time window of one month as a so called sprint. During a sprint every developer has a fixed number of tasks. An iteration meeting is divided into the following two parts: | ||
| + | *# Sprint Review: During an iteration meeting the current sprint ends and all results/progress are reported individually by every developer. | ||
| + | *# Sprint review: We then plan the upcoming sprint. Meaning, that each developer proposes new tasks for herself/himself and subsequently discusses his taks with the group. | ||
| + | * '''Weekly meetings:''' | ||
== Task tracking== | == Task tracking== | ||
Revision as of 15:02, 23 January 2017
Project Management
SCRUM concept
The MNE-CPP project is maintained by an agile management approach based on the SCRUM concept. Throughout the MNE-CPP project we have three participating groups:
- Developer team: This group includes all developers currently working on a MNE-CPP related project. You can find a list of all active developers here.
- Product owner: The product owners can be seen as the senior supervisors of the project. In contrast to the developers the product owners are not directly contributing code to the project. They are in charge of mentoring the project with their long background of industrial and scientific expertise. Furthermore, they are responsible for providing the basic financial backbone of the project. MNE-CPP's product owners are listed here (last on the list).
- SCRUM master: The scrum master is organizing all project management related tasks throughout the MNE-CPP project. He takes care of organizing and moderating all project meetings. Also, he is in charge of communicating results, problems and all other issues between the developers and product owners. This communication takes place weekly in form of a short E-Mail, including a task table and status of all tasks. A more detailed overview of all tasks is send on a monthly basis. Furthermore, the SCRUM master is responsible for creating and maintaining a productive work environment for all particiapting members of the project. If developers or product owners are facing problems or any issues The SCRUM master is the person to contact. The current SCRUM master of the MNE-CPP project is Lorenz Esch.
A transparent and team oriented workflow is a key concept of the MNE-CPP project. Therefore, we are endorsing the following types of meetings:
- Monthly iteration meetings: We define a time window of one month as a so called sprint. During a sprint every developer has a fixed number of tasks. An iteration meeting is divided into the following two parts:
- Sprint Review: During an iteration meeting the current sprint ends and all results/progress are reported individually by every developer.
- Sprint review: We then plan the upcoming sprint. Meaning, that each developer proposes new tasks for herself/himself and subsequently discusses his taks with the group.
- Weekly meetings:
Task tracking
JIRA is a well known issue tracking tool by Atlassian, which let's you post bug reports, improvement tasks, wishes for new features and much more. It gives you a way to directly participate in the development of MNE-CPP. Please go to MNE-CPP's JIRA website and sign up for an account if you wish to help to improve MNE-CPP.
Document sharing
Next to JIRA we also use Atlassian's Confluence to share documents, meeting notes and other project related files. You can find our confluence page here.
