university of tampere faculty of natural …€¢ final meeting, final report + test report. ......
TRANSCRIPT
UTA.FI/LUO
Luonnontieteiden tiedekuntaTampereen yliopisto
FACULTY OF NATURAL SCIENCES
UNIVERSITY OF TAMPERE
UTA.FI/LUO
TIEA4 and TIETS19 Practice
• TIETS19 Software Project Management (Practice), 5-10 ECTS
• TIEA4 Project Work, 5-10 ECTS
• Periods I and II (and partially III)
• Staff:• Lecturer: Timo Poranen ([email protected], B1023)
• Project supervisor: Pekka Mäkiaho ([email protected])
• Course homepage: http://www.uta.fi/sis/tie/pw/index.html
8.9.2017 2Faculty of Natural Sciences
UTA.FI/LUO
Lecture 8.9.2017
• Staff, lectures/presentations, definitions
• Contents of the course
• Previous projects
• Prerequisites of the courses
• Learning outcomes and benefits
• Grading, credits and requirements
• Schedule, first meeting with the team
• Guidance and duties, working hour reporting
• Tools and tool training
• Project plan and project plan inspection, Reviews
• Next Friday: Scrum, Finishing the project, Requirements management
8.9.2017 3Faculty of Natural Sciences
UTA.FI/LUO
Lectures / presentations
• SPM+PW, lecture on Friday, 8.9, B3116, 10:15-12.
• SPM+PW, lecture on Friday, 15.9, B3116 10:15-12.• Scrum, Requirements management, Finishing the project
• Problematic project situations -workshop
• SPM+PW, lecture on Friday, 22.9, B3116 10:15-13.• Short project presentations by teams
• Metrics Monitoring Tool demo (Pekka Mäkiaho / Murat Pojon)
• Tool guidance
• SPM+PW, final project presentations, Wednesday, 10.1.2018, 10-?, SimSpace? Time will be confirmed later.
8.9.2017 4Faculty of Natural Sciences
UTA.FI/LUO
Definitions (PMBOK)
• A project is a temporary endeavor to create a unique product, service or result.• Projects are usually time-constrained, and often constrained by funding or
deliverables.
• Project management is the application of knowledge, skills, tools, and techniques to project activities to meet the project requirements.• Project management is accomplished through the appropriate application
and integration of project management processes, which are categorisedinto five process groups: Initiating, planning, executing, monitoring and controlling, and closing.
8.9.2017 5Faculty of Natural Sciences
UTA.FI/LUO
Contents of the course shortly
• There is a client who has suggested a project topic.
• 1-2 PMs manage a 3-5 developers project team to achieve such a software product that satisfies the client’s reasonable wishes.
• Periods I and II (deadline is 14th of January 2018).
• All projects choose their:• Tools, meeting and working practices.
• Development model and how it is applied in your project (iterative, Scrum, other agile software development models and methods,...).
• Freedom to decide many things but a lot of responsibilities!
8.9.2017 6Faculty of Natural Sciences
UTA.FI/LUO
Projects from previous years
• Finished projects and project videos and posters:• http://www.uta.fi/sis/tie/pw/previous-projects.html
• Työelämäsimulaattori (Tilannehallinta - ”Situation management” application).• Schedule, tools, roles, teamwork, risks, methods, experiences.
• Project posters.
8.9.2017 7Faculty of Natural Sciences
UTA.FI/LUO
TIEA4 Prerequisites
• http://www.uta.fi/sis/tie/pw/curriculum.html
• At least 50 ECTS credits. Level: 3rd year.
• Recommended previous studies:• Basic Studies in Computer Sciences, Introduction to Object-Oriented
Programming, Software Engineering, WWW Programming, Usability Evaluation Methods, Graphical User Interface Design Project
• Required in bachelor's studies.
• Project work can be compensated with Innovation Project (LUOYA200).
8.9.2017 8Faculty of Natural Sciences
UTA.FI/LUO
TIETS19 Practice prerequisites
• PW or Innovation Project (Demola project).
• Software Project Management – Theory.• Can be studied at the same time.
• Compulsory course in Software Development master's program.
• Can be done also by managing a Demola project (with the same prerequisites), more information from: http://www.uta.fi/sis/yhteiset/innovaatioprojekti/index.html
8.9.2017 9Faculty of Natural Sciences
UTA.FI/LUO
Learning outcomes – TIEA4
After completing the course a student is expected to be able to:
• Know basics of project based work and can participate as a group member in a software development project.
• Know most common software development models, their phasesand deliverables.
• Can present orally project outcomes and write project documentation.
• Can take account ethical requirements related to project work.
• Know basic concepts related to software development and quality, and can take them account in project work.
8.9.2017 10Faculty of Natural Sciences
UTA.FI/LUO
Learning outcomes – TIETS19 Practice
After completing the course a student is expected to be able to:
• Participate in a software development project as a project manager.
• Take responsibility of a project team and project organisation.
• Apply theoretical knowledge on project management and software development into practice.
• Be well aware on ethical issues related to software project management and can apply this ethical knowledge in practical situations.
• Understands how different management and development practices affect software and process quality.
8.9.2017 Faculty of Natural Sciences 11
UTA.FI/LUO
Benefits
• Better project working (management) capabilities and skills for (work) life.
• Reference:• http://www.uta.fi/sis/tie/pw/previous-projects.html
• Project poster
• 5-10 ECTS.
• A lot of practical experience on software projects.
• Your work is a challence: after the project, you should have a senseof achievement.
• It is fun!
8.9.2017 Faculty of Natural Sciences 12
UTA.FI/LUO
Grading, credits and requirements
• Grading and credits• http://www.uta.fi/sis/tie/pw/guidelines.html#credits-and-grading
• Compulsory documents:• http://www.uta.fi/sis/tie/pw/documents.html
• Two Moodle questionnaires. In November and in January.
8.9.2017 Faculty of Natural Sciences 13
UTA.FI/LUO
Schedule and statistics
• Schedule: http://www.uta.fi/sis/tie/pw/schedule.html
• Meetings with the course staff:• http://www.uta.fi/sis/tie/pw/guidelines.html#meeting-with-the-course-
staff
• First meeting with the team:• http://www.uta.fi/sis/tie/pw/guidelines.html#First-meeting-with-the-team
• Statistics: http://www.uta.fi/sis/tie/pw/statistics.html
8.9.2017 Faculty of Natural Sciences 14
UTA.FI/LUO
Duties
• Project managers (PMs) have more responsibilities. However, who actually implements an individual task, can be decided inside theteam.
• Project manager is responsible of the wholeness (scheduling, project's progress, meetings, coordination, division of duties and responsibilities, quality, communication with the client).
• PM takes care of that all members have something to do. PM also controls that tasks will be done correctly.
• Weekly reports (PM) using Metrics Monitoring Tool.
• Participating reviews and presentations (All).
8.9.2017 Faculty of Natural Sciences 15
UTA.FI/LUO
Working hour reporting
• Check from the course website:• http://www.uta.fi/sis/tie/pw/guidelines.html#working-hour-reporting
• Metrics Monitoring Tool is used to log working hours.• http://metricsmonitoring.sis.uta.fi/
8.9.2017 Faculty of Natural Sciences 16
UTA.FI/LUO
Tools and tool training
• Familiarise yourself with the tools (managers coordinate)• http://www.uta.fi/sis/tie/pw/tools.html• http://www.uta.fi/sis/tie/pw/guidelines.html#tool-training
• Tools training is controlled in the project plan review meeting.
• Project manager is in charge on organising the training.• Version control.• UI design tool.• Project management tool.• Simple ”Hello World” application to show that your development environment
is ok.• Logging and unit testing optional.
• Recommendation: Systematical code reviews when using Github.
8.9.2017 Faculty of Natural Sciences 17
UTA.FI/LUO
Project plan and Project plan inspection
• Project plan:• http://www.uta.fi/sis/tie/pw/documents.html• Template from TUT.• Replace ”Tampere University of Technology” with ”University of Tampere”, etc.• In Section 5.1 (Iterations), list also iteration 0 that ends when the Project plan is
inspected.
• Start writing the project plan together with the team in collaboration withthe client.
• Invite team, client and supervisor to the Project plan inspection:• http://www.uta.fi/sis/tie/pw/guidelines.html#project-plan-inspection
• Team shows also their Hello World -application!
• Deadline 29.9.
8.9.2017 Faculty of Natural Sciences 18
UTA.FI/LUO
Reviews
• http://www.uta.fi/sis/tie/pw/guidelines.html#Reviews-and-review-meeting-agenda
8.9.2017 Faculty of Natural Sciences 19
UTA.FI/LUO
Scrum
• A (software) development framework.
• Mostly used in SPM/PW: ”modified scrum” / ”scrumbut”:• https://www.scrum.org/ScrumBut
• See wikipedia: Scrum software development.
• Scrum basics: https://www.youtube.com/watch?v=vmGMpME_phg&t=3s
• Introduction to Scrum – 7 minutes: https://www.youtube.com/watch?v=9TycLR0TqFA
• Product owner, Scrum Development team, Sprint, Sprint planning, Daily scrum, Sprint review meeting master,, Sprint retrospective, Product Backlog, Sprint backlog.
• Challenges when applying Scrum in student projects?
8.9.2017 Faculty of Natural Sciences 20
UTA.FI/LUO
Finishing the project
• Final meeting, final report + test report.
• Project CD / DVD / usb stick …
• Project poster.
• Final project presentation in January.
• Personal report II in the Moodle.
• Before team gets credits, all tasks should have been done. This is verified in the final meeting from the client.
• If there are unfinished tasks, those are listed in the meeting minutes of the final meeting, and the team need to report when the tasks are done.
• Could a public repository be a final location of codes and documentation?
8.9.2017 Faculty of Natural Sciences 21
UTA.FI/LUO
Requirements management
• Team decides how to manage requirements (wiki / PM-tool's issue tracker / excel / ...). Use cases, stories,...
• High level requirements are listed in the Project Plan.
• Four statuses of a functional requirement• In Product Backlog: Feature is in the Product Backlog.• In Progress: Team is implementing the feature in the current iteration.• Done: Feature is implemented, it is tested and verified that it is implemented
correctly. Definition of Done (DoD)? Team defines in the project plan.• Rejected (Deleted): the requirement is rejected/deleted for some reason. It
might have been a duplicate, or the project is not going to implement the feature.
• http://www.uta.fi/sis/tie/pw/guidelines.html#requirements-management
8.9.2017 22Faculty of Natural Sciences
Faculty of Natural SciencesFI-33014 Tampereen yliopistoUniversity of Tampere, Finland
Kanslerinrinne 1, TamperePinni B-rakennus, 1. kerros
Tel. +358 3 355 111Email: [email protected]
UTA.FI/LUO
Luonnontieteiden tiedekuntaTampereen yliopisto
FACULTY OF NATURAL SCIENCES
UNIVERSITY OF TAMPERE