LO1 Agile Basics: Understand Agile principles, including the Agile Manifesto, and differentiate it from Waterfall
LO2 Product vs Project: Grasp the nuances between Product and Project Management, focusing on Product Discovery and Delivery
LO3 Teamwork: Learn team collaboration through group projects, covering challenge mechanics and use-case proposals
LO4 MVP & Prioritization: Acquire skills in defining MVPs, mapping User Stories, and prioritizing features with techniques like Impact vs Effort and MoSCoW
LO5 Scrum & Kanban: Understand Scrum and Kanban methodologies, including Scrum rituals and artefacts like Backlogs, Epics, User Story Mapping, and Acceptance Criteria. LO6: Familiarize with tools like Azure Boards, and Google Analytics, and apply metrics like the AARRR funnel for product evaluation
LO7 Conduct retrospectives, gather user feedback and apply lessons learned for ongoing product improvement

S1 Fundamentals and Agile Manifesto. Agile versus Waterfall
S2 Product Management vs Project Management. Two-Way Development: Product Discovery & Product Delivery
S3 Group project challenge. Challenge mechanics. Use-case proposals and outcomes
S4 Agile digital product teams
S5 Introduction to Minimum Viable Product - MVP and User Story Mapping (USM)
S6 Agile Methodologies Scrum and Kanban. Scrum rituals and artefacts: Product and Sprint Backlog, Epics, USM, Acceptance Criteria
S7 Definition of MVP for each use case and respective USM, using Miro: requirements and features of each step
S8 Prioritizing features: Impact vs Effort Matrix and MoSCoW
S9 Agile product development planning using Azure Boards: MVP delivery in weekly sprints
S10 Metrics to evaluate product effectiveness and efficiency. AARRR Funnel. Analysis in Google Analytics. User interviews. Retrospective and lessons learned. Demo day.

Course w/ periodic assessment. No Final Exam. Assessment weights:
• 70% Lab project carried out in a group + the final presentation and individual discussion.
• 30% 3 Mini-tests with multiple choice and um final test
A mark below 10 assigns the student to an exam in normal and/or the appeal period (30% of the mark), where the completion and approval of the group project or an individual project (70%) is mandatory.

The objective of the UC is to develop a technological project in line with the scope of the Course. Contact will be established with project planning considering the main phases: Requirements analysis, development, partial tests and final tests and changes. Contact with laboratory equipment and tools is one of the goals for designing a software, hardware or both project.

I. Introduction to technological innovation along the lines of Europe
II. Planning a technological project and its phases
III. Essential aspects for the development of a project
IV. Definition of material resources
V. Budget of a project
VI. Partial and joint Test Plan
VII. Presentation of a technological project
VIII. Technological project demonstration
IX. Preparation of Technical Report

Periodic grading system:
- Group project: first presentation: 30%; second presentation and exibithion: 40%; final report: 30%. The presentations, demonstrations and defence are in group.