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 Agile process HDX uses is broadly similar to Scrum, a framework to support teams in complex product development. In Scrum, the time available to work is broken down into time periods known as Sprints of two weeks during which a “Done”, useable, and potentially releasable product Increment is created. It is helpful to look at a diagram of the Scrum Framework.

Roles

Customers (

...

including Sarah)

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 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)

The Product Owner is responsible for maximizing the value of the product resulting from the work of the Development Team. She is the sole person responsible for managing the Product Backlog which includes:

• Liaising with Customers to understand their requirements.
• Clearly expressing Product Backlog items.
• Ordering the items in the Product Backlog to best achieve goals and missions.
• Optimising the value of the work the Development Team performs.
• Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next.
• Ensuring the Development Team understands items in the Product Backlog to the level needed.

...

No one can force the Development Team to work from a different set of requirements!

Scrum Master (Dan) 

The Scrum Master is a servant-leader for the Scrum Team. He helps those outside the Scrum Team understand which of their interactions with the Scrum Team are helpful and which aren’t and encourages changing these interactions to maximize the value created by the Scrum Team. He helps the Development Team to create high-value products and removes impediments to their progress.

...

• 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.

...

The Daily Scrum is a 15 minute event for the Development Team to discuss:

• The previous day's work.
• Progress toward the Sprint Goal.
• Work for the next 24 hours.
• Any impediments to progress.

...

• Inspect how the last Sprint went with regards to people, relationships, process, and tools.
• Identify and order the major items that went well and potential improvements. 
• Plan ways to increase product quality by improving work processes or adapting the definition of "Done" if appropriate and not in conflict with product or organizational standards.
• Enumerate improvements to its development process and practices to make it more effective and enjoyable for the next Sprint.

...

Demo to HDX

...

(+2 weeks)

A demo is scheduled at the end of the Sprint so that any new features can be shown to the wider HDX Team which offers . This is an opportunity for discussion and feedback on the changelist.