-
Notifications
You must be signed in to change notification settings - Fork 14
/
Copy pathmilestones.tex
89 lines (81 loc) · 3.47 KB
/
milestones.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
\eucommentary{Milestones means control points in the project that help to chart progress. Milestones may
correspond to the completion of a key deliverable, allowing the next phase of the work to begin.
They may also be needed at intermediary points so that, if problems have arisen, corrective
measures can be taken. A milestone may be a critical decision point in the project where, for
example, the consortium must decide which of several technologies to adopt for further
development.}
\paragraph{General Milestones}
\begin{milestones}
\milestone[
id=startup,
month=12,
verif={
Completed all corresponding deliverables
and preparation for deployment of prototype services is underway
}
]
{Startup, requirements, and prototype generic Jupyter service}
{
By milestone 1, we will have established the infrastructure
for the project and begun prototyping development and deployment of services,
engaging with the existing communities,
coordinating plans for \TheProject with those of the wider Jupyter and open science communities,
and prototyping operation of a generic Jupyter service
for Open Science.
EGI Infrastructure-as-a-Service (IaaS) cloud resources will be available with a
Service Level Agreement (SLA) for \TheProject.
}
\milestone[
id=prototype,
month=24,
verif={
Completed all corresponding deliverables and early users are able to access and test prototype services
}
]
{Generic Jupyter service and early local demonstrators}
{
By milestone 2, we will have deployed a generic Jupyter service for Open Science, and begun to experiment with early-adopter
users and local demonstrators to guide further development of \TheProject,
ensuring that development serves the needs of the community.
An initial \TheProject Service Management System shall be available,
and \TheProject services will be integrated with the EOSC Marketplace,
and AAI Cloud services.
}
\milestone[
id=community,
month=36,
verif={Completed all corresponding deliverables and services
are operational and ready for public testing}
]
{Demonstrator services and community engagement}
{
By milestone 3, demonstrator services should be useful and accessible
to a broad range of users.
By this point, we will have training materials and run
workshops to train users in Open Science,
making use of operational \TheProject services,
gathering feedback to guide the further development of \TheProject.
The \TheProject Service Management System will be fully compliant with
the EOSC Service Management practices.
}
\milestone[
id=final,
month=48,
verif={Completed all corresponding deliverables and reported progress at the final project review}
]
{Full EOSC integration, adoption, sustainability, and evaluation}
{
By this point, all \TheProject services should be operational, available via EOSC-hub,
and the generic Jupyter service TRL 8.
Through community engagement via workshops, conferences, and other media,
the services should have established groups of users,
benefiting from these services and improving the Open Science landscape
on EOSC and beyond.
At the end of the project,
we will have engaged with the community to evaluate
the prototype EOSC services,
identified which services and tools shall be sustained beyond the life of the project,
and developed a sustainability plan for
how this may be achieved under community support and leadership.
}
\end{milestones}