lab08 : Understanding your Epic

num ready? description assigned MW lect due MW lect assigned TR lect due TR lect
lab08 true Understanding your Epic Wed 02/19 05:00PM Thu 02/20 11:59PM Tue 02/18 05:00PM Wed 02/19 11:59PM

This lab requires in-person participation

This lab requires you to attend and participate with your team in your assigned lab section on either 2020-02-20 23:59 or 2020-02-19 23:59 and cannot be made up, except by participation with your team over Slack.

If you are not able to attend lab, you should be in touch with your team and your team mentor (as explained many previous times during the quarter.)

The teams you are on now are a starting point

If your team wants to stay together and work on the epic to which you have been assigned, you have that option.

Today, you’ll learn what that project would be like.

You may also have a few other options, possibly including:

This will be explained in more detail on the Slack and in lecture on

This lab is required in any case

Even if you already know you prefer to work alone on “conventional labs” for the rest of the quarter rather than on a legacy code project, you still need to complete this lab.

This gives you at least a taste of real world software development practice.

This lab has a quick turn around time

This lab should be completed MOSTLY within your 50 minute discussion section, though there is somework that you might need to continue over the subsequent 24 hours.

It needs to be finished, however, before:

The reason is that on those days in lecture we’ll be assigning final project teams.

This lab helps you to prepare for that.

Step 1: Locate your teams’s Epic (:00 to :10)

Each team has been assigned an “Epic” which is a collection of user stories from one of the three class legacy-code projects.

Navigate to: https://ucsb-cs56.github.io/w20/info/projects/ and locate your team’s epic.

You’ll discover that your Epic is associated one of three projects:

Meet with your team and your mentor for a 10 minute briefing about the big picture purpose of the project, and the purpose of your particular epic. Your mentor will explain to you what your epic is about.

Take notes. You’ll need to write down a few things about your project and your epic in a later step.

Time box this to the first 10 minutes of lab (you need to be finished by 10 minutes after the hour.)

Step 2: Explore the Kanban board (:10 to :20)

Ask your mentor to walk you through the Kanban board for your Epic, and explain how a Kanban board works.

Go through each of the stories at a high level, so you have a general sense of the Epic and what is involved.

Again, take notes. Time box this

Step 3: Get app running on localhost (:20 to :35)

In order to be able to work with this app, you need to be able to get it running on localhost.

Find the repo for your teams project, and clone it. Configure it for OAuth on localhost.

Run mvn spring-boot:run and explore the app. Ask your mentor for help with understanding the current features.

If this takes longer than past :35, you can go to :40 if needed, but by :40 move on to Step 4.

Step 4: Groom at least one story (:35 to :50)

(preferably two, unless you are running late)

Then take the first story on the board.

The process of adding clear acceptance criteria to stories is sometimes called “Grooming”.

Step 5: Record your observations (after lab).

This is an individual step to be done after lab is over.

The way you do this step depends on whether you are on a mapache-search team or not.

Step 5a: Mapache Search Teams

Please fill out this survey: https://docs.google.com/forms/d/e/1FAIpQLSdN02OEYKx9T43tdoECkzLPW20KbTDL8P7pZxzJeYJLQ9hRAg/viewform?usp=sf_link

This counts in place of the rest of step 5.

Step 5b: Other Teams

Your team has a repo called, for example TEAM-w-5pm-b.

This web search will bring up a list of all of these TEAM repos. Locate the one for your team.

In a previous class meeting you should have been added to a team (as a “maintainer”) that has admin access to this repo. If that’s not the case, then find someone on your team that can fix that now.

Next, clone this TEAM repo on your computer or your account. Create a branch called lab08-githubid (where githubid is your githubid). You may also collaborate with up to one pair partner, in which case, use lab08-githubid1-githubid2

On this branch, create a directory called lab08 in the repo, and under that directory, create a file called lab08-githubid.md (or lab08-githubid-githubid2.mdin which you put the following headings:

# Name(s): (your name(s))

# Project Description

Link to project here: 

(Briefly describe the purpose of the project to which your team is assigned.)
(NOTE: Mapache Search folks can leave this out

# Our Epic

Link to epic here: 

(Briefly describe the epic to which your team is assigned.)

# Observations

(OPTIONAL: Add any observations you have about the project, and/or the epic to which you were assigned.)

Then, fill in the file, replacing the placeholder text with your own answers and observations.

Commit that to your branch and push that commit to GitHub.

Now, make a pull request (BUT DO NOT MERGE IT) for your lab08 branch to the master branch.

Then, put a link to that PR on your team’s slack channel. This is how you submit your work for grading to your mentor.

Step 6: Choose a story, and describe how you would go about it

Now, choose one story from your team’s Kanban board that does not already have any comments fron your team members.

Look at that story, and determine one place in the code that you would have to make changes in order to work on the story.

Make a comment on the issue with your ideas.

Then, link to the issue in your team’s slack chanel.

If you are completely lost, then USE THE SLACK CHANNEL for your team, and ask your mentor and your fellow team members questions. Do this sooner, rather than later (not at the last minute).

You may also use the three slack channels for the projects:

You are not necessarily expected to know how to address the issue. But you are expected to ask enough questions until you learn how to address the issue.

Beyond lab08

Now that you’ve done what was needed for the grade for lab08, I suggest the following steps:

Rubric