Tweet
Tweet

Slide 1

Slide 1 text

Dr. Javier Gonzalez-Sanchez [email protected] www.javiergs.info o ffi ce: 14 -227 CSC 307 Introduction to Software Engineering Lecture 05. Task Board

Slide 2

Slide 2 text

Product Backlog 2 INVEST

Slide 3

Slide 3 text

As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit)

Slide 4

Slide 4 text

Tasks

Slide 5

Slide 5 text

Create a Backlog and Task board 5 stories tasks (new)

Slide 6

Slide 6 text

Create a Backlog and Task board 6 stories tasks (new) UI UI UI UI UI

Slide 7

Slide 7 text

7 Stories A Story describes a fe a ture from the user’s perspective. Key Ch a r a cteristics • Focused on v a lue, not implement a tion • Describes wh a t a nd why • C a n be demonstr a ted a nd v a lid a ted • Sm a ll enough to f it in a sprint Ex a mple As a student, I w a nt to submit my a ssignment online so th a t I c a n receive feedb a ck

Slide 8

Slide 8 text

8 Acceptance Criteria • M a ke the story test a ble a nd un a mbiguous. • Specify observ a ble beh a vior a nd constr a ints. • UI det a ils a re a llowed only if they aff ect correctness or us a bility. • Wirefr a mes / Mockups c a n help to visu a lize solutions Ex a mples: • “The f ilter is presented a s a dropdown.” • “Results upd a te without refreshing the p a ge.” • “Filtering completes in under 1 second.”

Slide 9

Slide 9 text

9 Tasks A T a sk is a concrete piece of engineering work required to implement a story. Key Ch a r a cteristics • Focused on how • Technic a l a nd implement a tion-speci f ic (but not limited to coding) • Me a sured in hours or d a ys

Slide 10

Slide 10 text

10 Tasks Ex a mples: • Add a select (dropdown) widget a nd popul a te it with options (x, y, z) • Register a n event listener on the f ilter selection ch a nge • Upd a te the results p a nel with the fetched f iltered d a t a • Add v a lid a tion for f ile size • Write unit tests for submission service • Cre a te d a t a b a se t a ble for …

Slide 11

Slide 11 text

Designer (non-technical) tasks

Slide 12

Slide 12 text

12 Stories vs Tasks • Stories express intent a nd v a lue • T a sks express execution a nd e ff ort • Common Mist a ke: ❌ Writing t a sks a s stories Rule of Thumb • If it c a nnot be demoed to a user, it is not a story • If it describes coding work, it is a t a sk

Slide 13

Slide 13 text

Agile in Action 13

Slide 14

Slide 14 text

14 Tools We need a Tool

Slide 15

Slide 15 text

No content

Slide 16

Slide 16 text

Taiga

Slide 17

Slide 17 text

https://taiga.io 17

Slide 18

Slide 18 text

Let’s Work 18 Register on Taiga

Slide 19

Slide 19 text

https://taiga.io 19

Slide 20

Slide 20 text

Project 20

Slide 21

Slide 21 text

Project 21

Slide 22

Slide 22 text

Team 22

Slide 23

Slide 23 text

Team 23

Slide 24

Slide 24 text

Product Backlog 24

Slide 25

Slide 25 text

Product Backlog 25

Slide 26

Slide 26 text

Product Backlog 26

Slide 27

Slide 27 text

Sprint 27

Slide 28

Slide 28 text

Sprint 28

Slide 29

Slide 29 text

Sprint 29

Slide 30

Slide 30 text

Task Board 30

Slide 31

Slide 31 text

Task Board 31

Slide 32

Slide 32 text

Burndown Chart 32

Slide 33

Slide 33 text

One More Thing Burn down Chart

Slide 34

Slide 34 text

34 Work Remaining (Hours or Points) days Burn down Chart

Slide 35

Slide 35 text

Which ones are Burn down Charts? 35 A B C D

Slide 36

Slide 36 text

Questions 36

Slide 37

Slide 37 text

Lab 05. Taiga

Slide 38

Slide 38 text

No content

Slide 39

Slide 39 text

39 A Desktop version (Java Desktop Aplication) of this Tool

Slide 40

Slide 40 text

40 A Desktop version (Java Desktop Aplication) of this Tool

Slide 41

Slide 41 text

41 A Desktop version (Java Desktop Aplication) of this Tool

Slide 42

Slide 42 text

42 A Desktop version (Java Desktop Aplication) of this Tool

Slide 43

Slide 43 text

43 Let’s Work We need to create a Product Backlog

Slide 44

Slide 44 text

44 Let’s Work Together: - Create a Product Backlog. - Define a first Sprint (1 week). Individually: -Take property of one or more unique Stories -Add Tasks to your story!

Slide 45

Slide 45 text

Let’s Work 45

Slide 46

Slide 46 text

CSC 307 Introduction to Software Engineering Javier Gonzalez-Sanchez, Ph.D. [email protected] Winter 2026 Copyright. These slides can only be used as study material for the class CSC307 at Cal Poly. They cannot be distributed or used for another purpose.