Development - Where the Plan is Put Into Place

TO THE GOOD STUFF

Development - Where the Plan is Put Into Place

RedSky discusses their development methodology and the benefits of using sprints. Tanner Barney discusses the development stage and explains why and how we pre-plan each sprint and procedure.

No items found.

Hey, guys. I wanted to talk about the red sky engineering process today. So we here at Red Sky very much follow the Agile methodology. We plan all of our sprints. We plan all of our processes. We give you a dedicated team of very talented, full stack developers. The one thing that we do that's a little bit different from your traditional agile process is we follow planning.

right that is our bread and butter, very much what we like to do. So we know relative to the team that you have the skill set that they have specific to the front end versus the back end. We know if our developers quote out something based on who it is, where their velocity lands. So as we quote out your project throughout the entirety of the project, particularly the development phase, we get into the sprints, which is your subset of tasks that we break things down to.

We know exactly what that time looks like. So when we tell you this sprint, sprint one, sprint two, sprint three, this is going to be completed. This is what you can expect. This is where we're going to give this presentation to you. We're confident in what we tell you. We know exactly what it's going to be because we know the team.

We know our processes. We have everything completely dialed in based on the exact efficiencies of the developers that we have on the process. It's phenomenal. As we get through the project, you'll see it come to life. Again, we're going to hit these marks because we know the team. We have these processes we follow these processes. It's what we do.

If there's more you want to know, you're more than welcome to visit us at redskyeng.com.

Also Check Out

Devshop Stories #4 - The Story of Don't Be A Karl

H.R. Jacob joins Josh and Tanner in this episode to talk about what it means to not be a Karl. We talk about Karl and the difficulties we faced when dealing with people who didn't suit our cultural environment.

DevShop Stories #11 - The Cost of Skipping User Acceptance Testing

In this episode, we cover user acceptance testing. Which covers user an important part in the software development process. It involves the customer reviewing the software, comparing it to the requirement documents, and ensuring that it meets their expectations.

Devshop Stories #2 - The Story of Why You Hire a Dev Shop

Josh and Tanner explain that if a project has no structure or communication, it can be difficult to complete successfully