At Software Planet, we take great pride in our customer-centric development process. This is why from start to finish, a striking sense of partnership is present in all we do.
The first step in our development process is the planning and estimating phase, where multiple things occur. We create user stories, define our acceptance criteria and put together valuable estimates. We also make use of system metaphors.
Next, we draw up a highly flexible Time and Materials (T&M) contract. Under this model, because our customers only pay for our expertise and the work that they wish to complete, they are given the power to direct and scale development in any way they like.
We work in one to two-week iterations known as Sprints. Each Sprint leads to a potentially shippable product — with fully working functionality — which in turn provides our customers with the freedom to decide whenever they are ready for their first official release.
When development proper begins, the first thing we must do is define our Sprint goal. This spells out the main objective that our developers will be striving to meet in the current iteration. In order to define it, we invite our customers to a Sprint planning meeting, where our team members can then discuss your project’s iterative scope.
At the end of each iteration, we summon everyone together for a show of demonstrable updates. These demo meetings are a time to gauge overall progress, evaluate performance, compare original goals with what has actually been delivered and above all, receive critical feedback that will help us moving forward.
While our demo meetings are primarily geared towards customers, Sprint retrospectives are periodical reviews in which developers evaluate their achievements. In these events, we ask open-ended questions to reveal the root cause of our problems, and size up every aspect of development, from budget, to timeline, to goals.
To certify that no problems will arise after deployment, we may also make use of a staging environment. This closely mirrors our customer’s own in-house settings, enabling us to address a variety of different issues in load-balancing, security and scalability.
We have found that the best way to work with designers is for all of the UI/UX work to be prepared a Sprint ahead of development. This makes planning an essential part of synchronisation for both designers and developers.
And finally, in our Quality Assurance testing stage, we do everything in our power to guarantee the business value of your projects. Our teams unflaggingly scrutinise every aspect of your product’s development and determine if the users’ needs are being adequately met.