Collegiate programming laboratory 0800-PPROZESP2-1

http://www.fizyka.umk.pl/~grochu/ppz2

During the course students will work in teams to carry out a software project. Teams and projects selection is agreed with the teacher.
Projects are implemented using iterative (agile) methodologies using tools that support development teams such as version control systems (git or subversion) and project management systems (TFS/VSTS, GitHub, trac).
The classes are held once every two weeks. During meetings teams will report work progress, they will identify and assign tasks for next iteration, discuss issues related to the project, share knowledge about the technologies and tools they are using for project implementation.
The main tasks facing the teams:
- team creation and team role assignment, team leader selection
- identify project milestones and software requirements, define task and assign them to team members
- task planing, work items prioritization and effort estimation
- selection of development tools and technologies needed to complete the tasks
- development of architecture and system specifications
- providing a web page containing information about the project and the team
- project implementation in accordance with provided specification
- collaborative development using version control tools and project management tools
- application documentation and technical documentation preparation and maintaining
- reporting tasks and work progress
- final product presentation

Total student workload

- total hours of student work in direct contact with the teacher: 15h laboratory - time spent on individual work needed to successfully pass the course: 10h - time required to prepare and participate in the final evaluation process: 5 h - time required for obligatory internships: 0 h

Learning outcomes - knowledge

W1. knows basic principles of working in a development team (K_W04) W2. knows basic principles of project management methodologies, with particular emphasis on agile methods. (e.g. Scrum) (K_W05, K_W06) W3. knows the basics of version control systems (K_W06) W4. has knowledge about issue tracking and project management tools (K_W05, K_W06) W5. knows basic principles of IT project specification, knows and understands elements of the system requirement specification, has basic knowledge about methods used to plan and organize team work (K_W04, K_W05)

Learning outcomes - skills

U1. is able to collect, analyze and present information needed to solve an IT problem (K_U01, K_U02, K_U03) U2. is able to collaborate in development team with division of powers and responsibilities, has ability to use version control systems, is able to use issue tracking systems and project management systems (KU_05, K_U10) U3. is able to plan and schedule work for simple IT projects, is able to prepare technical documentation (K_U02, K_U04, K_U08) U4. is able to evaluate the usefulness of IT technologies and is able to choose the right development tools to meet project requirements (K_U02, K_U06) U5. is able to use the right software development tools to implement informatics systems (K_U10) U6. has ability to identify and formulate set of tasks for a development team working on a simple IT project (K_U08) U7. is able to prioritize tasks, has basic ability to estimate the workload and time required to complete tasks (K_U05)

Learning outcomes - social competencies

K1. works and thinks in a creative and entrepreneurial way (IS s2: K_K01) K2. is able to work as a team member, has ability to manage his time and meet deadlines (IS s2: K_K04) K3. has ability in effective IT project implementation (IS s2: K_K05)

Teaching methods

- team work - projects - presentations

Observation/demonstration teaching methods

- display

Expository teaching methods

- informative (conventional) lecture

Exploratory teaching methods

- seminar
- project work

Online teaching methods

- methods referring to authentic or fictitious situations
- content-presentation-oriented methods
- cooperation-based methods

Type of course

compulsory course

Prerequisites

- structured programming skills - basic knowledge of object-oriented design - ability to program in at least one object-oriented language - basic knowledge of version control systems - ability to read technical documentation in English

Course coordinators

Marek Grochowski

Assessment criteria

The course covers 30 hours of classes divided into 2 semesters.
Assessment of the course after the first semester depends on the current stage of work on the project. Final course assessment take place on the basis of presentation of product (finished project) developed by each team.
The assessment given by teacher takes into account:
- quality of the final product including working application, documentation, design, technical and user documentation, project website, algorithmic and technical solutions applied, form of final presentation (outcomes W5, U4, U5, K3)
- degree of cooperation in the team, proper division of tasks and team roles, effectiveness of team communication, utilization of collaborative tools for developers (version control, project management systems, IDEs, issue trackers) (outcomes W1, W2, W4, U2, U6, U7, K2)
- evaluation of project planing, software requirements analysis, proper task specification and degree of compliance of implemented features with the objectives (outcomes W5, U3, U6, U7)
- effectiveness in execution of scheduled tasks and effort estimation accuracy (outcomes U7, K2, K3)
- selection of development tools and technologies necessary for the project (outcomes W3, W4, U4, U5)
- ability to acquire, share and present knowledge about the tools and technologies used in the project (outcomes U1)

Bibliography

2003.
- Scott Chacon and Ben Straub, Pro Git, 2nd edition, https://git-scm.com/book/en/v2
- Martin, Robert C., Agile software development: Principles, Patterns, and Practices, Pearson Education, 2003 - 529
- Ben Collins-Sussman, Brian W. Fitzpatrick, C. Michael Pilato, Version Control with Subversion, http://svnbook.red-bean.com/
- Murray Cantor, Jak kierować zespołem programistów, Wydawnictwa Naukowo-Techniczne, Warszawa, 2004.

Additional information

Additional information (registration calendar, class conductors, localization and schedules of classes), might be available in the USOSweb system:

Description of 0800-PPROZESP2-1 in USOSweb