Skip to content
Snippets Groups Projects

Draft: Add Processes & Meetings

Closed Kaj Habegger requested to merge 7-define-document-meetings-processes into master
2 files
+ 109
1
Compare changes
  • Side-by-side
  • Inline
Files
2
@@ -16,7 +16,111 @@
\section{Type of Collaboration}
\section{Roles}
\section{Meetings}
\section{Processes \& Meetings}
To achieve an agile project our team uses Scrum+ to define processes in this project.
\subsection{Backlogs}
\subsubsection{Product Backlog}
The Product Backlog is realized in Excel.
\subsubsection{Sprint Backlog}
The Sprint Backlog is realized in GitLab.
Product Backlog items will be refined and transformed into GitLab Issues during Planning.
\subsection{Sprint}
\noindent Sprint informations:
\begin{itemize}
\item Sprint duration: 2 weeks
\item Sprint start: Tuesday (Or second day of work week)
\item Total amount of Sprints: 5
\end{itemize}
\subsubsection{Planning}
Each Sprint is started by Planning.\\
\noindent Planning procedure:
\begin{enumerate}
\item Discuss what should be achieved during this Sprint
\item Evaluate which Product Backlog items should be put into the Sprint Backlog
\item Discuss which developer takes care of which Sprint Backlog items
\end{enumerate}
\vspace{2mm}
\noindent Further informations about Planning:
\begin{itemize}
\item Frequency: Once every two weeks
\item Location: OST campus building 5
\item Date/Time: Tuesday 12:00
\item Duration: 30 min
\end{itemize}
\subsubsection{Weeklys (Meetings)}
Our team will do weekly meetings, so called weeklys, to catch up with each others progress.
Without further reason every team member attends to weeklys in person on site.\\
\noindent Further informations about weeklys:
\begin{itemize}
\item Frequency: Once per week
\item Location: OST campus building 5
\item Date/Time: Tuesday 10:00
\item Duration: 1h
\end{itemize}
\subsubsection{Review}
Each Sprint-ending is initiated by a Review.\\
\noindent Review procedure:
\begin{enumerate}
\item Each developer presents what they worked on during the Sprint
\item Progress evaluation of the project
\item Evaluate and apply environment changes (Risk analysis, Product Backlog adjustments, etc.)
\end{enumerate}
\vspace{2mm}
\noindent Further informations about Review:
\begin{itemize}
\item Frequency: Once every two weeks
\item Location: OST campus building 5
\item Date/Time: Tuesday 11:00
\item Duration: 30 min
\end{itemize}
\subsubsection{Retrospective}
Each Sprint ends by a Retrospective.\\
\noindent Retrospective procedure:
\begin{enumerate}
\item Discuss positive experiences of the last Sprint
\item Discuss problems of the last Sprint
\end{enumerate}
\vspace{2mm}
\noindent Further informations about Retrospective:
\begin{itemize}
\item Frequency: Once every two weeks
\item Location: OST campus building 5
\item Date/Time: Tuesday 11:30
\item Duration: 30 min
\end{itemize}
\subsection{Stakeholder meetings}
\begin{itemize}
\item Frequency: After reaching a milestone
\item Location: Room 8.025, 8.125, 8.225 or 8.U25
\item Attendants: Thomas Kälin and all team members
\end{itemize}
\subsection{Documentation guidelines}
There are no additional documenation guidelines beside the ones already given by this \LaTeX \: template.
\subsection{Code guidelines}
Our team complies to the official C\# coding guidelines, which can be found \href{https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/coding-style/coding-conventions}{here}.
\section{Long-term Plan}
\section{Short-term Plan - Next Iteration}
\section{Risk Management}
\ No newline at end of file