CSC307 Lecture 05

Introduction to Software Engineering
Task Board
(202601)

Transcript

1. Dr. Javier Gonzalez-Sanchez javiergs@calpoly.edu www.javiergs.info o ffi ce: 14 -227 CSC 307 Introduction to Software Engineering Lecture 05. Task Board
2. Product Backlog 2 INVEST
3. 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)
4. Tasks
5. Create a Backlog and Task board 5 stories tasks (new)
6. Create a Backlog and Task board 6 stories tasks (new) UI UI UI UI UI
7. 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
8. 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.”
9. 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
10. 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 …
11. Designer (non-technical) tasks
12. 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
13. Agile in Action 13
14. 14 Tools We need a Tool
16. Taiga
17. https://taiga.io 17
18. Let’s Work 18 Register on Taiga
19. https://taiga.io 19
20. Project 20
21. Project 21
22. Team 22
23. Team 23
24. Product Backlog 24
25. Product Backlog 25
26. Product Backlog 26
27. Sprint 27
28. Sprint 28
29. Sprint 29
30. Task Board 30
31. Task Board 31
32. Burndown Chart 32
33. One More Thing Burn down Chart
34. 34 Work Remaining (Hours or Points) days Burn down Chart
35. Which ones are Burn down Charts? 35 A B C D
36. Questions 36
37. Lab 05. Taiga
39. 39 A Desktop version (Java Desktop Aplication) of this Tool
40. 40 A Desktop version (Java Desktop Aplication) of this Tool
41. 41 A Desktop version (Java Desktop Aplication) of this Tool
42. 42 A Desktop version (Java Desktop Aplication) of this Tool
43. 43 Let’s Work We need to create a Product Backlog
44. 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!
45. Let’s Work 45
46. CSC 307 Introduction to Software Engineering Javier Gonzalez-Sanchez, Ph.D. javiergs@calpoly.edu 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.