Developing a product is an empirical process that involves frequent calibration based on the feedback acquired during development. Ensuring that there is enough feedback from both internal stakeholders and external users during the development process significantly improves the likelihood that the resulting product meets expectations and satisfies its users. Great products aren’t created in a vacuum.
Our designers produce artifacts "just in time" at the level of fidelity necessary to communicate ideas, not more. In some cases a white board sketch is appropriate, in other cases a detailed wireframe and in others, a fully-realized composite sketch. And what better way is there to be prepared for a product launch then to invite real users to use the product during development of the product? We set a goal of having a version of your product that is ready for early users to use in the first couple of weeks so that we can bootstrap the process of collecting feedback.
At Carbon Five we have adopted and mastered an Agile methodology that faces the challenge of building great software head on. The central feature of this practice is short development cycles that feature a range of feedback mechanisms designed to improve the efficacy and reliability of subsequent iterations. How we work with our clients and implement their requirements evolves and improves during the course of the project. This reduces the risk of software development by focusing on client priorities and providing high visibility into project progress.
At Carbon Five, we bootstrap companies and development efforts by combining outsourced development services with process and technology training. We staff projects with seasoned teams of developers experienced in Agile development practices and use a standard suite of open source technologies well-suited for a rapid rollout. As the client hires developers, we include them on our team, at our offices. As integrated team members, our client's developers are trained on the processes, tools and technologies they will need to continue development after version 1.0 and beyond.