\documentclass[10pt,a4paper]{article}

% Packages
\usepackage{fancyhdr}           % For header and footer
\usepackage{multicol}           % Allows multicols in tables
\usepackage{tabularx}           % Intelligent column widths
\usepackage{tabulary}           % Used in header and footer
\usepackage{hhline}             % Border under tables
\usepackage{graphicx}           % For images
\usepackage{xcolor}             % For hex colours
%\usepackage[utf8x]{inputenc}    % For unicode character support
\usepackage[T1]{fontenc}        % Without this we get weird character replacements
\usepackage{colortbl}           % For coloured tables
\usepackage{setspace}           % For line height
\usepackage{lastpage}           % Needed for total page number
\usepackage{seqsplit}           % Splits long words.
%\usepackage{opensans}          % Can't make this work so far. Shame. Would be lovely.
\usepackage[normalem]{ulem}     % For underlining links
% Most of the following are not required for the majority
% of cheat sheets but are needed for some symbol support.
\usepackage{amsmath}            % Symbols
\usepackage{MnSymbol}           % Symbols
\usepackage{wasysym}            % Symbols
%\usepackage[english,german,french,spanish,italian]{babel}              % Languages

% Document Info
\author{vini.vivero}
\pdfinfo{
  /Title (scrum.pdf)
  /Creator (Cheatography)
  /Author (vini.vivero)
  /Subject (SCRUM Cheat Sheet)
}

% Lengths and widths
\addtolength{\textwidth}{6cm}
\addtolength{\textheight}{-1cm}
\addtolength{\hoffset}{-3cm}
\addtolength{\voffset}{-2cm}
\setlength{\tabcolsep}{0.2cm} % Space between columns
\setlength{\headsep}{-12pt} % Reduce space between header and content
\setlength{\headheight}{85pt} % If less, LaTeX automatically increases it
\renewcommand{\footrulewidth}{0pt} % Remove footer line
\renewcommand{\headrulewidth}{0pt} % Remove header line
\renewcommand{\seqinsert}{\ifmmode\allowbreak\else\-\fi} % Hyphens in seqsplit
% This two commands together give roughly
% the right line height in the tables
\renewcommand{\arraystretch}{1.3}
\onehalfspacing

% Commands
\newcommand{\SetRowColor}[1]{\noalign{\gdef\RowColorName{#1}}\rowcolor{\RowColorName}} % Shortcut for row colour
\newcommand{\mymulticolumn}[3]{\multicolumn{#1}{>{\columncolor{\RowColorName}}#2}{#3}} % For coloured multi-cols
\newcolumntype{x}[1]{>{\raggedright}p{#1}} % New column types for ragged-right paragraph columns
\newcommand{\tn}{\tabularnewline} % Required as custom column type in use

% Font and Colours
\definecolor{HeadBackground}{HTML}{333333}
\definecolor{FootBackground}{HTML}{666666}
\definecolor{TextColor}{HTML}{333333}
\definecolor{DarkBackground}{HTML}{02DEC1}
\definecolor{LightBackground}{HTML}{EFFCFB}
\renewcommand{\familydefault}{\sfdefault}
\color{TextColor}

% Header and Footer
\pagestyle{fancy}
\fancyhead{} % Set header to blank
\fancyfoot{} % Set footer to blank
\fancyhead[L]{
\noindent
\begin{multicols}{3}
\begin{tabulary}{5.8cm}{C}
    \SetRowColor{DarkBackground}
    \vspace{-7pt}
    {\parbox{\dimexpr\textwidth-2\fboxsep\relax}{\noindent
        \hspace*{-6pt}\includegraphics[width=5.8cm]{/web/www.cheatography.com/public/images/cheatography_logo.pdf}}
    }
\end{tabulary}
\columnbreak
\begin{tabulary}{11cm}{L}
    \vspace{-2pt}\large{\bf{\textcolor{DarkBackground}{\textrm{SCRUM Cheat Sheet}}}} \\
    \normalsize{by \textcolor{DarkBackground}{vini.vivero} via \textcolor{DarkBackground}{\uline{cheatography.com/172693/cs/36299/}}}
\end{tabulary}
\end{multicols}}

\fancyfoot[L]{ \footnotesize
\noindent
\begin{multicols}{3}
\begin{tabulary}{5.8cm}{LL}
  \SetRowColor{FootBackground}
  \mymulticolumn{2}{p{5.377cm}}{\bf\textcolor{white}{Cheatographer}}  \\
  \vspace{-2pt}vini.vivero \\
  \uline{cheatography.com/vini-vivero} \\
  \end{tabulary}
\vfill
\columnbreak
\begin{tabulary}{5.8cm}{L}
  \SetRowColor{FootBackground}
  \mymulticolumn{1}{p{5.377cm}}{\bf\textcolor{white}{Cheat Sheet}}  \\
   \vspace{-2pt}Published 4th January, 2023.\\
   Updated 4th January, 2023.\\
   Page {\thepage} of \pageref{LastPage}.
\end{tabulary}
\vfill
\columnbreak
\begin{tabulary}{5.8cm}{L}
  \SetRowColor{FootBackground}
  \mymulticolumn{1}{p{5.377cm}}{\bf\textcolor{white}{Sponsor}}  \\
  \SetRowColor{white}
  \vspace{-5pt}
  %\includegraphics[width=48px,height=48px]{dave.jpeg}
  Measure your website readability!\\
  www.readability-score.com
\end{tabulary}
\end{multicols}}




\begin{document}
\raggedright
\raggedcolumns

% Set font size to small. Switch to any value
% from this page to resize cheat sheet text:
% www.emerson.emory.edu/services/latex/latex_169.html
\footnotesize % Small font.

\begin{multicols*}{4}

\begin{tabularx}{3.833cm}{X}
\SetRowColor{DarkBackground}
\mymulticolumn{1}{x{3.833cm}}{\bf\textcolor{white}{Scrum Essentials}}  \tn
% Row 0
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Scrum Definition}}} \tn 
% Row Count 1 (+ 1)
% Row 1
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{Scrum is a lightweight framework that helps people, teams and organizations to generate value through adaptive solutions for complex problems} \tn 
% Row Count 4 (+ 3)
% Row 2
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Agile Manifesto}}} \tn 
% Row Count 5 (+ 1)
% Row 3
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{{\bf{1.}} Individuals and interactions over processes and tools. \{\{nl\}\}{\bf{2.}} Working Software over comprehensive documentation \{\{nl\}\}{\bf{3.}} Customer collaboration over contract negotiation. \{\{nl\}\}{\bf{4.}} Responding to change over following a plan. \{\{nl\}\}\{\{fa-star\}\}While there are value in the items on the right, we value more the items on the left.} \tn 
% Row Count 13 (+ 8)
\hhline{>{\arrayrulecolor{DarkBackground}}-}
\end{tabularx}
\par\addvspace{1.3em}

\begin{tabularx}{3.833cm}{X}
\SetRowColor{DarkBackground}
\mymulticolumn{1}{x{3.833cm}}{\bf\textcolor{white}{{\bf{Pillars of Empiricism}}}}  \tn
% Row 0
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{1.}} Transparency} \tn 
% Row Count 1 (+ 1)
% Row 1
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{{\bf{2.}} Inspection} \tn 
% Row Count 2 (+ 1)
% Row 2
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{ 3.}} Adaptation} \tn 
% Row Count 3 (+ 1)
\hhline{>{\arrayrulecolor{DarkBackground}}-}
\end{tabularx}
\par\addvspace{1.3em}

