project work on pervasive systemsprojekti/tie-proj_intro.pdf · 2015-08-25 · sprint plan harri...

Project Work On Pervasive

Systems

25.08.2015

Sten

Content

25.8.2015 Harri Sten / Opening slides 2

• What is this course ?

• Goals & Content

• Motivation

• What’s most important in SW Project ?

• Key issues of SW Project

• Course schedule – deadlines

• About the SW project implementation

• Softty organization & roles

• Real SW project & customer

• Forming groups

• International students

• Group actions

• Agile & Processes

• Sprint plan

• Documents & Disciplines

• Customer relations

• Lectures & Workshops

• Learn from others

• Grading & Requirements

• People here to help you

• What now ? Next week ?

What is this course ?


Theory

and

Working

Practises

of

SW Project

Implementation

of

Actual

SW Project

Learnings

for

coming

SW Projects

Learnings & experiences from earlier studies & work

experience (SWD, UX, HW, Sec)

Goals & Content ?


• Goals

• Learn SW project work content – What’s in there ?

• Learn working process in SW projects – Phases, deadlines, etc

• Learn to apply knowledge from previous courses in practise – e.g. Software

Engineering Methodology

• Learn how to work as a team – project team

• Learn how to work with customer – customer collaboration

• Learn how to work in SW organization – Our course organization

• Learn to design and implement real working product

• Learn to do inevitable bureaucracy (documents, reports, reviews, etc)

• Content

• Starting a project

• Requirements management & Project management Project plan

• Product & sprint backlogs up-to-date

• Describe requirements & environment modeling

• Implementation & reviews code and code & pair reviews

• Quality assurance test planning, testing & testing results

• Delivery ready working SW to customer

• Ending the project Updated plan vs working stuff (demo/reviews)

Motivation part

25.8.2015 04.08.2015 / Harri Sten / Opening slides 5

• Prepare your self for

– Real touch to SW Business Real projects from real

companies

– New contacts to SW business companies (job

opportunities ?)

– Hard work Good results

– Positive and negative learning experiences

– Team work, commitment, (no free-riders)

– Celebration at the end

Project work


Thousands of different kind of implementations, products,

projects, teams, processes, environments, etc…

How’s your

project going

on?

It’s like a

steaming

nuclear power

plant ! It’s like fifteen

drunken

monkeys with a

jigsaw puzzle !

Boss

How’s your

project going

on?

Fine !

Colleague Project manager

Project work - Important


3. Execution 4. Teamwork

1. Customer 2. Requirements

Project work – Key issues


Schedule – deadlines


25.8 Course starting lecture / mandatory (CEO Harri Sten, CQO Tero Ahtee, TE Matti Vuori)

25.8-4.9. Groups are formed by students

1.9 Lecture 2 / mandatory: Customer pitches. Customers will tell shortly about their topics. (CEO, Customers)

4.9 Deadline: Teams formed and topic picked. Sprint zero begins.

8.9. Lecture 3 / mandatory : Overall SW project & Best project last year (CEO Harri Sten, TBD)

11.9 Deadline: Groups should have had held a kick-off meeting with course staff (PCs & co)

15.9. Lecture 4 / mandatory : Requirements and Customer & legal issues (CQO Tero Ahtee)

22.9. Lecture 5 / mandatory : Roles and responsibilities (CQO Tero Ahtee)

29.9. Lecture 6 / not mandatory : Acute issues / PPlan & Reqs (CQO Tero Ahtee, TE Matti Vuori + PCs)

2.10. Deadline: Absolute deadline for ending sprint zero (project plan, requirements)

6.10. Lecture 7 / not mandatory : Project Management in SWP (CQO Tero Ahtee)

Exam week (12.-18.10.)

20.10. Lecture 8 / not mandatory : UX and UI & Security (TE Thomas Olsson & TE Marko Helenius)

27.10. Lecture 9 / not mandatory : Acute issues / implementation (CQO Tero Ahtee, TE Matti Vuori + PCs)

3.11. Mid-presentations /mandatory : (All)

10.11. Visiting lecture 1 / mandatory : TBD (e.g. customer project related)

17.11. Lecture 10 / not mandatory : QA in SW project (TE Matti Vuori, TE Thomas Olsson)

24.11. Visiting lecture 2 / mandatory : TBD (e.g. Implementation of SWP)

1.12. Lecture 11 / not mandatory : Acute issues. Preparation for Christmas break (CQO Tero Ahtee, TE Matti Vuori + PCs)

11.-15.1. Audit with PCs & support by TE Matti Vuori

12.1. Lecture 12 / not mandatory : Acute issues / Finalysing & Course ending (CQO Tero Ahtee, TE Matti Vuori + PCs)

19.1. Lecture 13 / not mandatory : Entrepreneurship (Jaakko Sairanen)

25.1. Deadline : Product / Project ready (delivery to customer)

