Our engineers are passionate about technology, many have advanced degrees in Computer Science (CS) and they continue to be pioneers and thought leaders in their field.
Our clients are serious about building apps that look good on the outside and function seemlessly on the inside as well. We build apps for long-term growth and stability. This is where our experience counts, we’ve been around the block a few times and we know that works best.
We are proud of the fact that we still retain and service many of our old clients. Our clients tell us that it is comforting to know that they can pick up the phone and talk to someone even after a few years have gone by.
We sit with you either in person or virtually to discuss the initial requirements of the project. Most of our clients come with pre-formulated requirements that they’ve been working on Prior to meeting us. Notes, sketches, mindmaps are all very helpful at this stage. We want to understand the big picture, what problems will this app solve, who would be the end users, what technology is required to solve the problem etc.
From our Requirements meeting/s we formulate a Business Requirements Document. Business Requirements are what must be delivered to provide value and success. Stakeholders provide the guidelines for the BRD.
We collaborate with our clients in creating Functional Specifications Documents (FSD) and Non Functional Specifications Documents. Typically FSD will define behavior or functions. NFSD will define how the system should work.
Steps 2, 3 and 4 are highly interconnected. In some projects defining a Minimum Viable Product also known as MVP, is the first step in the process of kicking off a project. What is an MVP? It is the minimum feature set that is required to get your product in front of customers, so that they can try it and give you feedback and you can improve your product further. Build-Measure-Learn feedback loop. Similar to how it is defined in the Lean Startup book by Eric Ries (we highly recommend this book for anyone starting a new app project).
In this step our User Interface (UI) designers sketch out the important user interface elements of each of the screens on the application. This is similar to how an architect would rough sketch a house before moving on to full design. Wireframing allows us to see how a user will interact with the system and also correct any potential barriers to them using the system. Working with an experienced UI designer is very critical as it will save lots of time and money later down the line.
At Cenango we strongly adhere to the Agile Development methodology. Why Agile? Well, Agile development is an alternative to traditional project management where emphasis is placed on empowering people to collaborate and make team decisions in addition to continuous planning, continuous testing and continuous integration. We split a project down into small parts and teams then set daily goals to accomplish those parts. Daily Scrum meetings are held to help team members report on their progress and correct any problems they are encountering. We encourage our clients to get involved by reviewing completed sections of the project and providing feedback as the project is being developed. Code is hosted on a Beta server for review and testing.
To keep bugs and errors to a very minimum we strongly believe that application testing goes hand in hand with programming and development. For almost every line of code we write, we also write a line of test code that will test the code using automation tools (automation testing). These tests are set to run automatically and they test various use scenarios, this way our test engineers can catch bugs early on and correct them before they are released to the customer. Our testers carry out both automation testing as well as manual user testing. Our code is tested at various stages for security vulnerabilities as well.