\begin{tabularx}{3.833cm}{X}
\SetRowColor{DarkBackground}
\mymulticolumn{1}{x{3.833cm}}{\bf\textcolor{white}{{\bf{Scrum Values}}}}  \tn
% Row 0
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{1.}} Commitment {\bf{2.}} Focus {\bf{3.}} Openness {\bf{4.}} Respect {\bf{5.}} Courage} \tn 
% Row Count 2 (+ 2)
\hhline{>{\arrayrulecolor{DarkBackground}}-}
\end{tabularx}
\par\addvspace{1.3em}

\begin{tabularx}{3.833cm}{X}
\SetRowColor{DarkBackground}
\mymulticolumn{1}{x{3.833cm}}{\bf\textcolor{white}{{\bf{The Increment}}}}  \tn
% Row 0
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Definition}}} \tn 
% Row Count 1 (+ 1)
% Row 1
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{Is a {\bf{concrete stepping stone}} toward the {\bf{Product Goal.}}} \tn 
% Row Count 3 (+ 2)
% Row 2
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Key Points}}} \tn 
% Row Count 4 (+ 1)
% Row 3
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-star\}\} Each sprint should deliver an increment. A potentially releasable increment is created each sprint. \{\{nl\}\}\{\{fa-star\}\} Multiple increments may be created within a sprint. \{\{nl\}\}\{\{fa-star\}\}Increment may be delivered to stakeholders prior to the end of the Sprint.\{\{nl\}\}\{\{fa-star\}\} Sprint Review should never be a gate to releasing value or a bottle neck. Showing or releasing an increment to the stake holders should no wait till the sprint review.\{\{nl\}\}\{\{fa-star\}\} Increments are an additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. \{\{nl\}\}\{\{fa-star\}\} In order to provide value, the Increment must be usable.} \tn 
% Row Count 18 (+ 14)
% Row 4
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{The commitment for the increment is: The Definition od Done (DoD)} \tn 
% Row Count 20 (+ 2)
% Row 5
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{The {\bf{Definition of Done}} is a formal description of the state of the Increment when it {\bf{meets the quality measures}} required for the product.} \tn 
% Row Count 23 (+ 3)
% Row 6
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{DoD creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment. }}} \tn 
% Row Count 26 (+ 3)
% Row 7
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{nl\}\}\{\{fa-star\}\} It creates transparency, so everyone knows what needs completing and to what standards. \{\{nl\}\}\{\{fa-star\}\} If a Product Backlog item does not meet the Definition of Done, it cannot be released or even presented at the Sprint Review.  \{\{nl\}\}\{\{fa-star\}\} Instead, it returns to the Product Backlog for future consideration.} \tn 
% Row Count 33 (+ 7)
\end{tabularx}
\par\addvspace{1.3em}

