1. Time Management and Teamwork (a.k.a. “Software Project”)
MTAT
Time Management and Teamwork
(a.k.a. “Software Project”)
Coordinator: Marlon Dumas Mentors: Jaanus Jaggo, Volodymyr Leno, Mikhaylo (Michael) Dorokhov

2. Not an ordinary course
Very few lectures
Two lectures about requirements and UI design + two demo sessions
Lots of teamwork (about 150 hours per member, 600 per team)
Lots of mentoring – weekly meetings with mentors start next week
Mentors are will clarify what needs to be achieved by when, will help you resolve conflicts and mediate problematic soituations, and will assess your deliverables
Lots of online communication…
Please make sure you configure your Google groups settings so that you receive at least “abridged” version of messages

3. (Almost) everything you want to know or ask should be here…
Course web page:
Google forum:

4. Development and collaboration infrastructure
Every team must set up a development/collaboration infrastructure
Min requirements:
Version Control System (VCS), e.g. git
Issue tracker
Wiki
Continuous Integration
GitLab is recommended, Github or BitBucket are alternatives but they need to be combined with a CI platform (e.g. Travis, Shippable)
It’s your choice, you set it up and then grant access to your mentor
For CI of mobile apps, we recommend using a free NeverCode.io account

5. Development and collaboration infrastructure (cont.)
We can provide:
A Linux Ubuntu or CentOS bare-bones virtual server with 2 cores, 2 GB RAM, 20GB Disk in University of Tartu’s cloud (available with VPN access only)
If you need more capacity (CPUs, RAM), ask, but not sure we can provide it
If you need external IP address (to show to your customer), please ask upfront
Drop me an to make your virtual server request
But you can also use another deployment infrastructure, e.g.
Engine Yard for PHP/Ruby/Node.js
Heroku for Java/Ruby (a bit limited though)
DigitalOcean – you can get $100 credits by applying for a GitHub education pack

6. Development and collaboration infrastructure (cont.)
Docker for CI is allowed
Normally, your CI process should end in a deployed/executable application
However, producing a docker image in Docker Hub and “manually” pulling it into your deployment server on UT’s cloud is OK

7. Working Principles Transparency Traceability Reproducibility
Anything that is not in your dev and collaboration infrastructure does not exist.
Any server-side application that is not running on a server does not exist.
Traceability
Every commit must be linked to an issue
Where applicable, every issue must be linked to a requirement documented in Wiki
Reproducibility
A person having ordinary skill in the art (PHOSITA) should be able to build and test your app from the source code with reasonable effort. Your mentor is a POSHITA.
Continuous Integration (CI)
On the end, every commit should lead to a new tested & deployed version of the system

8. What to do now/next?
Choose your project & contact your customer by Friday 8am
I will send you the contact details by Friday at 12:00
Agree on a first meeting
Prepare for your meeting – read the project description, prepare your meeting, do some searches online to get info, check for possible approaches, think about possible requirements, prepare questions
Read the grading criteria (at least for iteration 1)
Reminder: Iteration 1 deadline is 25 September

9. Past examples of very good projects