Internet Praktikum TK (6CP)17.10.2019 Internet Praktikum Telecooperation (6CP) 26 Sprint Agenda • Sprint 00 –Planning (Thu, 24.10.19, >13:00*, AHG 07) • We (the customer) will

Internet Praktikum Telecooperation (6CP)17.10.2019 1

Internet Praktikum TK (6CP)

Kickoff Meeting


Lecturers

Christian Meurisch

[email protected]

S2/02 A112


Lecturers

Sebastian Kauschke

[email protected]

S2/02 D202


General Remarks

• Main objectives of this course

• Learning about mobile & backend development

• Implementing your own project

• Type: P4, 6CPs (20-00-0131-pr)

• Teamwork!! ~4-5 students per group

• At the end, we expect...

• build-/runnable apps (.apk), documented code (> 2 days before)

• technical documentation (> 10 pages, TUD template, 11pt)

• final presentation (i.e., 1min pitch/promotion video + live demo)

1CP = 25-30h / student

6CP = 150-180h / student


Grading – "How to be successful?"

• Submit ALL the required work (i.e., code, docu, pitch)

• Present a WORKING prototype of your app

• Be creative, do things AWESOME😃


TOPIC WS19/20


Fitness & Health


Fitness & Health

▪ Activity Dashboard

▪ Movement (incl. distance)

▪ Excercise (e.g., walk)

▪ Step count

▪ Calorie estimation

▪ Stand hourly

▪ History


Fitness & HealthWorkouts

▪ Workout tracking

▪ Some stats

▪ Map visualization


Fitness & Health(Social) Incentives

▪ Internal Incentives

▪ Achievements

▪ External/social Incentives

▪ Awards

▪ Rankings


Fitness & Health"Hidden" Features

▪ 24/7 User Tracking

▪ activity

▪ location

▪ steps

▪ User Management / Sharing

▪ including a backend system

▪ Bonus, e.g.,

▪ sleep behavior

▪ "smart" recommendations

▪ web-based NSA dashboard


Course Mode

• Teams of 4-5 people

• Scrum-like process• We act as customers

• Stefan is the product owner

• Will be more work in the beginning of the semester!• But less work in the end, when the exams are!


Scrum roles

A scrum team consists of

• Scrum Master

• Product Owner

• Development Team

And

• The Customer


Role: Customer

Who: Christian and Sebastian

Our goals are:

• We want to have the best product possible

• We have some ideas about its functionality

• We are not „know-it-alls“• Require suggestions of the development team, how something has to be

built


Role: Product Owner

Who: Stefan Wullkotte (the tutor)

• Responsible for maximising the value of the product

• Responsible for Product Backlog Management• Orders the backlog items by priority

• Ensures all items are clearly stated

• Ensures, dev team understands what the items mean


Role: Scrum Master

Who: A member of dev team (not ideal)

• Ensures proper execution of scrum

• Keeps team members on track

• Deals with the product owner when things are unclear


Role: Development Team

Who: All Developers

• Self-Organizing• Decides how to handle the product backlog themselves

• Cross-functional• Every member has the competency to fulfill any task

• No sub-teams

• Deliver product iteratively and incrementally


Scrum practices

• Weekly meetings

• Continuous integration (avoid incompatible assumptions)

• Retrospective (reflect on experiences and lessons learned)

• Shared code ownership (whole team is responsible for code)

• Coding standards: common style rules


Scrum Events

• Scrum consists of Sprints• Defined what is to be built next

• Time boxed (1 month or less)

• Only product owner can cancel sprint

• Consists of• Sprint planning

• Daily scrums

• Development

• Sprint review

• Sprint retrospective


Sprint Planning

• Determine Sprint Goal• Defined by the whole scrum team

• Input: the (ordered) product backlog

• Output: a sprint backlog• Select items from product backlog for the sprint

• Team can select the amount of items


Daily Scrums (we are doing weekly)

• 15min per day

• Participants: Dev Team

• Purpose• Synchronize activities, create plan for next day

• Inspect progress and adapt

• Each member explains• What did I do yesterday, what will I do today

• What difficulties am I facing


Sprint Review

Who: Scrum Team & Customer

Agenda:

• Product Demonstration (Team shows their software)• Answer questions of customers

• Present what went well and which problems occured

• Product owner declares whats done

• Customer Feedback

• Discussion: What is next? • Result: revised product Backlog

• Undone items go back into the backlog


The Scrum Product Backlog

• Ordered list of everything that might be needed in the product• Features

• Functions

• Requirements

• Enhancements

• Fixes, etc…

• Dynamic (requirements may change)

• Exists as long as the product exists


Task board example

