The client had an existing site which was running on a legacy platform that they wanted to move over to Drupal. There was a key requirement that multiple sites would need to sit on the same code base, so that the client could benefit by reusing functionality across a number of different sites, and we needed to develop with this in mind.
There were also requirements for a sophisticated workflow process to allow content to be properly moderated before it made its way onto the live site accessible by normal users. In addition to this there were a number of backend integrations that would be required to get everything working in the way the client wanted.
With this particular project we wanted to maximise what content editors could do on their own without the need for lots of technical training to get to grips with the new system. To aid in this we built the site around the concept of 'tiles' which are essentially distinct blocks of content that could be used to build up a rich, dynamic page whilst giving the content editor much greater flexibility over what elements were used and how these got rendered. This had the huge advantage of meaning that with minimal additional training content editors could create engaging content without the need for lots of technical know how.
When it came to implementing the frontend designs we leveraged modern web development techniques, using things like SASS to keep the style nice and tidy and reduce the amount of repetition in our code.
IBM Datapower Integration
Each sprint was tested in isolated with any bugs being fed back into to the development cycle to be fixed making extensive use of our internal issue tracking system. This approach meant that we were only ever testing a specific subset of functionality meaning it was less likely issues would be missed and they could be quickly fixed without having a huge impact of timescales or budget.
In addition to the robust process of manual testing, be that QA or UAT we also constantly sanity check our code using a suite of automatic tests such as unit tests, which make sure that nothing breaks as we add more code.
A Platform Solution
A traffic light system was implemented to allow content editors to clearly see what stage of the workflow process a particular piece of content was in at any given time. Once content moderators were happy with the content then they could authorise it to be published on the live, end user facing site.
Sprints could then be tested in isolation allowing us to incorporate any bug fixes or changes to the original requirements in subsequent sprints. The result is that at every stage we are moving forward, so for example we don't have to halt development whilst we wait for previous deliverables to be tested and fixed.