Internship Project

Requirements
As an Internship Coordinator I want to be able to define an Internship Program with different
streams having separate training plans
Each training Plan needs to have a set of topics with a set of exercises for each topic.

It should be possible to split the topics per phases

It should be possible to add attachments to the exercises

As an IC I want to be able to re-use an internship program

As an IC I want to be able to assign people to different streams and automatically allocate an
defined training program to the individual
As an IC I need to split the training program per sprints(e.g. weeks)

As an IC, and Mentor, I need to monitor the progress of the interns

As an IC I need to know what training sessions have been done and what is outstanding

Confluence

 What is internship in AM and how is it all going inside – that’s what our project is about.
Structured version of everything every stream had. Our interns will use Jira and Confluence,
their progress to be more transparent for their mentors and Int’s Coordinator. Also they will
have a clear image of their tasks and their due dates (nobody to say “HEY, I forgot. Sorry,
duuuudes ”)

 So let’s start with the Confluence.

Here we have:
a. Exactly as Internship in Endava’s AM, the Space in Confluence is divided in two
phases.

b. Weekly reporting is also mentioned here. With the details each intern need to
provide to the coordinators.

c. As soon as a specific training starts, the mentor will make it visible/available for
streams which need to attend it.
d. Each main page of the training has general information about it. Also the mentor
can track the progress of the tasks for the interns (right here)
e. Each presentation will have it’s own sub-page. Here you can find the training’s
material, as well the list of task (if there are any)
 f. Each mentor will be able to edit the pages of his trainings. So the information will be
constantly updated.

g. Phase two – projects.

h. Here you can find the stories need to be done for the project and some comments on
the process.
i. Page for mentors only. It consists of schedule of the trainings which are divided by
streams. A table with the names of all interns (also divided by streams). And an excel
for IC to load all the trainings at the beginning of the internship.

JIRA
 As you could notice each training asks the intern to move a task to “In Review” when it
was done. And to “Done”, when it was approved by mentor.
So let’s switch to Jira.

a. In JIRA there are 3 different boards. The first one is the Agile board, and the main
purpose of it is for mentors to be able to create sprints. Another one is the Kanban
board where you can easily check the progress of the interns. The filters which you
can find on top were set up on streams and phases. The third dashboard which is
visible only for the IC and our mentors will show you what training sessions have
already happened and which ones still have to be done.
b. What kind of tasks should interns have in JIRA? Being interns we understood how
important is time management and how challenging it is to keep in mind the load of
our tasks. We have solved this issue – now mentors will create tasks for all the
interns at the end of the trainings. You might think that it is insane to create
manually tasks for a bunch of people. The solution is simple – import an easy
configurable Excel file. We have designed a special guide in Confluence on how to
do that. The same thing applies to mentors. At the beginning of the internship we
will import all the training sessions that need to be done and as soon as you held it –
change its status.
c. Another helpful feature is the filter that will send interns notifications about tasks
that are up to 3 days close to the due date. If he didn’t manage to do it, his mentor
will receive an email notification.
d. We have a dashboard shared by mentors and Marin with some statistics.
e. reusability