This repository has been archived by the owner on Dec 22, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathRoadmap.tex
136 lines (115 loc) · 8.43 KB
/
Roadmap.tex
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
%%% Hello!
\section{Roadmap} \label{sec:Roadmap}
% DK: This is a bit self-referential. You have roadmap embedded throughout the description of the pattern. E.g. the context and problem should be able to describe the situation before the solution has been applied, so you should be able to describe them without the solution name in them.
% DK: How is this different from a Backlog? Who “owns” the roadmap? How are changes made to it? How precise is it? Does it have a time dimension to it? You refer to deadlines later on. Does the roadmap include them? (What do deadlines really mean in a project like this anyhow?) Priority?
\subsubsection*{Motivation} This pattern shows how the group can define the scope of their project and make a realistic plan to address it. This pattern provides the backbone of our pattern language. It can be used to find a shared goal.
\subsubsection*{Context} \patternname{Peeragogy} has both distributed and centralized aspects. The discussants or contributors who collaborate on a project have different points of view and heterogeneous priorities, but they come together in conversations and joint activities.
% {\icon \symbol{"002127}}
% {\icon \symbol{"0021A9}}
\subsubsection*{Forces}~
\begin{tabular}[t]{p{.8\textwidth}@{\hspace{.03\textwidth}}c}
\textbf{Variety}: people have different goals and interests in mind. & {\icon \symbol{"0021D4}}\\
\textbf{Clarity}: some may be quite specific, and some rather vague. & {\icon \symbol{"0021A6}} \\
\textbf{Coherence}: only some of these goals will be well-aligned. & {\icon \symbol{"0021C2}}
\\
\end{tabular}
\subsubsection*{Problem} In order to collaborate, people need a way to share current, though incomplete, understanding of the space they are working in, and to nurture relationships with one another and the other elements of this space. At the outset, there may not even be a coherent vision for a project -- but a only loose collection of motivations and sentiments. Once the project is up and running, people are likely to pull in different directions.
\subsubsection*{Solution} Building a guide to the goals, activities, experiments and working methods can help \patternnameplural{Newcomer} and old-timers alike understand how the nature of their relationship with the project. %% This guide may be a research question or an outline, an organizational mission statement, or a business plan.
It may combine features of a manifesto, a syllabus, and an issue tracker. It may be a design pattern or a pattern language \cite{kohls2010structure}. The distinguishing qualities of a project \patternname{Roadmap} are that it should be adaptive to circumstances, and that it should ultimately get us from \emph{here} to \emph{there}. By this same token, any given version of the roadmap is seen as fallible. %% Everyone with an interest in the project should have the right to update it, although in practice not everyone will choose to do so.
% * <Charles Danoff> 15:21:53 29 Nov 2015 UTC-0600:
% Should we add the business canvas?
In lieu of widespread participation, the project's \patternname{Wrapper} should attempt to synthesize an accurate roadmap that is informed by participants' behavior, and should help moderate in case of conflict. Nevertheless, full consensus is not necessary: different goals, with different \emph{heres} and \emph{theres}, can be pursued separately, while maintaining communication.
\subsubsection*{Rationale}
% DK: This seems more like advice about how to implement the solution than it is an explanation of how the solution addresses the forces from the context/problem [jc: fixed]
In the Peeragogy project our initial roadmap was an outline of the
first draft of the \emph{Peeragogy Handbook}.
Later, it took the form
of a schedule of meetings following a regular
``\patternname{Heartbeat}'' supplemented by a list of upcoming
deadlines. Most recently, it is expressed in the emergent
objectives listed in Section \ref{sec:Distributed_Roadmap} of the
current paper. We have seen that a list of nice-to-have features created
in a top-down fashion is comparatively unlikely to \emph{go} anywhere.
A backlog of tasks and a realistic plan for accomplishing them are
vastly different things. An adaptive roadmap is an
antidote to \patternnameext{Tunnel Vision}
\cite[pp. 121--124]{david2001software}.
\subsubsection*{Resolution}
% DK: This seems like Rationale to me [jc: fixed]
An emergent roadmap is rooted in real problems and justifiable
solutions-in-progress in all their \textbf{variety} and communicates
both resolution and follow-through. The process of meshing varied
issues with one another requires thought and discussion, and this
encourages \textbf{clarity}. The test of \textbf{coherence} is that
% * <Charles Danoff> 15:40:10 29 Nov 2015 UTC-0600:
% lisa: getting everyone on the same page + clarity even if what you're doing is not clear
contributed goals and ideas should be actionable.
%
% - what happens if you don't have a roadmap?
The ultimate quality-control test is if it worked, i.e., did it come to pass that the task(s) the roadmap was created to achieve ended up being achieved, or not? If all of the issues that the roadmap outlines are not resolved, the roadmap itself should be revised. Without a roadmap, we would never know.
% https://en.wikipedia.org/wiki/Wikipedia:Cleaning_up_vandalism is another localized roadmap.
\subsubsection*{Example 1} The \emph{Help} link present on every Wikipedia page could be seen as a
localized \patternname{Roadmap} for individual user
engagement: it tells users what they can do withthe site, and gives instructions on how to do it.\footnote{\url{https://en.wikipedia.org/wiki/Help:Contents}}
%% It tells users what they can do on the site, and gives instructions
%% about how to do it:
%% \begin{quotation}
%% \noindent
%% I want to \emph{read} or \emph{find} an article \ldots;
%% I want to \emph{edit} an article \ldots;
%% I want to \emph{report a problem} with an article \ldots;
%% I want to \emph{create a new article} or \emph{upload media} \ldots;
%% I have a \emph{factual question}\ldots
%% ~[Etc.]
%% \end{quotation}
For someone who is prepared to jump in and get to work, there are
around 30 pages listing articles with various kinds of problems, for
example articles tagged with style issues, or ``orphaned'' articles
(i.e., articles with no links from other pages in the
encyclopedia).\footnote{\url{https://en.wikipedia.org/wiki/Category:Wikipedia_article_cleanup}}\textsuperscript{,}\footnote{\url{https://en.wikipedia.org/wiki/Category:Wikipedia_articles_with_style_issues}}\textsuperscript{,}\footnote{\url{https://en.wikipedia.org/wiki/Category:All_orphaned_articles}}
%
%
Wikimedia previously developed
a detailed strategic plan drawing on community input
\cite{wikimedia2011plan}. In 2015, a two-week
Community Consultation was carried out and
synthesized, resulting in ``a direction that will guide the decisions for the organization.''\footnote{\url{https://blog.wikimedia.org/2015/02/23/strategy-consultation/}}\textsuperscript{,}\footnote{\url{https://blog.wikimedia.org/2015/08/27/strategy-potential-mobile-multimedia-translation/}}
%
%
Community-organized WikiProjects often invite outside involvement on \patternname{A
specific project}.
%%%%%%%%%%%%%%%%%%%% Adjust spacing for wrapfigure
\begingroup
%\setlength{\intextsep}{0pt}%
\setlength{\columnsep}{6pt}%
\begin{wrapfigure}{r}{.32\textwidth}
\vspace{-.9cm}
{\centering
\includegraphics[width=.32\textwidth,trim=140 30 30 30, clip=true]{alabama-big}
\par}
\vspace{-.5cm}
\caption{President's Home, University of Alabama.
%Public domain.
\label{presidents-home}}
\vspace{-.8cm}
\end{wrapfigure}
\subsubsection*{Example 2}
In a future university run in a peer produced manner, a fancy
President's Residence presumably wouldn't be needed. Leadership would
be carried out in a more collaborative and distributed fashion.
However, depending on just how distributed things are, it may turn out
to be useful for project facilitators to gather at a University Hall.
Whereas there is strength in numbers, there is leverage in
organization. This is what the \patternname{Roadmap} provides.
\endgroup
\smallskip
\begin{framed}
\noindent
\emph{What's Next in the Peeragogy Project}
\definecollection{RoadmapWN}
\begin{collectinmacro}{\RoadmapWN}{}{}
If it becomes clear that something needs to change about the project, that is a clue that we might need to revise our patterns or record a new one. We can use the names of the patterns to tag our upcoming tasks.
\end{collectinmacro}
\RoadmapWN
\end{framed}
\newpage