\documentclass[hyperref=pdftex, presentation]{beamer}
% Replacing 'presentation' with 'handout' in the above line
% will produce 4 slides per page.
% The hyperref option makes it possible to include hyperlinks.

\mode<presentation> {
\usetheme{Boadilla}
\setbeamercovered{transparent}
}

\usepackage[english]{babel}
\usepackage[latin1]{inputenc}
\usepackage{times}
\usepackage[T1]{fontenc}

\mode<handout>{
\usepackage{pgfpages}
\pgfpagesuselayout{4 on 1}[letterpaper,landscape,border shrink=5mm]
\setbeamercolor{background canvas}{bg=black!10} }

\setbeamertemplate{footline}
{
\leavevmode%
\hbox{%
\begin{beamercolorbox}[wd=.333333\paperwidth,ht=2.25ex,dp=1ex,center]{author
	in head/foot}%
	\usebeamerfont{author in head/ foot}\insertshortauthor%&\approx& (\insertshorti
\end{beamercolorbox}%
\begin{beamercolorbox}[wd=.333333\paperwidth,ht=2.25ex,dp=1ex,center]{title
	in head/foot}%
	\usebeamerfont{title in head/foot}\insertshorttitle
\end{beamercolorbox}%
\begin{beamercolorbox}[wd=.333333\paperwidth,ht=2.25ex,dp=1ex,right]{date in
	head/foot}%
	\usebeamerfont{date in head/foot}\insertshortdate\hspace*{2em}
	\insertframenumber / \inserttotalframenumber\hspace*{2ex}
\end{beamercolorbox}}%
\vskip0pt%
}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%


\title{Software priorities}

\author{Sho Uemura}
%\institute{SLAC}
\date[May 15, 2014]

\begin{document}

\begin{frame}
	\titlepage
\end{frame}

\begin{frame}{Acting on priorities}
	\begin{itemize}
		\item We have consensus on priorities: what next?
		\item Need to go from ``yeah, we should do that'' to actually knowing how we get it done
		\item We're not a top-down organization:
			\begin{itemize}
				\item Nobody can keep track of everything that needs to be done
				\item People closer to the work understand better what's involved
				\item An ``expert'' in one task is a ``learner'' in another
				\item Need direct person-to-person contact
			\end{itemize}
		\item Due dates, not just priorities
	\end{itemize}
\end{frame}

\begin{frame}{A proposal}
	\begin{itemize}
		\item Spin out responsibility for priority items (let's call them ``components'') to individuals (``component leads'')
		\item The lead is not the person who does all the work; the lead is the person who knows what work needs to be done
		\item Components have:
			\begin{itemize}
				\item Defined requirements/deliverables and milestones
				\item Simulation studies or system tests
				\item Due dates
				\item Tasks with assignees
			\end{itemize}
		\item Leads should know what work is being done for their component
			\begin{itemize}
				\item Make this part of the ``software roundtable?''
				\item JIRA
			\end{itemize}
	\end{itemize}
\end{frame}

\begin{frame}{What does this mean for people?}
	\begin{itemize}
		\item Leads should feel comfortable assigning tasks, asking for expert help, etc.
			\begin{itemize}
				\item Not that others shouldn't! But if you're responsible for something that we need to run HPS, everyone is responsible for helping you
			\end{itemize}
		\item If you're doing work for a component:
			\begin{itemize}
				\item You should be talking to your lead/updating JIRA about what you're doing, even if it's incomplete
				\item Your lead should know how oversubscribed you are with non-software work/other software components
			\end{itemize}
	\end{itemize}
\end{frame}

\begin{frame}{Components, leads (strawman)}
	\begin{itemize}
		\item Needed for run:
			\begin{itemize}
				\item Trigger tuning/monitoring: Kyle?
				\item Data quality monitoring: Matt?
				\item ECal monitoring/calibration: Stuart?
				\item SVT monitoring/calibration: Omar?
				\item Conditions: Jeremy?
				\item DAQ/ET/EVIO: Jeremy? Sho?
			\end{itemize}
		\item Needed for analysis:
			\begin{itemize}
				\item ECal reconstruction: Holly?
				\item Tracking/alignment: Pelle? Matt?
				\item Event reconstruction and DST: Omar?
				\item Physics analysis/MDC: Matt?
				\item MC: Sho?
				\item Data catalog: ?
			\end{itemize}
		\item More? We can add things later as they come up
	\end{itemize}
\end{frame}

\begin{frame}{If this is OK, next steps:}
	\begin{itemize}
		\item Over e-mail: discuss requirements with leads
		\item Leads should learn status, identify tasks, talk with other leads and non-software people about dependencies
		\item At upcoming software meetings, quick presentations on components
			\begin{itemize}
				\item Emphasis on plans over status
			\end{itemize}
	\end{itemize}
\end{frame}
%\item My model for this is something like the SVT (Omar) and ECal (me) monitoring talks at September 2012 collab meeting

\end{document}