---
title: 'Project documentation template'
disqus: hackmd
---

# Metronomicon


# Table of Contents

[TOC]

# Beginners Guide / Overview

This part of the documentation is meant to provide any new entrant with a quick high-level overview over our actual project management processes, which mix agile and top down waterfall roadmap planning.

This chapter is not exhaustive and does not go into all the details

## The Stage Gate Process

## Project Execution after Stage Gate

## Smaller Projects (ad hoc)

## Unplanned Tasks like Bugs and Surprise Maintenance

## Obvious shortcomings that we know of

…tomorrow's TODO list.

## JIRA Structure

### JIRA Projects

JIRA software projects exist per team. We are aware this is not (exactly) the way it should be used. Since a lot of the work that is done is maintenance that is bound to teams, which in turn are bound to certain concrete tasks/components, this is what could be called a _pragmatic_ decision.

So essentially, each team is represented by exactly one JIRA project. Larger teams like "Search & Data" are split into their subteams which each are represented by exactly one JIRA project (Software, Data, Crawling).

### JIRA Boards

Each team by default gets different boards:
- a sprint board to handle tasks with the simple status:
- todo
- work in progress
- done
- a story board to handle the different status a story can have:
- todo
- development
- internal review
- quality assurance
- external review
- ready for deployment
- done
- a bug board to have a focus view on bugs (bugs will be shown in sprint board too)

Default board style is Scrum for all teams. Depending on team decision this may be Kanban too (?).

### Plans / Roadmapping Feature

## Confluence Structure

…as we naively imagine it.

## "Project" --> Stage-Gate-Process

select pmo project, pmo board
create issue, type project
give it a name
describe your project for g0, g1
attach your files, etc

create work packages
create issue, type epic
select project as parent link
give it a name
describe your work package in description
talk to EA and PO(s)

the PO can create his story in their team board and connect it via epic link

## "Smaller Project" --> Not Stage-Gate-Process
## Bugs
Currently it's not planned to have a perfect solution where we have only one place to create a new bug and assign this bug later to a specific team.

For the start, we start with issuetype bug and we think it's ok, that anyone create a new bug in the team specific board.

## Unplanned
## Spike
## Epic
## Story
## Task

# Jira-Project

Currently we have two different types of Projects:
- Team
- Project

A project with category "Team" and prefix "Team" in project name is the starting point for a 11880 development team or other kind of department.

The other Projects are big projects related to the gate process <-- @JohannesTiemer: is that still correct?

# Confluence

we want to create a new data structure in confluece, where we have the abbilty to create the follwing tasks:
- meeting notes
- with a template
- linked to specific components / projects
- project templates
- here's the place where we can plan the project from idea over g0/g1/g2 to a running project
- linked to jira
- linked to task description from sprint planing
- linked to further documentation
- mix of atlasian draft and melanies draft?

What to do to create a new development team / clone a existing team as new (approx 12 minutes)
- create project
- select scrum
- use template
- company managed
- add project details
- name
- key
- share settings with an existing project
- select existing project
- create project
- view all filters
- copy bug filter
- edit settings
- view all boards
- copy bug board
- edit settings
- change name
- change location
- change filter
- change shares
- copy story board
- edit settings
- change name
- change location
- change filter
- change shares
- copy daily board
- edit settings
- change name
- change location
- change filter
- change shares