• Initial tasks are identified by theteam during sprint planning

• Additional tasks are discoveredduring sprint execution

• Only tasks that fit inside the sprintscope are added here


Scrum Workflow

*original source: Wikipedia

7 days

~4 weeks

A running software, incrementally improved

Weekly scrum


Sprint Agenda

• Sprint 00 – Planning (Thu, 24.10.19, >13:00*, AHG 07)

• We (the customer) will present you our idea

• In the first sprint, you are supposed to prepare the project, find suitable libraries, write down userstories/tasks, make mockups, etc.

• Sprint 01 (Thu, 21.11.19, >13:00*, AHG 07)

• Retrospective Sprint 00, Planning Sprint 01

• Actual development starts

• Sprint 02 (Thu, 19.12.19, >13:00*, AHG 07)

• Sprint 03 (Thu, 23.01.20, >13:00*, AHG 07)

• Sprint 04 (Thu, 20.02.20, >13:00*, AHG 07)

• Submission deadline (Tue, 17.03.20, 23:59 CEST, Online)

• Final presentation (Thu, 19.03.20, 13:00, AHG 07)

*Doodle (30min time slot)


Weekly Scrum

• Mandatory meetings with Stefan• In his consultation hours

• Supposed to keep development on track

• Stefan is also there to help you with issues regarding theprogramming! ASK HIM!


Scrum: further reading

http://agilemanifesto.org/

https://www.scrumguides.org/

Bertrand Meyer: Agile! The Good, the Hype and the Ugly, Springer, 2014

http://agilemanifesto.org/

https://www.scrumguides.org/


Orga Stuff – GitLab

• GitLab platform (RWTH Aachen)

• Login with your TU-ID is necessary

(using RWTH Single-Sign-On)

• Purpose of use• overview of recent activities (+ news)

• two discussion forums: organizational + technical issues

• common git repository containing both code examples and slides

• your group workspace (incl. git repo)

• Pls use the git repository to merge your code• Each team member should contribute to the project (> git commits)

https://git.rwth-aachen.de


Orga Stuff – Tutor

• Regular consulting hours• when? – weekly (starting from October 29)

• where? – S2|02 A313 (see next slide for details)

• Digital support• general questions: GitLab forum

• specific questions: email to Stefan ([email protected])

• Pls ask Stefan first if you have any technical or understanding issues

Stefan Wullkotte


Orga Stuff – Tutor hours/rooms

17:15 - Tuesday 29 October 2019 | S2|02 A313

17:15 - Tuesday 05 November 2019 | S2|02 A313




17:15 - Tuesday 03 December 2019 | S2|02 A313



🎄🎁 *** CHRISTMAS BREAK *** ☃️🎉

17:15 - Tuesday 14 January 2020 | S2|02 A313



17:15 - Tuesday 04 February 2020 | S2|02 A313




17:15 - Tuesday 03 March 2020 | S2|02 A313

17:15 - Tuesday 10 March 2020 | S2|02 A313

17:15 - Tuesday 17 March 2020 | S2|02 A313

At least * 10 * (out of 18) MUST be visited.


Orga Stuff – Agenda (ignore Tucan :)

• Kickoff: topic presentation (Wed, 16.10.19, 17:10, C120)

• Sprint 00 – Planning (Thu, 24.10.19, >13:00*, AHG=S1|03 07) → 4 weeks

• Sprint 01 (Thu, 21.11.19, >13:00*, AHG 07) → 4 weeks


--------------------------- (christmas break) -------------------------------------


--------------------------- (end of lectures, exam time) --------------------------


• Submission deadline (Tue, 17.03.20, 23:59 CEST, Online)

• Final presentation (Thu, 19.03.20, 13:00, AHG S1|03 07)

* Doodle (30min time slot)


Orga Stuff – Your Next Steps

• FILL OUT the registration form until SUNDAY, 20.10.19• Team members: name, matriculation number, email, Android phone?

• Building groups in advance (~4-5 students)

• ONE registration per group (https://forms.gle/AiMTdrc2qbwzuqmz9)

• LOG IN to the GitLab w/ your TUDA university account• https://git.rwth-aachen.de

• at latest by SUNDAY, 20.10.19

• FAMILIARIZE yourself with the project topic


Thanks for your attentionQuestions?


See you NEXT ThursdaySprint 00 (Planning): Thu, 24.10.19, >13:00 (Doodle), AHG 07

Documents

Internet Praktikum TK (6CP)17.10.2019 Internet Praktikum Telecooperation (6CP) 26 Sprint Agenda • Sprint 00 –Planning (Thu, 24.10.19, >13:00*, AHG 07) • We (the customer) will