QualityAssessmentChecklist.md

[katherinemendel]

Team Culture:

• [x] Build team culture through non-work activities.
• [x] Regularly recognize and complement team members for their contributions.
• [x] Respectfully provide coaching to improve team effectiveness and efficiency.

Communication:

• [x] Set up and use communication tools and processes for effective and rapid information exchange.
• [x] Use these tools and processes regularly.
• [x] Establish and use remote communication tools and processes for distributed team interactions.
• [x] Establish and use initiation and exit checklists.
• [x] Establish and use team policy statement.

Testing:

• [x] Design and execute tests for confirming refined user stories match initial user stories.
• [x] Design and execute tests for confirming design matches refined user stories.
• [x] Design and execute tests for confirming implementation matches design.
• [x] Create basic execution test capabilities.
• [ ] Create comprehensive test capabilities.
• [x] Create and regularly use unit testing.
• [x] Use a pull-request, code-review integration process for source changes.
• [ ] Automatically monitor and report code coverage.
• [x] Use test-driven development.
• [ ] Measure and track software performance.

Requirements and Analysis:

• [x] Create user stories to capture basic product requirements.
• [x] Analyze, refine, prioritize, select and convert user stories into tasks for development.
• [x] Organize tasks into Epic-story-task packages.
• [x] Experiment with Job Stories as an alternative to User Stories (see https://maherou.github.io/files/CS317/CS317-Links).

Design:

• [x] Create basic design documents such as class, interaction and use case.
• [x] Write lightweight design documents
• [x] Write throw-away prototype code to explore high-risk design elements.

Development:

• [x] Create GitHub Isses describing major design and development tasks.
• [x] Establish GitHub Project (Kanban) board.
• [x] Actively manage work by tracking issues on your Kanban board.
• [x] Conduct regular project meetings to assess progress and manage schedule.
• [ ] Use code formatting tool to assure uniform source code.
• [x] Identify and use a coding convention.
• [x] Develop in-source comments that can be used to generate documentation, e.g., Javadoc or Doxygen.

Product Release:

• [x] Create a unique and traceable release of your software product.
• [ ] Make a citable version (with DOI) of your code and make it available on Zenodo or Figshare.
• [x] Generate user and developer documentation.
• [x] Create product branding, e.g. logo family, catchphrase, product description.

[katherinemendel]

Experiment with Job Stories as an alternative to User Stories

https://livecsbsju-my.sharepoint.com/:w:/g/personal/ndrees001_csbsju_edu/Ea-18WwN9MxPn-jrJV2yIwoB9KQTYBm8Z0mVtK-UOpPNjw?e=ij6JhD`

[katherinemendel]

Use a pull-request, code-review integration process for source changes

See pull request #13

[katherinemendel]

Build team culture through non-work activities

See picture for team dinner

[katherinemendel]

Write lightweight design documents

https://github.com/404NameNotFound404/MarchMadness/wiki/Design-Document

[katherinemendel]

Analyze, refine, prioritize, select and convert user stories into tasks for development.

https://github.com/404NameNotFound404/MarchMadness/projects/1

[katherinemendel]

Regularly recognize and complement team members for their contributions.

Comments on closed issues such as #23

[katherinemendel]

Respectfully provide coaching to improve team effectiveness and efficiency.

Slack channel and comments on some issues

[katherinemendel]

Set up and use communication tools and processes for effective and rapid information exchange. Use these tools and processes regularly. Establish and use remote communication tools and processes for distributed team interactions.

Slack channel

[katherinemendel]

Establish and use initiation and exit checklists. Establish and use team policy statement.

In TeamDocuments repo

[katherinemendel]

Create GitHub Isses describing major design and development tasks. Establish GitHub Project (Kanban) board. Actively manage work by tracking issues on your Kanban board. Conduct regular project meetings to assess progress and manage schedule.

See Kanban board

[katherinemendel]

Develop in-source comments that can be used to generate documentation, e.g., Javadoc or Doxygen.

Using Docstring module in python

[katherinemendel]

Use test-driven development.

testMasseyMethod.py written before MasseyMethod.py

[katherinemendel]

Create and regularly use unit testing.

Using unittest package in python - see test files such as testMasseyMethod.py