26.1. Lecture 14 / not mandatory : Distribution of SWP & Famous IT projects(CEO Harri Sten, CQO Tero Ahtee)

25.-29.1. Product check with PCs & CQO (Demo, test results, etc)

2.2. Deadline: for Project report

5.2. Final presentations (mandatory, whole day event) & evening party (All, possibly at Teekkarisauna)

8.- 19.2. Final meetings: with course staff (assistant and/or someone else) (mandatory)

About the SW project

implementation

-this course


25.8.2015 Harri Sten / xx 11

Softtty

Organization Harri Sten

CEO

Laura Hokkanen

Project Coach, TE

NN

Project Coach, TE

Marko Leppänen

Project Coach, TE

Teemu Laukkarinen, TE

Project Coach

Tero Ahtee

CQO

Technology Experts

Matti Vuori

Marko Helenius

Jarmo Palviainen

Thomas Olsson

Project 1

Project 2

Project 3

Project …

Harri Sten / Opening slides 25.8.2015 11


Roles & Responsibilities

CEO

• Chief Executive Officer, General management, course management, high level company

collaboration, business perspective, etc

CQO

• Chief Quality Officer, course technology, most of lectures, project work, communication, etc

TE

• Technology Expert, technology lectures & coaching, etc

PC

• Project Coach, coaching of project teams, reporting, problem solving, customer collaboration,

student reviews, etc

PM

• Project Manager, project lead, schedule, task management, planning, other project work,

customer collaboration, contact person for course, etc

PO

• Product Owner, requirement lead, customer collaboration, product backlog, etc

SM

• Scrum Master, sprint backlog, tasks, burndown chart, etc

QA Lead

• Quality Assurance Lead, testing, test planning, testcases, etc

TECH lead

• Technical lead, technology issues, architecture, etc

SW Engineer

• SW planning, development, testing, analysing code, review, etc

25.8.2015 13

Meetings

Board meetings (CEO, CQO, Technology Expert Matti Vuori and Kari Systa)

• Bi-weekly / when needed

• Course high level issues, grades, promlem solving, etc

Mgmt meetings (CEO, CQO, Project Coachs (PC), Technology Experts)

• Weekly / Bi-weekly

• Project level problems, status, schedule issues, contant issues, etc

Project meetings (Project Manager (PM), Team, PC)

• Weekly / Bi-weekly

• Project status, project issues & problems, etc

Sprint meeting (PM, Team, PC, Customer)

• End of sprint

• Product & Sprint report, demo, product & sprint backlog planning, etc

Project team meeting (Project members only)

• When needed

• Project related issues (schedule & content & Quality)

Harri Sten / Opening slides

Project Coach

Role & Responsibilities

25.8.2015 Harri Sten / Coach role & resp 14

• Help team to start their work

• To support team during project

• Coach for project related issues

• Coach process related issues

• Coach for team & roles related issues

• Review project & product related issues

• Support team to prepare documents, presentations, etc

• Ensure & support team to achieve deadline

• Evaluate team’s & individual’s performance

• Support to establish & maintain customer relationship

• Help & guide in problems & conflicts

• Help course to achieve it’s targets

Real SW project &

customer


• In this course we are working in real business environment

• We have several real customer projects & topics

• From real companies

• For you to pick-up one to implement

• Size and content of projects varies (number of credits depends

on your project hour log needed)

• Some projects require special skills (UX, HW, Security, etc)

• You are working with real customer in real business environment

• Act like it as well !

• Topics will be presented next week this time (1.9. Tuesday)

• When you have selected your topic / project

• Inform course CEO & CQO about your choice

• Then wait for approval from course management

• Contact to customer

• Start the project…

• Be sure to establish meetings after every sprint for demo and

feedback with the customer

Forming groups


• Preferable group size is 5 persons

• Make use of your expertise and different expertise of

others

• A group must have at least these assigned roles

• PM – Project Manager

• PO – Product Owner

• SM - Scrum Master

• QA Lead

• Tech Lead / Architect

Note: One person can /need to have several roles

Note: All are also doing implementation work

• Group formation deadline is 4.9. (Next week’s Friday)

• More details can found from course web site…

International students


• We have here some international students

• They should join groups with Finnish students

• Every group should have at least two Finnish speaking

students

• Finns: Please, invite international students to join – this is a

learning opportunity for both parties

Group actions


• One of the first action is to create web site for project team

• Basic info about team members, selected project,

reported hours, etc (more info from web)

• Create Project Highlights

• Sent weekly to CEO, Tero Ahtee and your own Project

Coach deadline every Monday 8pm

• Not more than one A4 with current status (just text, no

attachments), what’s new, what’s happening near

future, risks/problems, each persons weekly hour

sum/cumulative hours, etc

• More info from web

• Weekly / BI-weekly meetings with with team & Coach

• Note: All kind of templates available via web pages

