forked from magagr/adp_project
-
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.
Draft project requirements for magagr#2, write up remains.
- Loading branch information
Showing
1 changed file
with
34 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,34 @@ | ||
# Project Meta Requirements | ||
|
||
- git and github for version control | ||
|
||
- issue tracker | ||
- prioritized product backlog | ||
- sprint commitment | ||
- should have automatic traceability to git commits | ||
- suggestions: github issue tracker or Trello | ||
|
||
- Continuous Integration | ||
- use for example Travis-CI | ||
- lots of alternatives covered by https://github.com/larsbrinkhoff/lbForth | ||
|
||
- repository, issue tracker, and build should be accessible | ||
without any licence restrictions, | ||
for all group members and supervisors | ||
|
||
- Agile Practices - all should be possible to use in the project | ||
|
||
- Vertical slice, customer value every sprint | ||
|
||
- GUI | ||
|
||
- Tests for "all" code, for some definition of "all" | ||
- Logic/behaviour to test | ||
|
||
- The software should be runnable by the supervisors, | ||
platform independent. | ||
|
||
- Knowledge transfer within the group. | ||
Use the Agile Practices for this, | ||
for example pair programming, | ||
integrate into group work. |