The Development Process: Implementation

Posted on

Welcome back to our series on Coretec’s development process.

So far we’ve sat down and had our Discovery Session. We’ve talked about the scope of your project, done a code review of any existing tech you’ve already had developed, decided on the coding languages moving forward, and now it’s time to present you with our Scope of Work which includes detailed information about your project, and our estimate of how many developer weeks it will take to deliver your final project.

But what’s a developer week?

If you hire a single developer, the number of developer weeks they quote you will be how many weeks it will take them to develop and deliver your project. But when you hire a software development company like Coretec, a Developer Week includes a whole team of people and processes, and takes on a completely different meaning.

First, along with your developer, there’s an entire development team for the developer to reach out to and even engage with in pair programming. Every day, our Lead Developer conducts code review of the previous day’s committed code, so your code is going through two sets of developer eyes at a bare minimum.

And it’s not just coding. The Developer Week also includes testing of your code; tests are programs that we set up to ensure the code delivers the results it’s supposed to. They help us ensure that future work does not inadvertently break the functionality of the previous work. Testing and quality assurance involves a different set of developers who are ensuring the program works as per your requirements and they point out any deficiencies they see. (At Coretec, we offer many testing and quality assurance services on existing systems; see our blog post on Penetration Testing for an example of one of them.)

Then there’s our Project Manager who keeps track of the status of every project. If your project warrants a Waterfall approach, you’ll have invested time with the Project Manager up front, going over the exact flow of the application and approving all the wireframes. If your project is a larger one and we’re working with an Agile methodology, you’ll hear from the Project Manager at the end of every sprint at a bare minimum; we work to your comfort level and can keep you informed on a schedule that works for you. During the sprint call, you’ll receive an update on how the last sprint went and a demo, you’re able to approve or to request changes, give feedback, ask questions, and discuss what’s coming up in the next sprint.

But What’s a Sprint?

A sprint is a period of time to which a certain number of tasks are assigned. We generally work in two week sprints to give us more traction than a one week interval.

At the start of the sprint (ie Monday morning), we pull a certain number of tasks or features from the client’s Discovery Session wishlist that the Lead Developer plans to have developed for the project over the next two weeks.

Each day of the sprint the development team engages in a “standup”; a brief meeting where they each discuss what they did yesterday, any problems they’ve come up against, and what the plan is for today. The Lead Developer re-assesses the tasks for the current sprint, decides what tests need to be completed, and liaises with the Project Manager so everyone knows where we are in the schedule. The daily standup gives everyone a visual of exactly where we are with your project and how much we have left to do to ensure we stay on track and delivery quality work to you within the time frame we estimated.

We hope these last few posts have given you an idea of Coretec’s development process and the expertise we can bring to your next project. Feel free to contact us for more information or to start discussing the wishlist for your next project.