\vfill
\columnbreak
\begin{tabularx}{3.833cm}{X}
\SetRowColor{DarkBackground}
\mymulticolumn{1}{x{3.833cm}}{\bf\textcolor{white}{{\bf{The Increment}} (cont)}}  \tn
% Row 8
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{If the Definition of Done for an increment is part of the standards of the organization, all Scrum Teams must follow it as a minimum.}}} \tn 
% Row Count 3 (+ 3)
% Row 9
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-star\}\} If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product. \{\{nl\}\}\{\{fa-star\}\} The scrum team can add standards. \{\{nl\}\}\{\{fa-star\}\} The Developers are required to conform to the Definition of Done.  \{\{nl\}\}\{\{fa-star\}\} If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same Definition of Done.} \tn 
% Row Count 12 (+ 9)
% Row 10
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Key Points}}} \tn 
% Row Count 13 (+ 1)
% Row 11
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-star\}\} Once the developers meet the Definition of Done of a product backlog item, and increment is born. \{\{nl\}\}\{\{fa-star\}\} Once a Product Backlog Item meets the DoD is ready to present to the stakeholders and be considered for releasing to the users.} \tn 
% Row Count 19 (+ 6)
\hhline{>{\arrayrulecolor{DarkBackground}}-}
\end{tabularx}
\par\addvspace{1.3em}

\begin{tabularx}{3.833cm}{X}
\SetRowColor{DarkBackground}
\mymulticolumn{1}{x{3.833cm}}{\bf\textcolor{white}{{\bf{Scrum Artifacts}}}}  \tn
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{Scrum's artifacts {\bf{represent work or value}}. They are designed to {\bf{maximize transparency of key information}}. Thus, everyone inspecting them has the same basis for adaptation. \newline % Row Count 4 (+ 4)
Each artifact {\bf{contains a commitment}} to ensure it provides information that enhances transparency and focus against which progress can be measured: \newline % Row Count 8 (+ 4)
{\bf{1.}} For the {\bf{Product Backlog}} it is the {\bf{Product Goal}}. \newline % Row Count 10 (+ 2)
{\bf{2.}} For the {\bf{Sprint Backlog}} it is the {\bf{Sprint Goal}}. \newline % Row Count 12 (+ 2)
{\bf{3.}} For the {\bf{Increment}} it is the {\bf{Definition of Done}}.% Row Count 14 (+ 2)
} \tn 
\hhline{>{\arrayrulecolor{DarkBackground}}-}
\end{tabularx}
\par\addvspace{1.3em}

\begin{tabularx}{3.833cm}{x{1.7165 cm} x{1.7165 cm} }
\SetRowColor{DarkBackground}
\mymulticolumn{2}{x{3.833cm}}{\bf\textcolor{white}{{\bf{Scrum Principles}}}}  \tn
% Row 0
\SetRowColor{LightBackground}
{\bf{1.}} Satisfy Customers Through Early \& Continuous Delivery. & {\bf{7.}} Working software is the primary measure of progress. \tn 
% Row Count 4 (+ 4)
% Row 1
\SetRowColor{white}
{\bf{2.}} Welcome Changing Requirements Even Late in the Project. & {\bf{8. }}Agile Processes to support a consistent development pace. \tn 
% Row Count 8 (+ 4)
% Row 2
\SetRowColor{LightBackground}
{\bf{3.}} Frequent Delivery of working software. & {\bf{9. }}Attention to technical detail and design enhances agility. \tn 
% Row Count 12 (+ 4)
% Row 3
\SetRowColor{white}
{\bf{4.}} Collaboration between the business stakeholders and developers throughout the project. & {\bf{10.}} Simplicity (the art of maximizing the amount of work not done) is essential \tn 
% Row Count 17 (+ 5)
% Row 4
\SetRowColor{LightBackground}
{\bf{5.}} Support, trust and motivate the people involved. & {\bf{11.}} Self-organizing teams encourage great architectures requirements and designs. \tn 
% Row Count 22 (+ 5)
% Row 5
\SetRowColor{white}
{\bf{6.}} Enable face-to-face interactions. & {\bf{12.}} Regular reflections on how to become more effective. \tn 
% Row Count 26 (+ 4)
\hhline{>{\arrayrulecolor{DarkBackground}}--}
\end{tabularx}
\par\addvspace{1.3em}

