Code: game1
Size: 1
Dependencies: none.
Rename:
• ’Wizard’ to ’Captain’
• ’Band’ to ’Squad’
• ’Apprentice’ to ’Ensign’
to more accurately reflect specification.

Code: form5
Size: 3
Dependencies: None.
Write a config file and use it to determine what port to serve to and other
variables that may change. Configuration changes should not require edition
of the source code.

Code: form1
Size: 5
Dependencies: None.
All code that handles persistent storage should be within its own source file.
This should then be imported into the main source file.

tool1- Dependencies: None.
Write a README detailing dependencies. This should say that Python and
PIP are system requirements, giving versions. It should further describe how
to install Flask using

Sprint 2

This issue documents the planning for sprint 2.

Sprint 1 achieved what was intended. All tasks listed as defined in are now complete. For details see the planning document in /doc/ dir.

The most pressing issue deemed to be addressed are:

• Abstracting game rules to a separate file (form2).
• creating a build script (tool6)
• writing some unit tests (tool5)
• Linking github to CI server (tool3)

This will be quite an intensive sprint but should leave code in much better shape. As with sprint 1 priority is given to getting code to a higher quality so that it can be extended in dialogue with a customer and/or end user.

Code: bug2
Size: 3
Dependencies: form1.

Error when writing new file for new squad. This appears to happen when the
form is incorrectly filled. Instead there should be an error message clearly
explaining to the user what is wrong. For ease, development work on this
should happen after data handling code has been abstracted out.

IOError: [Errno 21] Is a directory: u’~/project/bands/’

Code: form3
Size: 1
Dependencies: None.
Make sure lines do not exceed a certain length in source. Make sure all lines
are indented to the correct degree.

Code: tool4
Size: 2
Dependencies: None.
GitHub also has issue tracking built in. The tasks outlined in this section
should all be entered into this.

Code: tool3
Size: 3
Dependencies: tool2.
Use Travis CI to run a build script every time source is pushed. At first this
can just check that the code runs in Python without errors, later it should
run a suite of unit tests. Even later it could also run integration/UI tests.

Code: data1
Size: 3
Dependencies: form1.
Determine what best option long term for data storage is. Possibilities in-
clude SQL database, JSON flat files, XML flat files.

Code: form2
Size: 5
Dependencies: None.
All code that implements game rules should be within its own source file.
This should then be imported into the main source file.

Code: bug1
Size: 1
Dependencies: None.
Rename this to something sensible, such as ’Home Page’.

tool6
USe virtualenv and pip to install dependencies.

Code: form4
Size: 2
Dependencies: tool3, tool2.
Find a suitable linting tool for Python and run it on all sources from within
the build script.

Code: game2
Size: 3
Dependencies: None.
Write a config file and use it to determine what characters cost and their
attributes. It should be possible to change these without editing source
code.

make sure any data stored during testing is not version controlled.

Sprint 2 review

It seems reasonable to call sprint 2 a success as all the issues were resolved. The unit test coverage as in #5 is pretty limited but this should be added to as work progresses.

Sprint 3

Sprint 3 will involve completing all remaining issues.

Code: tool5
Size: 2
Dependencies: tool3, form1, form2.
Write a suite of tests and run these in the build script. Also include test
coverage report if possible.

Code: tool2
Size: 1
Dependencies: None.
Git is an obvious choice for a source control tool. It is completely dominant
and the author is familiar with it. A GitHub account already exists for code
to be uploaded to.