Years of software development experience in science, medicine, higher education, and business
Customer-focused, responsive, and collaborative teams
A proven success record solving problems
Knowledge and insight translating customer needs into software products
We believe in agile software development. Requirements change and so do we. Keeping updates small and frequent and keeping communication channels open result in more successful software.
SciMed has worked hard to create a structure that is agile and meets our client needs, our values, and the happiness of our developers. As a result, we’ve implemented an engagement process involving a project team, a standard engagement lifecycle, and documentation integral to the success of our engagement.
For a breakdown of this process, read on.
At SciMed, we recognize that you understand your business needs best. Following agile development principles, you are a crucial member of our integrated team! Depending on the size of the project, each contributor may wear multiple hats. Together, we construct a project team fulfilling each of these seven project roles.
Your product will be developed following SciMed's product lifecycle combining the best of hybrid and agile development models. We analyze your requirements and allow you to prioritize features to best meet your needs. We collaborate with your IT staff to enable a smooth transition from development to operation and remain committed to providing maintenance and product enhancements at your convenience.
At SciMed, we work to maximize the value you receive per hour worked, which means we only create the documentation needed to facilitate the project. Why document for documentation's sake? We believe in continuously updating living artifacts that reflect the current state of your product.
Not your ordinary project plan, our engagement plan covers the elements we need to have an efficient relationship, without all the fluff.
A treasure trove of information, we fill the requirements repository with only the artifacts needed to specify what the product should do and how it should work. This living documentation is regularly updated to reflect the current state of the product.
Well documented by automated test coverage, your code is maintained in source control with revisioning capabilities.