...
In HDX, the development process is Agile and the audit trail for the work done is held in JIRA Jira in the form of issues, which are the fundamental units of work/planning information in JIRAJira. Where issues are part of a larger piece of work they are grouped under an epic.
...
Jira Issues
The start of the development process is the entry of issues into JIRAJira. Issues can be one of three different types:
...
The Customers are the source of requirements. They are not in the Scrum Team and hence do not attend Sprint meetings. Their connection to the Scrum process is by:
- A separate process by which ideas are floated, filtered and then broken down into JIRA Jira issues.
- Interaction with the Product Owner detailed below.
It is crucial that the only channel customers have to obtain developer time is by the creation of Jira issues so that all work is visible and tracked within the Scrum process. Any customer not comfortable with Jira should ask Godfrey for support in writing issues.
Scrum Team
Product Owner (Yumi)
...
- Ensuring that goals, scope, and product domain are understood by everyone on the Scrum Team as well as possible.
- Finding techniques for effective Product Backlog management.
- Helping the Scrum Team understand the need for clear and concise Product Backlog items.
- Understanding product planning in an empirical environment.
- Ensuring the Product Owner knows how to arrange the Product Backlog to maximize value.
Development Team (Arti, Alex, Dan, Serban)
The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of "Done" product at the end of each Sprint. Only members of the Development Team create the Increment. They are self-organizing: no one (not even the Scrum Master or Product Owner) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality.
...
A demo is scheduled at the end of the Sprint so that any new features can be shown to the wider HDX Team offering . This is an opportunity for discussion and feedback on the changelist.