... | ... | @@ -11,23 +11,22 @@ Roadmaps should: |
|
|
* be constantly updated with honest status and estimations
|
|
|
|
|
|
|
|
|
This is done in Gitlab, using milestones, labels and boards. Projects documentations and other more in depth stuff will be done via wiki. By organizing this with Trac tickets we will be able to create specific queries to answer specific questions. Example of use case questions:
|
|
|
This is done in Gitlab, using milestones, labels and boards. Projects documentations and other more in depth stuff will be done via wiki. By organizing this with Gitlab issues we will be able to create specific queries to answer specific questions. Example of use case questions:
|
|
|
|
|
|
* What was done on March for a specific sponsor ?
|
|
|
* What work on release x.x.x is related to a sponsor, and who are these sponsor?
|
|
|
* How much work is on person X plate?
|
|
|
* Person X will to take paternity leave and wants to plan for his absence - he wants to share with his team the tasks he needs to hand over while away.
|
|
|
* At a dev meeting a team wants to reaview the past ideas to plan what to do next about a project.
|
|
|
* Person X will to take paternity leave and wants to plan for his absence - she wants to share with her team the tasks she needs to hand over while away.
|
|
|
|
|
|
## Roadmap Exercise
|
|
|
|
|
|
There is a [template for pad](./process/TemplateRoadmapNotes) we use to take notes in.
|
|
|
There is a [template for the pad](./process/RoadmapNotesTemplate) we use to take notes in.
|
|
|
|
|
|
### Steps
|
|
|
|
|
|
1. Go over the priorities for the team. Do people need to add or change any of those priorities?
|
|
|
2. Go over the projects that the team is working on.
|
|
|
3. Us previous knowledge to move tickets around in the working board and create new tickets when needed.
|
|
|
3. Us previous knowledge to move tickets around in the working board and create new tickets when needed.
|
|
|
|
|
|
## Working Boards
|
|
|
|
... | ... | |