| Previous Lecture | lect06 | Next Lecture |
lect06, Wed 01/30
Upcoming: Sprint Planning, Retro, MVP
Review of the big picture
| platform | count |
|---|---|
| C# Unity | 2 |
| ioS Native | 2 |
| node.js | 2 |
| Flask | 8 |
The Kanban board
- What does it mean to be “done”
- That’s an unresolved question
- We are going to explore that in much more detail
- The three columns we started with are going to turn out to be, perhaps not quite enough
- Stay tuned:
- Acceptance tests/criteria
- Code review
- Continuous integration
- “Definition of Done”
Review of last time
Guest Presenter: Kate Kharitonova
Some clarifications:
- The “Gems” section should really be “dependencies”.
- What programming languages and frameworks are you using?
- “Gems” is a Ruby specific way of saying this.
- Remove “Gems” if you aren’t using Ruby, and replace it with Dependencies
-
Make things like node.js, React, etc. hyperlinks to those frameworks, not just words.
-
The README.md is a developer facing document, not a user facing document.
- “What do you need to install? Nothing! Just use a web browser”
- FALSE. That’ may be true for the end user.
- But if you are developer, you need at least the toolchain for your language and framework.
- “What do you need to install? Nothing! Just use a web browser”
- There shouldn’t be any “TODO” stuff in your document as delivered.
(I’ll be adding a rubric for these README.md’s into a future lab.)