A.pdf

Task board
(20260902)

Transcript

1. CSC 3100 Software Engineering Lecture 02. Task board Dr. Javier Gonzalez-Sanchez javiergs@calpoly.edu www.javiergs.info ffi o ce: 14 -227
2. Product Backlog INVEST 2
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. Agile in Action 4
5. Agile in Action 5
6. Agile in Action 6
7. Tasks
8. Create a Backlog and Task board stories 8 tasks (new)
9. Stories A Story describes fe ture from the user’s perspective. Key Ch r cteristics • Focused on v lue, not implement tion • Describes wh t nd why • C n be demonstr ted nd v lid ted • Sm ll enough to it in sprint Ex mple a a a a a a a a a a f a a a a a a a a a a a 9 a As student, I w nt to submit my ssignment online so th t I c n receive feedb ck
10. Acceptance Criteria • M ke the story test ble nd un mbiguous. • Specify observ ble beh vior nd constr ints. • UI det ils re llowed only if they ect correctness or us bility. • Wirefr mes / Mockups c n help to visu lize solutions Ex mples: a a a a ff a a a a a a a a a a a a a a a f a 10 a • “The ilter is presented s dropdown.” • “Results upd te without refreshing the p ge.” • “Filtering completes in under 1 second.”
11. Tasks A T sk is concrete piece of engineering work required to implement Key Ch r cteristics a f a a a a a a a a 11 a • Focused on how • Technic l nd implement tion-speci ic (but not limited to coding) • Me sured in hours or d ys story.
12. Tasks Ex mples: • Add select (dropdown) widget nd popul te it with options (x, y, z) • Register n event listener on the ilter selection ch nge • Upd te the results p nel with the fetched iltered d t • Add v lid tion for ile size • Write unit tests for submission service a a a a f a f a f a a a a a a a a a a 12 a • Cre te d t b se t ble for …
13. Stories vs Tasks • Stories express intent nd v lue • T sks express execution nd e ort • Common Mist ke: ❌ Writing t sks s stories Rule of Thumb user, it is not a a a ff a a a a a a a 13 a • If it describes coding work, it is t sk a • If it c nnot be demoed to story
14. Re lect on This If you were randomly assigned one of the listed tasks, • Would you understand what needs to be done (your specific part and how it fit into the whole)? • Is it clear what inputs you will receive and what outputs you are expected to deliver? • If your task depends on data or UI from another Task or Story, do you know what mock objects you might need? 14 f • Can you easily identify who on your team to contact for the part that will connect with yours?
15. Project Management Tools
16. Product Backlog 16
17. Sprint 17
18. Sprint 18
19. Sprint 19
20. Task Board 20
21. Task Board 21
22. Burndown Chart 22
26. One More Thing Burn down Chart
27. Burn down Chart Work Remaining (Hours or Points) days 27
28. Which ones are Burn down Charts? A 28 B C D
29. Review Stories
30. Case 1 30
31. Case 2 31
32. Case 3 32
33. Case 4 33
34. Case 5 34
35. Case 6 35
36. Case 7 36
37. Review Acceptance Criteria
38. Acceptance Criteria 38
39. Acceptance Criteria 39
40. Acceptance Criteria 40
41. Acceptance Criteria 41
42. Questions 42
43. CSC 3100 Software Engineering Javier Gonzalez-Sanchez, Ph.D. javiergs@calpoly.edu Fall 2026 Copyright. These slides may be used only as study material for CSC 5100 within the California State University system. They may not be distributed or used for any other purpose.