The team here at Boxmodel work using agile scrum methodologies. We utilise Team Pulse software by Telerik to organise our work flow. We create products our customers need, when they need them, by capturing their feedback using sprints and iterations.
The team really enjoy working in this process as it benefits both parties. Potential problems are quickly identified and rectified. Clients also get to witness individual snippets of their digital product en route to agreeing the larger or overall product.
Here's a breakdown of Boxmodel's agile scrum process.
The Agile process for communications and information sharing
Agile is a software development methodology. It is important to understand the practice to discern the benefits for both us, as the software developers, and our clients, the business owners. The key principles of the methodology allow us to:
The methodology is an iterative process, which allows us to break the project down into smaller tasks with deliverables at the end of every iteration (called “Sprints”) which would typically last 3-5 weeks on a project of this scale. At the end of each iteration there would be demonstration of the software and a feedback period, whereby clients can add feedback, comments and ideas to our feedback portal.
Our feedback portal is the main avenue of communication and information sharing with regards to the software development process, allowing you to add feedback and ideas and allows parties to comment and discuss items. These items will undergo a “triage” process, allowing us to consider these items for the next “Sprint” (iteration). This iterative process allows us to work closely with and be in regular communication with you, to ensure that the project is meeting requirements throughout the development lifecycle.
Agile and technical specification alignment
Agile is specifically geared to ensure that the software delivered is aligned to the requirements of the business throughout the lifecycle of the project.
This means that rather than planning the software in elaborate and great detail initially, manageable iterations of the software are planned, developed and demonstrated to ensure early and maximum visibility during the project. This allows for changeable priorities with regards to key business requirements. This also allows the focus of development to be changed as necessary and quickly. This opposes old school methods of waiting for the entire project to be delivered, only to realise it meets the business requirements of 12 months ago, when it was initially proposed, but unfortunately does not now meet the current business requirements.
The methodology allows the business requirements to influence the entire development of the project and can be used to provide insight on the best way forward continuously, when compared with traditional methods, which only allow the business requirements to influence the initial specification of the project and not throughout the development time frame.