Development Process

Software development is a team game. The team at Hero consists of several disciplines and we have designed a development process that aims to make the release of new features and requests as efficient and effective as possible. This page is aimed at anyone who is interested in understanding more about how our software solution is delivered to our end users.

Sitting behind our process are some key beliefs.

  • User feedback is essential.
  • Development Priorities are decided by the team.
  • Testing is fundamental to quality development.

To illustrate our process we use the analogy of a child moving through the schooling system. This is the process that is followed for every request for development that is raised.

  1. Birth


    A request is born when one of our users or a member of our internal team creates a new ticket.

  2. Early Childhood


    In this stage, the request is waiting to start their schooling and to be prioritised by our team.

  3. Starting School


    Each week our team meets to discuss all of the requests that are about to start and agree on which ones should take priority. During this meeting, we also agree on the testing that will need to be completed. Prioritisation takes in a number of factors including how many users have requested the feature, the complexity of the feature.

  4. Learning and progressing


    At this stage, our development team are actively working on writing the code!

  5. Peer Review


    A key part of the process is Peer Review, our developers review each others code and check that is ready to be tested.

  6. Testing


    Our consulting team test the work to make sure that it meets the expectations that had been set.

  7. Graduation


    The graduation process is where we produce the documentation that goes with the release.

  8. Finished


    At the end of the process, the feature is released live to our users. We release each week and this is accompanied by a set of release notes.