\begin{tabularx}{3.833cm}{X}
\SetRowColor{DarkBackground}
\mymulticolumn{1}{x{3.833cm}}{\bf\textcolor{white}{{\bf{The Sprint Backlog}}}}  \tn
% Row 0
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Definition}}} \tn 
% Row Count 1 (+ 1)
% Row 1
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{It is a list of work that need to be completed within the sprint.} \tn 
% Row Count 3 (+ 2)
% Row 2
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{The Developers owns the Sprint Backlog}}} \tn 
% Row Count 4 (+ 1)
% Row 3
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-circle\}\}Developers are always accountable for creating a plan for the sprint. \{\{nl\}\}\{\{fa-circle\}\}The Sprint Backlog is a plan by and for the developers. \{\{nl\}\}\{\{fa-circle\}\}It is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint in order to achieve the Sprint Goal} \tn 
% Row Count 11 (+ 7)
% Row 4
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{The Sprint Backlog is composed of:}}} \tn 
% Row Count 12 (+ 1)
% Row 5
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-circle\}\}The Sprint Goal (why) \{\{nl\}\}\{\{fa-circle\}\}The set of Product Backlog items selected for the Sprint (what) \{\{nl\}\}\{\{fa-circle\}\}Actionable plan for delivering the Increment (how).} \tn 
% Row Count 16 (+ 4)
% Row 6
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{The commitment for the sprint backlog is: Sprint Goal}}} \tn 
% Row Count 18 (+ 2)
% Row 7
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-circle\}\}The Sprint Goal is the single objective for the Sprint. \{\{nl\}\}\{\{fa-circle\}\}Although the Sprint Goal is a commitment by the Developers. \{\{nl\}\}\{\{fa-circle\}\}The sprint goal should be flexible enough in terms of the exact work that is needed to achieve.\{\{nl\}\}\{\{fa-circle\}\}The Sprint Goal is created during the Sprint Planning event and then added to the Sprint Backlog.\{\{nl\}\}\{\{fa-circle\}\}As the Developers work during the Sprint, they keep the Sprint Goal in mind. \{\{nl\}\}\{\{fa-circle\}\}If the work turns out to be different than they expected, they collaborate with the Product Owner to negotiate the scope of the Sprint Backlog within the Sprint without affecting the Sprint Goal.} \tn 
% Row Count 32 (+ 14)
\end{tabularx}
\par\addvspace{1.3em}

\vfill
\columnbreak
\begin{tabularx}{3.833cm}{X}
\SetRowColor{DarkBackground}
\mymulticolumn{1}{x{3.833cm}}{\bf\textcolor{white}{{\bf{The Sprint Backlog}} (cont)}}  \tn
% Row 8
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Key Points}}} \tn 
% Row Count 1 (+ 1)
% Row 9
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-star\}\}The sprint Backlog is initially created during sprint planning session, developers are accountable of the amount work they can deliver. \{\{nl\}\}\{\{fa-star\}\}The developers can modify the sprint backlog through out the sprint. And the sprint backlog emerges during the sprint. \{\{nl\}\}\{\{fa-star\}\}This emergence occurs as the scrum team works through the plan and learns more about the work needed to achieve the sprint goal. \{\{nl\}\}\{\{fa-star\}\}As more work is required, the developers add it to the sprint backlog.} \tn 
% Row Count 12 (+ 11)
\hhline{>{\arrayrulecolor{DarkBackground}}-}
\end{tabularx}
\par\addvspace{1.3em}

\begin{tabularx}{3.833cm}{X}
\SetRowColor{DarkBackground}
\mymulticolumn{1}{x{3.833cm}}{\bf\textcolor{white}{{\bf{The Product Backlog}}}}  \tn
% Row 0
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Definition}}} \tn 
% Row Count 1 (+ 1)
% Row 1
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{The Product Backlog is an {\bf{emergent, ordered list of what is needed to improve the product}}.  It is the {\bf{single source of work}} undertaken by the Scrum Team.} \tn 
% Row Count 5 (+ 4)
% Row 2
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Product Backlog is:}}} \tn 
% Row Count 6 (+ 1)
% Row 3
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Emergent}}: Means that you add to it and change it over time as you inspect and adapt \{\{nl\}\}{\bf{Ordered}}: Is ordered by priorities and/or dependencies. \{\{nl\}\}{\bf{Single Source}}: Product Backlog is the single source of work undertaken by the scrum team} \tn 
% Row Count 12 (+ 6)
% Row 4
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{The product owner owns the product backlog}}} \tn 
% Row Count 13 (+ 1)
% Row 5
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-circle\}\}Developing and explicitly communicating the product goal. \{\{nl\}\}\{\{fa-circle\}\}Creating and explicitly communicating product backlog items. \{\{nl\}\}Ordering product backlog items. \{\{nl\}\}\{\{fa-circle\}\}Ensuring that the product backlog is transparent, visible, and understood.} \tn 
% Row Count 19 (+ 6)
% Row 6
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Key points}}} \tn 
% Row Count 20 (+ 1)
% Row 7
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-star\}\}Anyone can add details to a BLI with the Product Owner´s discretion. \{\{nl\}\}\{\{fa-star\}\}Multiple teams can work together on the same product, but a single product backlog is used to describe the upcoming work on the product.} \tn 
% Row Count 25 (+ 5)
% Row 8
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Commitment to the product Goal}}} \tn 
% Row Count 26 (+ 1)
% Row 9
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-circle\}\}The Product Goal is the long-term objective for the Scrum Team. They must fulfill (or abandon) one objective before taking on the next. \{\{nl\}\}\{\{fa-circle\}\}The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against. \{\{nl\}\}\{\{fa- circle\}\}The scrum team should use this goal to plan the work to achieve this goal.} \tn 
% Row Count 34 (+ 8)
\end{tabularx}
\par\addvspace{1.3em}

