lab04 : README w. Installation Instructions, Acceptance Tests, GitHub Actions
| num | ready? | description | assigned | due |
|---|---|---|---|---|
| lab04 | true | README w. Installation Instructions, Acceptance Tests, GitHub Actions | Thu 02/06 04:00PM | Thu 02/13 07:00PM |
| Points |
|---|
What you need to finish TONIGHT
-
Conduct a standup meeting (5-10 minutes)
-
Review your deliverables for lab03 beyond the retrospective you held last week
- creating a MVP column on the Kanban board
- tagging issues with a Github custom issue label MVP
- tagging user story cards with
(MVP) - Every team member is assigned to at least one issue that is part of the MVP and that this issue is either in-progress or done
- retro1.md documentation was logged as described on last week’s lab, including definition of an experiment
- everyone submitted a retro evaluation form
New this week:
- Complete – or schedule a meeting for – the sprint planning (generating/updating user stories, issues) for a successful MVP delivery ONE week from tonight. Reminder: Your MVP should deliver actual value to the end user
- Decide when to hold your next retrospective and put a card for it in the TODO column
- Designate a pair of Reviewers (Lead Reviewer, Reviewer Note Taker) and a pair of Reviewees in charge (Lead Presenter and Reviewee Note Taker) from your team for next week’s MVP Demonstration. Put a card with the names for these four roles in your Kanban ToDo column. See lab05 description for an explanation of next week’s process.
What you need to finish over the next week, to be demonstrated as part of your MVP release:
To document your MVP release — which you are delivering one weeks from today — your repository should have a complete README.md file:
-
Adapt this README.md template to document your project.
-
Specifically, list and test the complete installation instructions for checking out and building your project from scratch on a new device.
-
Log Acceptance Tests for all of your (MVP) user story cards
Getting Started with Github Actions:
- Read through and follow the steps in the Github Actions documentation
- Define and demonstrate at least one simple (but meaningful) custom workflow. You can look through the “Popular continuous integration workflows” section on the Actions (“Get started with GitHub Actions”) tab in your repo to get ideas or find starting point templates that fit your project…
Here’s what we’ll be looking for and grading:
Graded:
- (lab04) (10 pts) Next Retrospective scheduled and put on a card in Kanban ToDo column
- (lab04) (10 pts) MVP review roles have been decided and recorded on a card in Kanban ToDo column
- (lab04) (10 pts) Pre-MVP Sprint Planning Meeting took place and was documented in TEAM folder
- (lab04) (30 pts) README.md file was updated for your project with
- all the section from the template filled in (10)
- reproducible installation instructions that let a novice user build the MVP distro from scratch, simply by following instructions (20)
- (lab04) (20 pts) Acceptance tests were authored and logged for all your MVP user stories
- (lab04) (20 pts) Github Actions: first custom workflow was created and demonstrated