Agile Development

We follow the Scrum agile software development approach when building applications. This sees us working with our customer Product Owner to prioritize and organize work into 4-week ‘buckets’ of activity, called Sprints.

Design of features earmarked for the first sprint, otherwise known as the minimum viable product (MVP), are elaborated in the Sprint’s early days. The information architecture and content strategy are further detailed, as are the user interactions and user interface design to “photoshop” quality.

As coding of the features in the Sprint backlog gets underway, works-in-progress are shared regularly, blemishes and all with the entire project team, customer included. That way, everyone can see and comment on the mobile application as work is being performed. This surfaces issues early allowing for corrective action to be taken with little to no risk to the Sprint schedule or budget.

Customers can track progress throughout the Sprint by monitoring the sprint board that shows work unfolding through a To Do-Doing-Done sequence. The entire process is completely open and transparent.

At the end of the sprint window, a demonstration of all features developed during the Sprint is provided and a decision is made on whether to ‘ship’ the mobile application in its current state or hold back and bundle with another Sprint worth of features for maximum punch.

Finally, a continuous improvement activity called a sprint retrospective is performed to surface key learnings and improvements to be factored into subsequent Sprints.

Key artifacts delivered from our front end development service include:

  • Sprint backlog
  • Sprint plan
  • Sprint board
  • Acceptance criteria
  • Source code (product increment)
  • Sprint review
  • Sprint retrospective