\vfill
\columnbreak
\begin{tabularx}{3.833cm}{X}
\SetRowColor{DarkBackground}
\mymulticolumn{1}{x{3.833cm}}{\bf\textcolor{white}{{\bf{The Product Backlog}} (cont)}}  \tn
% Row 10
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Product Definition}}} \tn 
% Row Count 1 (+ 1)
% Row 11
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{A product is a vehicle to deliver value. It has a clear boundary, known stakeholders, well-defined users, or customers. A product could be a service, a physical product, or something more abstract.} \tn 
% Row Count 5 (+ 4)
\hhline{>{\arrayrulecolor{DarkBackground}}-}
\end{tabularx}
\par\addvspace{1.3em}

\begin{tabularx}{3.833cm}{x{1.68217 cm} x{1.75083 cm} }
\SetRowColor{DarkBackground}
\mymulticolumn{2}{x{3.833cm}}{\bf\textcolor{white}{Scrum Roles and Responsibilities}}  \tn
% Row 0
\SetRowColor{LightBackground}
{\bf{Role}} & {\bf{Accountable For:}} \tn 
% Row Count 1 (+ 1)
% Row 1
\SetRowColor{white}
{\bf{Product Owner}} & The product owner(PO) is accountable for maximizing the value of the product resulting from the work of the scrum team. \tn 
% Row Count 8 (+ 7)
% Row 2
\SetRowColor{LightBackground}
{\bf{Developers (Developers \& Testers)}} & Developers are the people in the scrum team accountable for create any aspect of a usable increment each sprint. (Developers and Testers) \tn 
% Row Count 16 (+ 8)
% Row 3
\SetRowColor{white}
{\bf{Scrum Master}} & The scrum master is accountable for the scrum team effectiveness. They do this by enabling the scrum team to improve its practices within the scrum framework. \tn 
% Row Count 25 (+ 9)
\hhline{>{\arrayrulecolor{DarkBackground}}--}
\end{tabularx}
\par\addvspace{1.3em}

\begin{tabularx}{3.833cm}{X}
\SetRowColor{DarkBackground}
\mymulticolumn{1}{x{3.833cm}}{\bf\textcolor{white}{{\bf{Developers (Developers \& Testers)}}}}  \tn
% Row 0
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Key Points}}} \tn 
% Row Count 1 (+ 1)
% Row 1
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-star\}\}Scrum teams are cross-functional. \{\{nl\}\} \{\{fa-star\}\}Developers must be empowered and respected, they should be self-managed. They are structured and empowered to manage their own work. \{\{nl\}\} \{\{fa-star\}\}Developers are trusted to manage themselves to complete the work in the sprint backlog and holds themselves accountable for the success of the sprint. \{\{nl\}\} \{\{fa-star\}\}Developers are also accountable to internally decide who does what, when and how. \{\{nl\}\} \{\{fa-star\}\}It is up to the developers as a self-managed team to create a plan to complete the sprint goal (Sprint backlog). \{\{nl\}\} \{\{fa-star\}\}If some of the developers are struggling with assigned work they need to help each other. \{\{nl\}\} \{\{fa-star\}\}Developers should meet the Definition of Done for each task. \{\{nl\}\} \{\{fa-star\}\}They should adapt their plan each day toward the sprint goal. \{\{nl\}\} \{\{fa-star\}\}Developers should meet every day at daily scrum. \{\{nl\}\} \{\{fa-star\}\}There are no sub-teams or hierarchies, developers are a cohesive unit of professionals.} \tn 
% Row Count 22 (+ 21)
% Row 2
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Developers are always accountable for:}}} \tn 
% Row Count 23 (+ 1)
% Row 3
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-star\}\}Creating a plan for the sprint, the sprint backlog \{\{nl\}\} \{\{fa-star\}\}Instilling quality by adhering to a definition of done \{\{nl\}\} \{\{fa-star\}\}Adapting their plan each day toward the sprint goal \{\{nl\}\} \{\{fa-star\}\}Holding each other accountable as professionals.} \tn 
% Row Count 29 (+ 6)
\hhline{>{\arrayrulecolor{DarkBackground}}-}
\end{tabularx}
\par\addvspace{1.3em}

\begin{tabularx}{3.833cm}{p{0.57926 cm} p{0.65825 cm} p{0.57926 cm} x{0.81623 cm} }
\SetRowColor{DarkBackground}
\mymulticolumn{4}{x{3.833cm}}{\bf\textcolor{white}{Scrum Events}}  \tn
% Row 0
\SetRowColor{LightBackground}
{\bf{Daily Standup}} & {\bf{Sprint Planning}} & {\bf{Sprint Review}} & {\bf{Sprint Retrospective}} \tn 
% Row Count 3 (+ 3)
\hhline{>{\arrayrulecolor{DarkBackground}}----}
\end{tabularx}
\par\addvspace{1.3em}

