Requirements Management

Functional and technical requirements are tracked in Jira as Functional Stories and Technical Stories. A Functional Story is a description of some end-user facing functionality. A Technical Story describes technical features, design concepts or requirements.

Development Workflow

All development work is tracked in Jira as Bug, Task, Improvement, or New Feature issues. These issues all follow a similar workflow:
Start!
* Create Bug, Task, Improvement or New Feature issue
* Link issue with Functional Story or Technical Story
* Estimate time required to complete issue
Work!
* Assign issue to yourself
* Mark issue as started
* You should only have one issue marked as in progress at a time
* If you stop working on the issue (e.g. to pick up another one), log work done (you can check this through mylyn) and mark issue as no longer in progress
Done!
* Indicate what tests have been implemented for the issue in the Test Coverage field
* Mark issue as Resolved
* Log work done (you can check this through mylyn)
* Set work remaining to 0
* Assign to Customer resource to validate
Verify!
* Check test coverage
* Validate observed functionality against linked Functional or Technical Story