Upgrade to Pro — share decks privately, control downloads, hide ads and more …

CSC307 Lecture 05

CSC307 Lecture 05

Introduction to Software Engineering
Task Board
(202601)

Avatar for Javier Gonzalez-Sanchez

Javier Gonzalez-Sanchez PRO

January 16, 2026
Tweet

More Decks by Javier Gonzalez-Sanchez

Other Decks in Programming

Transcript

  1. Dr. Javier Gonzalez-Sanchez [email protected] www.javiergs.info o ffi ce: 14 -227

    CSC 307 Introduction to Software Engineering Lecture 05. Task board
  2. 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)
  3. Note • User Stories: Describe the go a l, not

    the UI design. • Accept a nce Criteri a : Add speci f ics like “the f ilter should be a dropdown” or “results should upd a te without refreshing the p a ge.” • Wirefr a mes/Mockups: Att a ched to a User Story a s supplement a ry m a teri a l (done by a designer or with coll a bor a tion). • T a sks/Sub-t a sks: Bre a k the story down a nd a dd T a sks for UI implement a tion (e.g., “Include a f ilter dropdown”). 7
  4. 12 Stories vs Tasks 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
  5. 13 Stories vs 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 Ex a mple • Cre a te d a t a b a se t a ble for submissions • Add v a lid a tion for f ile size • Write unit tests for submission service
  6. 14 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
  7. 43 Let’s Work Create a Product Backlog, define a first

    Sprint (1 week), and agree on a Sprint Backlog with Tasks for each Story. Add me (mscjaviergs@gmail) to your project.
  8. 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.