Sprint 0: 04 Apr - 18 Apr ========================= .. todo:: Inserire informazioni generali sullo sprint, come inizio e fine. Consegna -------- La seguente documentazione è stata fornita dal cliente durante questo sprint: - :download:`Descrizione iniziale del prodotto <0-initial.pdf>` - :download:`Sprint 0 <0-sprint-requirements.pdf>` Goal ---- .. todo:: Inserire qui lo sprint goal. Backlog ------- .. todo:: Mostrare qui lo sprint backlog di Taiga. Definition of done ------------------ .. todo:: Inserire qui la definition of done dello sprint. Registro attività ----------------- Riunioni collettive ^^^^^^^^^^^^^^^^^^^ .. list-table:: :header-rows: 2 * - Data - Ora - Durata - Attività * - - - 10h 6m - Totale * - 2021-04-08 - 20:45 - 1h - Analisi documento di specifiche * - 2021-04-09 - 14:15 - 35m - Intervista con il cliente * - 2021-04-09 - 15:00 - 1h - Resoconto intervista * - 2021-04-11 - 15:03 - 2h 39m - Documentazione e planning poker * - 2021-04-15 - 18:15 - 52m - Documentazione * - 2021-04-17 - 15:05 - 4h - Documentazione e partita a Scrumble Attività individuali ^^^^^^^^^^^^^^^^^^^^ Stefano Goldoni """"""""""""""" .. list-table:: :header-rows: 2 * - Data - Durata - Attività * - - 6h 30m - Totale * - 2021-04-08 - 1h - user stories * - 2021-04-09 - 1h - epic * - 2021-04-10 - 30m - use cases * - 2021-04-11 - 30m - use cases * - 2021-04-14 - 30m - documentazione SRS * - 2021-04-15 - 30m - documentazione SRS * - 2021-04-17 - 1h 30m - diagrammi di attività Flavia Cocca """""""""""" .. list-table:: :header-rows: 2 * - Data - Durata - Attività * - - 15h - Totale * - 2021-04-08 - 2h 30m - brainstorming Ui * - 2021-04-10 - 2h - creazione frame in figma con relativo css * - 2021-04-11 - 1h 30m - mockup UI con relativo css (creazione componenti) * - 2021-04-12 - 1h 30m - mockup UI con relativo css (creazione componenti) * - 2021-04-14 - 3h - mockup UI con relativo css (creazione pagine) * - 2021-04-15 - 2h - mockup UI con relativo css (creazioni pagine) * - 2021-04-16 - 2h - ultimi ritocchi UI * - 2021-04-17 - 30m - Stesura documentazione partita scrumble Chiara Calzolari """""""""""""""" .. list-table:: :header-rows: 2 * - Data - Durata - Attività * - - 12h 30m - Totale * - 2021-04-09 - 2.5h - Brainstorming UI * - 2021-04-10 - 1.5h - mockup UI con relativo css (dashboard ed elenco repositories) * - 2021-04-11 - 1.0h - mockup UI con relativo css (settings) * - 2021-04-11 - 0.5h - Prima versione del logo * - 2021-04-12 - 3.0h - mockup UI con relativo css (creazione componenti, light/dark mode) * - 2021-04-13 - 1.0h - mockup UI con relativo css (alerts) * - 2021-04-15 - 1.0h - Versione definitiva del logo * - 2021-04-16 - 0.5h - mockup UI con relativo css (Notifications e Share) * - 2021-04-17 - 1.0h - Documentazione Mockup * - 2021-04-17 - 0.5h - Doppiaggio video di presentazione Stefano Pigozzi """"""""""""""" .. list-table:: :header-rows: 2 * - Data - Durata - Attività * - - 23h 30m - Totale * - 2021-04-08 - 4h 30m - Configurazione Discord e GitLab * - 2021-04-09 - 3h 30m - Riunione con il cliente e configurazione Taiga * - 2021-04-10 - 4h - Configurazione Penpot, Taiga, UI Design, progettazione Database * - 2021-04-11 - 3h 30m - Riunione, configurazione GitLab e project management * - 2021-04-12 - 30m - Configurazione Twitter e UI Design * - 2021-04-15 - 2h 30m - Partita a Scrumble e project management * - 2021-04-16 - 1h 30m - Project management e configurazione SonarQube * - 2021-04-17 - 3h 30m - Riunione e partita a scrumble Giovanni Anniballi """""""""""""""""" .. note:: Giovanni ha iniziato a raccogliere dati sul tempo impiegato a partire dallo Sprint 1. Giorgio Minoccari """""""""""""""""" .. note:: Giorgio ha iniziato a raccogliere dati sul tempo impiegato a partire dallo Sprint 1. Lorenzo Balugani """""""""""""""" .. note:: Lorenzo ha iniziato a raccogliere dati sul tempo impiegato a partire dallo Sprint 1. Risultati della partita di Scrumble ----------------------------------- .. list-table:: :header-rows: 1 * - GOAL - QUESTIONS - EVALUATION - Chiara - Giorgio - Giovanni - Stefano P. - Lorenzo - Stefano G. - Flavia - QUESTION - METRIC * - Learn - Q1 - 1 = no idea of the Scrum roles 5 = perfect knowledge of the roles and their jobs - 4 - 4 - 4 - 4 - 5 - 5 - 4 - Do team members understand the Scrum roles? - Knowledge of Scrum roles by questions * - Learn - Q2 - 1 = couldn't repeat the game 5 = could play the game as a Scrum Master by himself - 3 - 3 - 4 - 5 - 3 - 3 - 3 - Do team members feel they learned the process? - Opinions from the participants * - Learn - Q3 - 1 = totally lost 5 = leads the game driving the other players - 3 - 4 - 4 - 4 - 5 - 5 - 5 - Does everyone keep up with the other players? - Check during every sprint retrospective if every one is on point * - Practice - Q4 - 1 = feels the game is unrepeatable 5 = feels the game could be played in any situation - 1 - 2 - 1 - 1 - 1 - 2 - 1 - Are the game mechanics linear and repeatable? - Opinions from the participants * - Practice - Q5 - 1 = 0 to 3 stories 2 = 4 to 6 3 = 7 to 9 4 = 10 to 12 5 = 13 to 15 - 5 - 5 - 5 - 5 - 5 - 5 - 5 - Do team success in completing the game? - Number of User Stories completed * - Practice - Q6 (Only Dev. Team) - 1 = abnormal difference from the other players 5 = coherent and uniform with the group most of the time - 5 - 4 - 5 - 4 - 5 - / - / - Do team members efficiently estimate during sprint planning? - Uniformity in evaluating the size and the priority of user stories * - Cooperation - Q7 - 1 = never speaks with the other players 5 = talks friendly to anyone in every situation - 4 - 5 - 5 - 5 - 5 - 5 - 4 - Do team members know each other better? - Level of players' serenity throughout the game * - Cooperation - Q8 - 1 = never puts effort in doing something 5 = every time is willing to understand what is going on - 4 - 3 - 3 - 2 - 3 - 4 - 3 - Does the game let all players cooperate? - Contribution of every player during the game * - Cooperation - Q9 - 1 = never asks for an opinion 5 = wants to discuss about every topic - 5 - 5 - 5 - 3 - 5 - 4 - 5 - Do team member consult each other about a topic? - Sharing of ideas * - Motivation - Q10 - 1 = not involved by the game 5 = always makes sure everyone is on point - 3 - 5 - 5 - 4 - 5 - 4 - 4 - Do team members encourage collegues in need? - Players explain something other players don't understand * - Motivation - Q11 (Only for PO) - 1 = poor/absent advices 5 = wise and helpful suggestions when is required - / - / - / - / - / - 4 - / - Does PO help the team? - Quality of PO's advices to get better in the next sprints * - Motivation - Q12 - 1 = doesn't express opinions during retrospective 5 = feels the retrospective fundamental to express opinions - 4 - 5 - 5 - 5 - 5 - 5 - 5 - Does the team come up with good ideas? - Effectiveness of sprint retrospective * - Problem Solving - Q13 - On the game board, if the debt pawn is on the lowest stage,the evaluation is 5, for every higher stage it decreases by 1 - 5 - 5 - 5 - 5 - 5 - 5 - 5 - Do team members behave well when facing a problem? - Level of the technical debt at the end of the game * - Problem Solving - Q14 (Only Dev. Team) - Calculate the average of tasks left for each sprint: 1 = 21+ 2 = 16-20 3 = 11-15 4 = 6-10 5 = 0-5 - 5 - 5 - 5 - 5 - 5 - / - / - Does team organize their tasks properly? - Average of tasks left at the end of each sprint * - Problem Solving - Q15 (Only for PO) - Same evaluation as Q14 for the PO - / - / - / - / - / - 5 - / - Does PO plan efficiently the Sprint Backlog? - Average of tasks left at the end of each sprint Statistiche ----------- Gitinspector ^^^^^^^^^^^^^ Questa statistica è stata generata dal prof. Marcello Missiroli con `Gitinspector`_ al termine dello Sprint. - :download:`Sprint 0 <0-stats.html>` .. _Gitinspector: https://github.com/ejwa/gitinspector