lect03

lect03, Mon 01/22

Scrum Process, Kanban Boards

Announcements:

Homework for Wednesday: On Retrospectives https://ucsb-cs148.github.io/w24/hwk/h03/

ToDos:

Please fill in some information on your planned tech stack(s) at https://bit.ly/148-teams. Look through the Technologies for Inspiration doc we pointed you to, and start requesting/using the Slack channels you need to succeed!

Topics:

User Analysis / Task Analysis - the first two steps of any design process.
User Stories, Personas, Scenarios: the common language of shareholders
Scrum Process
Scrum Standup and Github Project Kanban Board
Project group Standups and other Scrum coordination. Preparing Sprint00.

Electronic Handouts:

Scrum – A Breathtakingly Brief and Agile Introduction: https://sites.cs.ucsb.edu/~holl/CS148/handouts/Scrum.pdf
Scenario-based Design

Sprint Planning

Part of your lab02 deliverables include documentation of at least one Sprint Planning meeting in a team/sprint0?/ folder in your main repo (question mark for number of your current sprint, which may vary from team to team). For the purpose and mechanisms of a Sprint Planning meeting see, e.g., pages 25-27 of our Scrum booklet. It is OK for such a meeting to already have happened and to be documented retroactively.

IMPORTANT Update on User Story Mapping

Github Projects has changed substantially since the last time this course was taught. Prof. Conrad’s videos posted in the lect02 notes still describe what we are trying to accomplish, but the mechanisms that GitHub Projects support have been revamped since then. The old Github Projects (classic) experience is actually still available, but the new experience has several powerful new features, so we will adapt and practice the new functionality in this course.

We will give a brief demo on Kanban Board mapping in class today.

The most important pieces of information are:

You can now have several Github Projects associated with any one Repository (but we will likely maintain a 1-1 mapping)
Instrad of the old system of Cards and Issues, now every new item is created as an Issue.
There is a new powerful system of custom fields and tags. We will use a custom field “Type” to distinguish between User Stories and Issues.
You have new helpful views of your User Stories and Issues in addition of the Kanban Board: Item View, Roadmap view, and custom tables.

Where we are

We did not discuss all of the items below in detail, but we mentioned most of them, and will go into more detail in the weeks ahead.

Forming teams
Setting up a Kanban board
Establishing team norms/procedures
Defining user stories / issues
Assigning user stories to individuals for an iteration
Completing issues, and doing pull requests
Code reviews
Defining a minimum viable product
Retrospectives

Work in Project Groups:

Daily Scrum (log a lect03.md document!)
Further discussion on technologies
Work on lab01 deliverables
Work on your README and team/AGREEMENTS.md from last class
Scrum: User Stories