\begin{tabularx}{3.833cm}{X}
\SetRowColor{DarkBackground}
\mymulticolumn{1}{x{3.833cm}}{\bf\textcolor{white}{{\bf{Daily Standup}}}}  \tn
% Row 0
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{Definition} \tn 
% Row Count 1 (+ 1)
% Row 1
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{The {\bf{purpose}} of the daily scrum is to {\bf{inspect progress toward the Sprint Goal and adapt the Sprint Backlog}} as necessary, adjusting the upcoming planned work.  \{\{nl\}\}Daily Scrums {\bf{improve communications, identify impediments, promote quick decision-making}}, and consequently {\bf{eliminate the need for other meetings.}}  \{\{nl\}\}During Daily Scrum you can answer this questions:  \{\{nl\}\}1- {\bf{What I did Yesterday.}} \{\{nl\}\}2- {\bf{What I plan to do today.}} \{\{nl\}\}3- {\bf{What is Blocking me.}}} \tn 
% Row Count 11 (+ 10)
% Row 2
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Key Points}}} \tn 
% Row Count 12 (+ 1)
% Row 3
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-star\}\}It is held at the same time and place every working day of the sprint. \{\{nl\}\} \{\{fa-star\}\}Is is a 15 minutes event for the Developers of the Scrum Team. \{\{nl\}\} \{\{fa-star\}\}Developers are the only ones are required. \{\{nl\}\} \{\{fa-star\}\}Developers can select whatever structure and techniques they want, but they must focus on progress toward the sprint goal and produce and actionable plan for the next day of work. \{\{nl\}\} \{\{fa-star\}\}The Daily Scrum is not the only time Developers are allowed to adjust their plan. They often meet throughout the day for more detailed discussions about adapting or re-planning the rest of the Sprint's work.} \tn 
% Row Count 25 (+ 13)
\hhline{>{\arrayrulecolor{DarkBackground}}-}
\end{tabularx}
\par\addvspace{1.3em}

\begin{tabularx}{3.833cm}{X}
\SetRowColor{DarkBackground}
\mymulticolumn{1}{x{3.833cm}}{\bf\textcolor{white}{Sprint Planning}}  \tn
% Row 0
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Definition}}} \tn 
% Row Count 1 (+ 1)
% Row 1
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{Sprint Planning {\bf{initiates the Sprint}} by laying out the work to be performed for the Sprint. This resulting plan is created by the collaborative work of the entire Scrum Team.} \tn 
% Row Count 5 (+ 4)
% Row 2
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Key Points}}} \tn 
% Row Count 6 (+ 1)
% Row 3
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-star\}\}The Product Backlog must be refined. \{\{nl\}\}\{\{fa-star\}\}The whole Scrum Team is required, that means that more than just the scrum team can be involved. \{\{nl\}\}\{\{fa-star\}\}The Scrum Team may also invite other people to attend Sprint Planning to provide advice. \{\{nl\}\}\{\{fa-star\}\}The Product Owner ensures that attendees are prepared to discuss the most important Product Backlog items and how they map to the Product Goal.  \{\{nl\}\}\{\{fa-star\}\}Every participant must know what the Sprint Goal is. \{\{nl\}\}\{\{fa-star\}\}Sprint Planning results in a plan for the sprint, {\bf{The Sprint Backlog}}} \tn 
% Row Count 18 (+ 12)
% Row 4
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Deciding the Sprint Goal}}} \tn 
% Row Count 19 (+ 1)
% Row 5
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{The Scrum Team can decide the sprint goal by considering the following three topics during the planning session: \{\{nl\}\}{\bf{1-}} Why is this Sprint valuable? \{\{nl\}\}{\bf{2-}} What can be Done this Sprint? \{\{nl\}\}{\bf{3-}} How will the chosen work get done?} \tn 
% Row Count 24 (+ 5)
% Row 6
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{1- Why is this Sprint valuable?}}} \tn 
% Row Count 25 (+ 1)
% Row 7
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-circle\}\}The Product Owner proposes how the product could increase its value and utility in the current Sprint. \{\{nl\}\}\{\{fa-circle\}\}Then, the whole Scrum Team then collaborates to {\bf{define a Sprint Goal}} that communicates why the Sprint is valuable. \{\{nl\}\}\{\{fa-circle\}\}{\bf{The Sprint Goal must be finalized prior}} to the end of Sprint Planning.} \tn 
% Row Count 32 (+ 7)
\end{tabularx}
\par\addvspace{1.3em}

