PES deliverables: files and checklist per Fag

Team name

Replaces <nom>. The date uses YYYYMMDD (the delivery day); if your teacher asks for another format, use theirs.

Every document needs a cover page with the team and project name and which deliverable it is (inception or sprint, and which one).

The team's Google Drive folder

📁 (team folder)
├── Plantilla PRT            ← project record track
├── <nom>_memoria            ← living project report
├── info_equip               ← members, GitHub, Taiga (fill it in now!)
├── 📁 incepcio
├── 📁 sprints
│   ├── 📁 1
│   ├── 📁 2
│   └── 📁 3
└── 📁 entrega_final

Fag-1

Inception 1: the product vision

Elevator pitch Wed 16/09 · Due Fri 18/09

Files (`incepcio` folder)

Template: incepcio/nom_incepcio_1.docx. Recommended reading: The Agile Inception Deck.

Presentation

A 2-minute elevator pitch (between 1:55 and 2:05) by one person. Clear and realistic goals, why they matter to an investor today, and concrete facts about the product, business model, market and competitors. Timer and tips →

How it is graded

Elevator pitch: message (does it convey the vision?) and appeal.
Product box: clear vision, the 3 or 4 most representative features and an attractive design.
NOT list: cohesion and coherence between its three parts.
Market analysis: systematic, thorough scope and a useful analysis that makes your contribution clear.

Contents of incepcio_1

Sprint master reportWho did what and how the phase went.
General project conceptA couple of paragraphs, including the quality of the open dataset and the new concepts you add.
Product boxIt can be a link to an external resource.
Market analysisShort description of each similar app, a summary table by criteria, the business opportunity and evidence of your search method.
NOT listWhat the product does, does not do and is still undecided.

Fag-2

Inception 2: planning

Customer presentation Wed 30/09 · Due Fri 02/10

Files (`incepcio` folder)

presentation slides
copy of the report
copy of the record track

Template: incepcio/nom_incepcio_2.docx. In the report (root document) fill in section 2 (Methodology) and 3.4 (Instrumentation).

Presentation

A 10-15 minute customer presentation by two people (not the pitcher), designed to sell the product: include key market insights and high-quality mock-ups.

How it is graded

Presentation: clear message, shows business value, engaging and consistent with the documents.
Product backlog: sensible stories ordered by priority, well described, with points and the key acceptance criteria, consistent with the NOT list.
Other: main stakeholders, a complete list of epics, a clear physical architecture and the most critical mock-ups.

Contents of incepcio_2

Sprint master report
Updated NOT listWith the changes clearly marked (always).
Stakeholder listOnly the key ones; no lengthy descriptions needed.
Table of epics and user storiesNames only, grouped by epic.
Initial product backlog in TaigaWith story points.
Critical mock-ups
Physical architecture diagramA first overall sketch.
UML conceptual modelOf the envisaged final solution. Example →
Service consumers and producersIdentify the teams you will exchange services with.

Fag-3

Sprint 1

Planning Mon 05/10 · Retrospective and delivery Wed 28/10

At the start (`sprints/1` folder)

same day as the planning

At the end

Report template: sprints/1/nom_report_1.docx. Services between teams this sprint: define and negotiate the service you will build and the one you will consume.

How to do the planning, report and charts →

Sprint 1 checklist

planning_1: sprint goalOne sentence.
planning_1: sprint storiesName, epic and tasks for each, with estimated hours per task.
Sprint backlog in Taiga consistent with the planning
Report: introductionSummary of the sprint and the teamwork.
Report: ceremoniesMeetings, sprint burndown, velocity and product burndown.
Report: changelogEvery change since the previous iteration.
Updated project report (memoria)Requirements, methodology and technical description.
Service between teams defined and agreed

Fag-4

Sprint 2

Review + planning Mon 09/11 · Demo Mon 23/11 · Due Fri 27/11

At the start (`sprints/2` folder)

same day as the planning

At the end

On Monday 23 there is the demo of methodological and cross-cutting aspects: treat it like a mini delivery. Services between teams: each team finishes and offers its own (code, tests, endpoint and documentation).

This is the course's second assessment point (mid-course development).

Sprint 2 checklist

Sprint 1 review done and backlog revised
planning_2 with goal, stories, tasks and hours
Methodology demo readyTaiga, Git, tests, quality, deployment.
Own service built, tested and documented
Retrospective documented
Report with the three charts
Project report and PRT updated
Bugs recorded and handledEspecially those in stories from earlier iterations.

Fag-5

Sprint 3 and closing

Review + planning Mon 30/11 · Final presentation Wed 16/12 · Due Fri 18/12

Sprint 3 (`sprints/3` folder)

Closing (`entrega_final` folder)

Managerial report: executive summary, most significant deviations, self-assessment (challenges, barriers, opportunities, what you learned, what you would do differently, concepts from other courses) and a final statement on each member's involvement.
Final release information: step-by-step instructions to run the app and any useful material (videos, docs). It is graded too.
Final presentation slides.

Services between teams: each team integrates the service offered by its partner team.

Final checklist

planning_3 and report_3
The other team's service integrated
Realistic demo dataset
Presentation rehearsed (20 + 10 min)
Managerial report
Final release information
Final slides in entrega_final
Final project report and PRT with the per-member summary
Taiga closed: stories, tasks and actual hours

Always

What is assessed in every document

Text: writing, spelling, figures and tables.
Images: quality and readability (no blurry diagram screenshots).
Structure: cover page, page and section numbering.
Layout: page breaks, margins.

Taiga, frozen at every Fag

At each delivery, export the Taiga project, import it as a new project and share that copy with the teachers. Do not touch it again: it must stay unchanged. Step by step →

The project record track (Plantilla PRT)

It is assessed on completeness, on following the guidelines (date, duration, member, activity, story number and comments, one person per row) and on readability (uniform descriptions, useful comments). Activities and an example →

What to deliver, when and under which name

Inception 1: the product vision

Files (incepcio folder)

Presentation

How it is graded

Contents of incepcio_1

Inception 2: planning

Files (incepcio folder)

Presentation

How it is graded

Contents of incepcio_2

Sprint 1

At the start (sprints/1 folder)

At the end

Sprint 1 checklist

Sprint 2

At the start (sprints/2 folder)

At the end

Sprint 2 checklist

Sprint 3 and closing

Sprint 3 (sprints/3 folder)

Closing (entrega_final folder)

Final checklist

What is assessed in every document

Taiga, frozen at every Fag

The project record track (Plantilla PRT)

Files (`incepcio` folder)

Files (`incepcio` folder)

At the start (`sprints/1` folder)

At the start (`sprints/2` folder)

Sprint 3 (`sprints/3` folder)

Closing (`entrega_final` folder)