Our Process

[blox_row fullwidth=”true” image=”http://devalldigital.com/wp-content/uploads/2014/10/header-blog.jpg” bg_repeat=”no-repeat” bg_position=”left top” bg_attach=”scroll” text_light=”1″][blox_column width=”1/1″ ][blox_text animation=”none”]

Our Process

[/blox_text][blox_text animation=”none”]

Developed from our years of industry knowledge designing, building and running some of the largest online services deployed today

[/blox_text][/blox_column][/blox_row][blox_row fullwidth=”true” color=”#ffffff” text_light=”0″][blox_column width=”1/1″ ][blox_text animation=”none”]

There are lots of ways to design, build and run software. Running feature rich applications to large global audiences on a myriad of devices requires a solid processes and business systems. AllDigital’s process was developed from our years of industry knowledge designing, building and running some of the largest online services deployed today. We constantly improve with industry feedback and performance benchmarking. Well written and documented code deployed to state of art cloud infrastructure produces project calendars that are accurate and services that beat demanding consumers’ expectations. 

[/blox_text][/blox_column][/blox_row][blox_row columns=”1/4+3/4″ fullwidth=”true” color=”#ffffff” text_light=”0″][blox_column width=”1/4″ ][blox_image image=”http://devalldigital.com/wp-content/uploads/2014/10/ADprocess11.jpg” img_width=”176″ alignment=”right” target=”_self” animation=”slideInLeft”][/blox_image][/blox_column][blox_column width=”3/4″ ][blox_text animation=”slideInRight”]

Each integration services client is assigned a dedicated project manager who is the voice of the customer, and is accountable for creating and prioritizing user stories within the product backlog.

  1. The product owner defines the initial acceptance criteria for each story, and is responsible for completing the acceptance criteria before sprint planning
  2. The product owner consults the relevant subject matter experts to obtain a high level estimate of complexity (in story points)
  3. The product owner works closely with the stakeholders to manage the priority of the user stories

[/blox_text][/blox_column][/blox_row][blox_row columns=”1/3+1/3+1/3″ fullwidth=”true” color=”#ffffff” text_light=”0″][blox_column width=”1/3″ ][/blox_column][blox_column width=”1/3″ ][blox_image image=”http://devalldigital.com/wp-content/uploads/2014/10/ADprocess2.jpg” img_width=”176″ alignment=”right” target=”_self” animation=”slideInLeft”][/blox_image][/blox_column][blox_column width=”1/3″ ][blox_text animation=”slideInRight”]

The project is split into many iterations known as ‘sprints’ which represent a time-boxed effort, each restricted to the same duration (typically 2 weeks).

[/blox_text][/blox_column][/blox_row][blox_row columns=”1/3+1/3+1/3″ fullwidth=”true” color=”#ffffff” text_light=”0″][blox_column width=”1/3″ ][blox_image image=”http://devalldigital.com/wp-content/uploads/2014/10/ADprocess3.jpg” img_width=”176″ alignment=”right” target=”_self” animation=”slideInLeft”][/blox_image][/blox_column][blox_column width=”1/3″ ][blox_text animation=”slideInRight”]

QA take the acceptance criteria of the prioritized user stories from the product backlog, and create automated acceptance test scripts

a. QA design a comprehensive testing plan for each story

[/blox_text][/blox_column][blox_column width=”1/3″ ][/blox_column][/blox_row][blox_row columns=”1/3+1/3+1/3″ fullwidth=”true” color=”#ffffff” text_light=”0″][blox_column width=”1/3″ ][/blox_column][blox_column width=”1/3″ ][blox_image image=”http://devalldigital.com/wp-content/uploads/2014/10/ADprocess4.jpg” img_width=”176″ alignment=”right” target=”_self” animation=”slideInLeft”][/blox_image][/blox_column][blox_column width=”1/3″ ][blox_text animation=”slideInRight”]

Given the known user stories on the product backlog, an architecture and approach is defined.

[/blox_text][/blox_column][/blox_row][blox_row columns=”1/4+3/4″ fullwidth=”true” color=”#ffffff” text_light=”0″][blox_column width=”1/4″ ][blox_image image=”http://devalldigital.com/wp-content/uploads/2014/10/ADprocess5.jpg” img_width=”176″ alignment=”right” target=”_self” animation=”slideInLeft”][/blox_image][/blox_column][blox_column width=”3/4″ ][blox_text animation=”slideInRight”]

A sprint planning session is carried out on day 1 of each sprint where the entire team meets to discuss and plan the upcoming stories.

  1. The team is a cross-functional team, and may exist of project managers, developers, QA, architects and sysops
  2. The entire team, including the product owner, attends the sprint planning session
  3. The team discuss the acceptance criteria with the product owner, asking any questions that may be arise
  4. By the end of the sprint planning session, the team are responsible for breaking down the user stories into tasks, and providing an estimate in terms of effort (time based)
  5. The team commit to an amount of work that they feel they can develop and test by the end of the sprint. This committed list becomes the ‘sprint backlog’

[/blox_text][/blox_column][/blox_row]