Methodology
The implementation teams use a hybrid of waterfall and agile across all the parties. The actual development Scrum team either use Kanban or Scrum depending on their preferred way of work. Each team comprises of a few developers, a tester (within or assigned to the team) and a scrum master. We have multiple has a 2 week development
Product Owners
Product owners are assigned to various teams within the Technology Team and provide the documentation and clarity for the Technology team to implement. They own the backlogs for the team they are assigned to as well as the product they own.
They work with the business to identify new concepts,processes and ideas to implement. They handle this on a roadmapping tool called AHA
All created documentation is stored on the following share point site. Ignition Solution Hub
All userstories are translated and created on Azure Devops for the scrum teams to work on in terms of Epics–> Features–>User Stories –> Tasks .
Testing
The testing team adapts the Agile Methodology and all work allocated to the team should be allocated to a sprint User Story Task. All work needs to accompanied with a scope of work (i.e User story definition /BRS/ Technical Specification / Flow diagrams) The team will draw up their plan based on the scope provided. We provide the following types of testing
- Manual Functional Testing
- Compatibility testing
- Mobile testing
- Website testing
- Regression Testing
- Smoke Testing
- Automated testing (this is for the benefit of the internal testing team to automate their regression tests) using Selenium and Cypress.
- Entry Level Load testing using Jmeter