Agile & Processes


• Selected development process in this course is Agile / Scrum *

• With roles earlier defined, back,logs, sprints, demos, etc

• Here is common sprints & schedule for your project:

2015 2016

Sep Oct Nov Dec Jan Feb

Sprint 0

Sprint 1

Sprint X

Sprint 2 Sprint 3

Sprint 4

Definiton

& reqs

Implementation Phase

QA

phase

Final

Project

start

Planning

ready

Mid-

presentation

Implement

ready

Course

ready Product

ready

We

are

here

* Preferred method, but needs to be evaluated case by case

Sprint plan


• Number of sprints free to choose – what works best for you and your

customer

• Create sprint backlog for every sprint (no changes during to sprint)

• Example:

• Sprint 0

• Customer contact, requirements, modeling, product backlog

• Sprint 1-2

• Implementation, update reqs, first features done, some

prototype, Mid-presentation

• Sprint 3-4-5

• Implementation, code reviews, update regs, Xmas break

• Sprint X

• Final sprint, testing, error correction, preparing delivery

• Sprint x+1

• Final presentations, final customer meetings, demo of

complete product, project ending phase

Customer relations

25.8.2015 21

• Make contact with the customer as soon as possible

(group formed, staff gives a signal)

• Be sure to establish meetings after every sprint for demo

and feedback

• Make sure the customer is prepared to sign off the

project at the last meeting in February

Disciplines &Documents


• Disciplines

• Following phases are included to SW development & delivery to

customer – Requirements management, Modeling, Implementation

(coding), Testing and Delivery

• Two other actions – Project management and Processing working

results – are related to support other primary activities

• Documents

• Project plan with Project plan, details, goals, requirements, resources,

schedule, etc deadline 2.10.

• Mid-Presentation (ppt/pdf) with project & product status, early demo,

working hours, etc 3.11.

• Delivery report to customer with content, intructions, plan vs actuals,

code, etc deadline 26.1. (delivery)

• Final project report to personel (CEO, CQO, Coach) deadline 2.2.

Lectures & workshops


• This course mainly consist of lectures and project work

• Lectures (3 types: basic, special, visiting)

• Mandatory lectures (focus in early phase)

• Course starting lecture (today 25.8.)

• Customer pitches (1.9.)

• Overall SW project & Best project last year (8.9.)

• Requirements & Customer (15.9.)

• Roles & responsibilities in SW project (22.9.)

• Mid-presentations (3.11.)

• Visiting lecture 1 TBD (10.11.)

• Visiting lecture 2 TBD (24.11.)

• Final presentations, whole day event & evening party (5.2.)

• Final meetings (8.-19.2.)

• Voluntary lectures

• Acute issues / focus on PPlan & Reqs (29.9.)

• Project Management in SW Project (6.10)

• UX and UI & Security (20.10.)

• Acute issues / focus on implementation (27.10)

• QA in SW project (17.11.)

• Acute issues / focus on preparation for Xmas break (1.12.)

• Acute issues / Finalysing project & Course ending (12.1.)

• Entrepreneurship (19.1.)

• Distribution of SWP & Famous IT projects (26.1.)

Learn from others


• You have an unique opportunity to learn from others in your

group

• From management, process and implementation decisions

they make

• You have an unique opportunity to follow & learn from ~10

others project follow closely

• Possibility also to peer feedback will be provided

Grading & requirements


• Pass / Fail. In order to pass

• Documents delivered on time

• Project highlights provided weekly

• Project/Product successfully completed

• Customer’s ”stamp of approval”

• Participation in mandatory events

• Kaiku feedback given

• Course is 5-10 credit points. Credit points are mainly given

based on spent working hours. Approximately 125 hours will

give 5 cu and 250 hours the 10 cu.

• However, the course personnel will check how the hours were

used (emphasis on there should be work, not 100 hours on

sitting at lectures and ambiguous wondering).

• We will also consider the process and the end product.

People here to help you


• CEO, Harri Sten

• Course high level issues, feedback about course,

etc

• CQO, Tero ”Tensu” Ahtee

• Most lectures, reviews, etc

• TE, Technology Expert

• Matti Vuori, Jarmo Palviainen, Marko Helenius,

Thomas Olsson

• Expertise of certain technology, lectures , etc

• PC, Project Coach

• Laura Hokkanen, Marko Leppänen, Teemu

Laukkarinen, NN

What now ? –

Next week ?


• A lot of information today in short time (see website)

• What you need to do NOW !

• Form team by Friday 4.9.

• Come and listen pitches next week and

• Pick topic to implement by 4.9.

• Check course website for schedule and other information !

• Next week (1.9.) company representatives pitch for their topics

(starting at regular time 16:15-)

• Opportunity for you to ask more questions after the session

• Last chance to form groups around a topic – Deadline 4.9.

Take your responsibility !