\vfill
\columnbreak
\begin{tabularx}{3.833cm}{X}
\SetRowColor{DarkBackground}
\mymulticolumn{1}{x{3.833cm}}{\bf\textcolor{white}{Sprint Planning (cont)}}  \tn
% Row 8
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{2- What can be Done this Sprint?}}} \tn 
% Row Count 1 (+ 1)
% Row 9
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-circle\}\}Developers select items from the Product Backlog to include in the current Sprint. \{\{nl\}\}\{\{fa-circle\}\}The Scrum Team may refine these items during this process, which increases understanding and confidence.\{\{nl\}\}Selecting how much can be completed within a Sprint may be challenging. However, the more the Developers know about their past performance, their upcoming capacity, and their Definition of Done, the more confident they will be in their Sprint forecasts.} \tn 
% Row Count 11 (+ 10)
% Row 10
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{3- How will the chosen work get done?}}} \tn 
% Row Count 12 (+ 1)
% Row 11
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-circle\}\}For each selected Product Backlog item, Developers plan the work necessary to create an Increment that meets the Definition of Done.  \{\{nl\}\}\{\{fa-circle\}\}Developers decomposed Product Backlog items into smaller work items of one day or less.  \{\{nl\}\}\{\{fa-circle\}\}No one else tells the Developers how to turn Product Backlog items into Increments of value. \{\{nl\}\}\{\{fa-circle\}\}The Sprint Goal, the Product Backlog items selected for the Sprint, plus the plan for delivering them are together referred to as the Sprint Backlog. \{\{nl\}\}\{\{fa-circle\}\}Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.} \tn 
% Row Count 26 (+ 14)
\hhline{>{\arrayrulecolor{DarkBackground}}-}
\end{tabularx}
\par\addvspace{1.3em}

\begin{tabularx}{3.833cm}{X}
\SetRowColor{DarkBackground}
\mymulticolumn{1}{x{3.833cm}}{\bf\textcolor{white}{Sprint Review}}  \tn
% Row 0
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{Definition} \tn 
% Row Count 1 (+ 1)
% Row 1
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed.} \tn 
% Row Count 6 (+ 5)
% Row 2
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Key Points}}} \tn 
% Row Count 7 (+ 1)
% Row 3
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-star\}\}Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment.  \{\{nl\}\}\{\{fa-star\}\} Based on this information, attendees collaborate on what to do next.  \{\{nl\}\}\{\{fa-star\}\} The Product Backlog may also be adjusted to meet new opportunities.  \{\{nl\}\}\{\{fa-star\}\} The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation.} \tn 
% Row Count 16 (+ 9)
% Row 4
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Product Owner Role in the Sprint Review}}} \tn 
% Row Count 17 (+ 1)
% Row 5
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-circle\}\}Should be keeping on top of changes in the market place and be ready to make decisions on how to maximize the value of the product.} \tn 
% Row Count 20 (+ 3)
% Row 6
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Goals}}} \tn 
% Row Count 21 (+ 1)
% Row 7
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-star\}\}Inspect the outcome of the Sprint and determine future adaptations \{\{nl\}\}\{\{fa-star\}\}To transparently inform about work which {\bf{has been done (including adding work)}} and work {\bf{has not been done (including work removed).}} \{\{nl\}\}\{\{fa-star\}\}Take advantage to {\bf{receive feedback}} from the stakeholders and adapt.} \tn 
% Row Count 28 (+ 7)
\hhline{>{\arrayrulecolor{DarkBackground}}-}
\end{tabularx}
\par\addvspace{1.3em}

\begin{tabularx}{3.833cm}{X}
\SetRowColor{DarkBackground}
\mymulticolumn{1}{x{3.833cm}}{\bf\textcolor{white}{Product Owner}}  \tn
% Row 0
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Key Points}}} \tn 
% Row Count 1 (+ 1)
% Row 1
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-star\}\} The Product Owner is a {\bf{value maximizer}}. \{\{nl\}\}\{\{fa-star\}\} Is accountable for {\bf{effective product backlog management}}. \{\{nl\}\}\{\{fa-star\}\} Decides work tasks priority, is accountable for {\bf{ordering product backlog items}} \{\{nl\}\}\{\{fa-star\}\} Must {\bf{understand the market and the product}} to understand what makes a valuable product. \{\{nl\}\}\{\{fa-star\}\}Accountable to clearly {\bf{communicate the Product Backlog Items}}. \{\{nl\}\}\{\{fa-star\}\} Accountable to ensure the {\bf{Product Backlog is Transparent, visible and understood}}.  \{\{nl\}\}\{\{fa-star\}\} {\bf{Represents the needs of many stake holders}} in the product backlog. \{\{nl\}\}\{\{fa-star\}\} The Product Owner Vision is called {\bf{"The Product Goal"}}} \tn 
% Row Count 15 (+ 14)
% Row 2
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-bullseye\}\} {\bf{The Product Goal}}} \tn 
% Row Count 16 (+ 1)
% Row 3
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{Is the Product Owner Vision, is a long term objective for the Scrum Team} \tn 
% Row Count 18 (+ 2)
\hhline{>{\arrayrulecolor{DarkBackground}}-}
\end{tabularx}
\par\addvspace{1.3em}

