Active Outsource Development Sprints
The Mercury Platform was designed for the outsourcer/client relationship. Over years of crafting this solution, the Mercury Platform shines during the sprint. Not only does it greatly reduce (even eliminate) the chance of clients changing sprints and not being on the same page about deliverables of any given sprint, but the team and client have seamless contact for true collaboration without tech overload.
The Mercury Platform integrates client-friendly and technical to make your sprints more agreeable and profitable for you and your client.
Technical vs Client-Facing
The most important way the Mercury Platform teases apart the communication in order to ease the client's ability to keep control of the development process but not hinder it or be burnt out. The Mercury Platform allows for completely parallel and connected tasks that are for different levels of technical expertise.
There are 3 available dashboards. The client and the rest of the team can see Overview and History, but Development is only accessible by Team Admins, PMs, and Developers on this project. This ensures technical conversations stay away from the client to avoid burn-out.
The development dashboard gets items on it when a sprint on Overview dashboard has been started (the button "start development" is clicked). These items are a direct copy of the sprint's items on the client-facing Overview dashboard allowing you to have developers, team admins, and PMs talk technical details out of the view of the client but still having direct access to the items the client is viewing.
Item Movements During a Sprint
When development is making sure everything is in order and understood items are moved in sprints or individually into the "Ready to Develop" column. Meanwhile that sprint and their brothers and sisters in the sprint on the "Overview Dashboard" that the client can see doesn't move.
Once the developer(s) is/are happy with the items and begins work on the sprint item-by-item. They then move the items (by sprint or one at a time) into the Development Dashboard's "In Progress" milestone. This is when the Overview Dashboard (and therefore the client) sees items and sprints move into the "In Development" column.
When finished and all items are "In Development" the developer can click "Send to Client" and seek approval on the Overview Dashboard. If rejected, the items go back to Technical Staging and Ready to Develop on the Overview and Development Dashboards, respectively.
If the client approves the sprint, all the items are moved (with comments & sprint-level chat) to the History Dashboard. In History, items are frozen for all of time with a time-stamp of the date and time it was completed.
This acts as an immutable source of information for disputes, building out other operating systems, or any other reason you'd need to know exactly what happened and was talked about first-hand. Everyone can see this all important board leading to a great sales tool making clients feel at ease with the transparency and record that firms not using the Mercury Platform just can't offer.