Q.) Do you have expertise in relevant technologies and programming languages?
Q.) Do you have experience integrating your developers into pre-existing teams?
A.) Yes, we’re prepared to augment existing teams and/or carry projects from inception to completion or an established hand-off point to an internal team.
Q.) How do you evaluate the complexity of projects and manage resources to estimate project requirements and risks?
A.) We use a cross-departmental collaboration in which we evaluate the features from both a design and development perspective. We enumerate everything that needs to be built or considered, and create personnel allocation estimations, both in time and level of expertise (i.e. architect time, senior developer vs. junior developer, senior design vs. junior design, etc.).
Q.) What software development life cycle methodologies does your organization subscribe to?
A.) We utilize the Agile Methodology for project management. We “build, measure, and learn” and integrate user feedback within the subsequent Iterations.
Q.) What project management and tracking systems do you use to ensure timely delivery schedules?
A.) We primarily use JIRA for design and development team tracking. We generate a firm roadmap up front to provide all stakeholders with a shared understanding of project requirements and expectations. This collective understanding helps us and our Client(s) avoid scope creep.
Q.) How does your company ensure consistent standards throughout different services?
A.) Standards of service, acceptance criteria, and a “Definition of Done” are established for each project. As a general rule, every project requires testing and validation, but which types and how often vary based on Client/project requirements.
Q.) What tools do you use for quality assurance?
A.) We use functional testing, performance audits, user acceptance testing and implement additional measures as necessary.
Q.) What documentation standards do you produce for quality control?
A.) We determine a code style and a “Definition of Done” to benchmark against during development of Sprint deliverables.
Q.) Share an experience of delivering outcomes with Test Driven Development (TDD) and Behavior Driven Development (BDD) approaches.
A.)Test-Driven Development helps with back-end APIs to ensure inputs are handled correctly. We’ve seen success in utilizing Behavior-Driven Development to create requirements for both design and developers to meet project objectives.
Q.) How do you manage performance and test security (stress, load, volume)?
A.) To date, our Clients haven’t required extensive security testing, but we have the capacity to expand on these services as requested.
Q.) How do you minimize attrition and maximize business continuity?
A.) We’ve worked hard to develop and maintain an employee-centric culture at Sproutly.io. We offer our employees great benefits, work-from-home/remote flexibility to retain our talent and attract professionals with a variety of skills.
Q.) What is your typical ramp-up time for resource supplement?
A.) Two to six weeks to hire; two to twelve weeks to ramp up.
Tell about the capabilities and expertise in the following areas:
Automated testing/deployment/continuous integration
Automated testing and deployment are part of every project we work on. We use unit and functional testing along with continuous integration build servers to ensure code quality and functionality.
Performance and load examination
We utilize available instruments within a given platform to measure performance. When problem areas are identified, we implement strategic changes to fix bugs and/or delays.
We use in-line, auto-generated documentation for APIs. We document architecture and training material separately.
We’re familiar with basic security guidelines and can implement more in-depth security features upon request.