About
Kupsilla was founded with the idea that quality software can be made within predictable time and budget when skill and experience are combined together. Utilizing domain experience and large company technology acumen, we are right sized for the engagements where attention to detail meets scale.
20+
successful projects
70+
people
5+
years
How We Work
Productive Agile Approach
Kupsilla primarily works on projects in agile fashion. The agile methodology is followed as it allows the business to adjust its vision as requirements evolve.
There are times when agile software development lifecycle processes are not appropriate, e.g. GxP environments. In such cases, we design the solutions and assemble the teams to meet the client's requirements and follow their processes. It's highly unusual to see a client with a fully developed Business Requirements Specification or Functional Requirements Specification that are necessary for the waterfall approach.
Discovery
Prior to project engagement, Kupsilla conducts discovery workshops that serve to substantiate assumptions, establish the current state of affairs, and design the solution. Discovery workshops are a crucial step in the process of ensuring customer success.
The end result of the discovery workshop is a statement of work that defines the technology stack and project team needed to achieve the defined goals.
Kupsilla has a well defined discovery process that is tailored to each particular project.
Solution Delivery
Once the statement of work is finalized and signed, software development is started. Oftentimes, adjustments to the client's original vision and proposed team composition are made. Unless there is a clearly defined large scope to work on, we follow the crawl-walk-run approach of ramping up the team over a period of time.
The gradual ramp up process allows the project team to iron out any early onboarding issues with the smaller affected team, build the well defined scope, setup infrastructure, and establish the proper cadence. This approach has an additional benefit of being more helpful for the client's budget.
The composition may further fluctuate throughout the project depending on the business goals and the skills needed at the time.
The development process normally follows scrum practices. Adjustments are made in order to match those of the client if needed. Requirements are normally managed in a wiki-like system (e.g., Confluence), issue tracker is used (e. g., Jira), as well as code versioning system (e. g., git), and build and deployment solutions. Those can be either on the client's or Kupsilla's side. Weekly managerial check-ins are implemented on top of scrum ceremonies.
Support and Maintenance
When the solution is ready to be deployed to the end users, Kupsilla provides user training and creates the necessary end user documentation. After the deployment, Kupsilla provides support and maintenance as required.
Kupsilla maintains documented project history and institutional knowledge so developed applications can be extended with new features and functionality as the end user business processes evolve.
