-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Trying to fix merge conflict, adding meeting notes
- Loading branch information
1 parent
870edbf
commit 21529cc
Showing
1 changed file
with
14 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
09/16 Meeting Notes | ||
|
||
EVERY commit must be assigned to a user story - this includes random file deletions, | ||
bug fixes, etc. Assignments can be made by using # plus the issue number associated | ||
with the user story. | ||
|
||
At the end of a sprint, the only things graded are the Master branch and ZenHub. | ||
|
||
User stories should have a simple, informative title. The actual story part following the | ||
"As ___, I want ___, so ___" should be in the comments. | ||
|
||
Acceptance tests should be attached to the bottom of all "completed" user stories. | ||
Can be as simple as links, but must outline the process to verify that a user story | ||
has actually been completed. |