\begin{tabularx}{3.833cm}{X}
\SetRowColor{DarkBackground}
\mymulticolumn{1}{x{3.833cm}}{\bf\textcolor{white}{Scrum Master}}  \tn
% Row 0
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Key Points}}} \tn 
% Row Count 1 (+ 1)
% Row 1
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-star\}\}The Scrum master is a servant leader, who serves the scrum team, the product owner and the organization. \{\{nl\}\} \{\{fa-star\}\}The Scrum master is accountable for stablishing scrum as defined in the scrum guide. They do this by helping everyone to understand scrum theory and practice, both within the scrum team and the organization. \{\{nl\}\} \{\{fa-star\}\}The scrum master is accountable for the scrum team effectiveness. They do this by enabling the scrum team to improve its practices within the scrum framework.} \tn 
% Row Count 12 (+ 11)
% Row 2
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Scrum master serves the Scrum team by:}}} \tn 
% Row Count 13 (+ 1)
% Row 3
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-star\}\}Coaching team members to work together on the sprint goal through self management and cross-functionality. \{\{nl\}\} \{\{fa-star\}\}Helping the scrum team focus on creating high-value increments that meet the definition of done. \{\{nl\}\} \{\{fa-star\}\}Encourage the scrum team to raise problems, discover any dependencies or impediments and help to remove them finding solutions so the team can progress. \{\{nl\}\} \{\{fa-star\}\}Ensuring all scrum events happen are positive, productive and kept within the time box. \{\{nl\}\} \{\{fa-star\}\}Scrum masters coach the team on how to do scrum properly.} \tn 
% Row Count 25 (+ 12)
% Row 4
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Scrum master serves the Product Owner by:}}} \tn 
% Row Count 26 (+ 1)
% Row 5
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-star\}\}Helping find techniques for effective product goal definition and product backlog management. \{\{nl\}\} \{\{fa-star\}\}How to decompose BLI to be ready for the sprint. \{\{nl\}\} \{\{fa-star\}\}Helping the scrum team to understand the need for clear and concise product backlog items. \{\{nl\}\} \{\{fa-star\}\}Helping establish empirical product planning for a complex environment. \{\{nl\}\} \{\{fa-star\}\}Facilitating stakeholder collaboration as requested or needed \{\{nl\}\} \{\{fa-star\}\}Promote the inspection and adaption opportunities for empirical product planning.} \tn 
% Row Count 37 (+ 11)
\end{tabularx}
\par\addvspace{1.3em}

\vfill
\columnbreak
\begin{tabularx}{3.833cm}{X}
\SetRowColor{DarkBackground}
\mymulticolumn{1}{x{3.833cm}}{\bf\textcolor{white}{Scrum Master (cont)}}  \tn
% Row 6
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Scrum master serves the organization by:}}} \tn 
% Row Count 1 (+ 1)
% Row 7
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-star\}\}Leading, training, and coaching the organization in its scrum adoption. \{\{nl\}\} \{\{fa-star\}\}Planning and advising scrum implementation within the organization. \{\{nl\}\} \{\{fa-star\}\}Helping employees and stakeholders understand and enact an empirical approach for complex work. \{\{nl\}\} \{\{fa-star\}\}Removing barriers between stakeholders and scrum team} \tn 
% Row Count 9 (+ 8)
\hhline{>{\arrayrulecolor{DarkBackground}}-}
\end{tabularx}
\par\addvspace{1.3em}

\begin{tabularx}{3.833cm}{X}
\SetRowColor{DarkBackground}
\mymulticolumn{1}{x{3.833cm}}{\bf\textcolor{white}{Sprint Retrospective}}  \tn
% Row 0
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Definition}}} \tn 
% Row Count 1 (+ 1)
% Row 1
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{The purpose of the Sprint Retrospective is to {\bf{plan ways to increase quality and effectiveness.}} \{\{nl\}\}The Scrum Team inspects how the last Sprint went with regards to:  \{\{nl\}\}\{\{fa-circle\}\}individuals \{\{nl\}\}\{\{fa-circle\}\}Interactions \{\{nl\}\}\{\{fa-circle\}\}Processes \{\{nl\}\}\{\{fa-circle\}\}Tools \{\{nl\}\}\{\{fa-circle\}\}Definition of Done.  \{\{nl\}\{\{nl\}\}\{\{fa-star\}\} This event is a good chance to add to the wealth and improve the definition of done.} \tn 
% Row Count 10 (+ 9)
% Row 2
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Scrum Team discusses:}}} \tn 
% Row Count 11 (+ 1)
% Row 3
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-star\}\}what went well during the Sprint \{\{nl\}\}\{\{fa-star\}\}what problems it encountered \{\{nl\}\}\{\{fa-star\}\}how those problems were (or were not) solved.   {\bf{Key Points}}} \tn 
% Row Count 15 (+ 4)
% Row 4
\SetRowColor{LightBackground}
\mymulticolumn{1}{x{3.833cm}}{{\bf{Key Points}}} \tn 
% Row Count 16 (+ 1)
% Row 5
\SetRowColor{white}
\mymulticolumn{1}{x{3.833cm}}{\{\{fa-star\}\}focus on How you are working as a team \{\{nl\}\}\{\{fa-star\}\}The Scrum Team identifies the most helpful changes to improve its effectiveness.  \{\{nl\}\}\{\{fa-star\}\}Impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint. \{\{nl\}\}\{\{fa-star\}\}The Sprint Retrospective concludes the Sprint.} \tn 
% Row Count 24 (+ 8)
\hhline{>{\arrayrulecolor{DarkBackground}}-}
\end{tabularx}
\par\addvspace{1.3em}


% That's all folks
\end{multicols*}

\end{document}