Previous Lecture lect06 Next Lecture

lect06, Mon 01/27

Minimum Viable Product

Topics:

MVP Planning

To help your team (as well as your instructional staff) know what you are defining as part of your MVP—which you are delivering two weeks from Thursday (02/13) , we are asking you to do things process/tool wise:

In addition, issues on Github can have labels. Github creates some predefined labels, but can edit these and add new ones.

Finally, while regular cards cannot be given “labels” in the same way that issues are, you can just use the letters (MVP) in parens as a kind of label on the user stories that are part of your MVP.

In this way, anyone can look at your Kanban board, and see:

You main task in the remaining sprint is to adjust the user stories and issues that you want to include in the MVP.

There will be more detail on how to do that in Section.

Choose the right size MVP!

  • If it doesn’t deliver value ⇒ too small
  • If you can’t finish by due date ⇒ too big

Class slides:

We covered the following: https://sites.cs.ucsb.edu/~holl/CS48/handouts/Slides_SWDevelopment.pdf

Electronic Handouts:

Background Information: Code Smells