We follow a structured approach to have a organised delivery. Every step in the process is clearly marked by requirement and expectations. The primary goal is to have the requirements broken in to user stories and Epics (Group of related user stories) stored in Product Backlog. The work is organised in fortnightly periods called Sprints. With the start of every sprint the top priorities are defined by the product Owner and the tasks are organized and completed within a Sprint. This process ensures that the development is carried out in a timely and orderly manner.
- Agile Manifesto
A detailed day long interactive workshop is organised to gain insight on the product requirement and core components of the business. The team as a whole is part of the workshop. The Project Manager, UX Designer, Lead Developers and other important key people from the project attend the workshop. This workshop can be arranged at our office in Pune or at the client location. To emit the travel barrier and for clients outside Pune, we can even set up Skype calls. The exercise is to gain intensive insights and then process the requirements into Epics, User Stories and Journeys ensuring a water-tight implementation. Subject to these insights we gain from the client, we build a creative approach to the project.
Based on these initial discussions and style guidelines, we will establish a creative approach that is most beneficial to the project, populate backlog and generate wireframes for the upcoming website.
User stories are created, clearly described and captured, such that all aspects are addressed and stored in Product Backlog.
User Story format:
As a [role] I want to [task] so that [goal].
User Story Example:
As an analyst, I want to identify the trending patterns of this product and market reach to suggest newer markets and promotion mediums.
Every fortnight, the team estimates the complexity of every User Story in the Product Backlog.The team defines the details of User Story like goals, expectations, criteria, description and process.
At the beginning of every sprint, a sprint planning meeting is arranged. Here the product owner lays down the priorities on User Stories and estimated time and effort at executing each User Story. Emphasis is given on analysing the efforts and time required in the previous Sprints, to reach a measurable statistics. The team then mutually decides on the number of User Stories they can execute in a Sprint.
A Scrum process has Sprints which are series of iterations executed after one another. Every Sprint is initiated with a Planning Meeting, necessary to evalute a sprint backlog. Backlogs are list of task to be done/performed during the sprint, and a outcome that should be attained by the end of the sprint.
Additionally, every day a crisp stand-up meeting of 15 minutes is held to monitor the day wise progress. The members come prepared with their individual updates, hurdles and queries if any.The project progress is assessed on the following parameters-
Inspect and adapt THE PRODUCT.
The sprint review meeting is held to review and validate on the work finished and obtain feedback from project stakeholders - the Product Owner.
Inspect and adapt THE PROCESS.
This is purely a review ground to bring in the feedback from the past sprint cycle, valuable contributions in terms of increased optimisation, issues faced and addressed and effective solutions. This feedback system helps improved future Sprint cycles.
The products are split in increment for the ease of working. Finished set of working product increment (Piece of working software) is the primary and ultimate goal of every sprint. A working product increment adds to the previously created increments and they all sum up to a whole product.
Adapting to technology and changing scenarios is development. We ensure the product is tested to fit across different browsers and dynamic screen statistics. We ensure the products are tested across tablets, phones, desktops, gaming consoles and TV's.