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

TO THE GOOD STUFF

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

Listen on Apple

Listen on Spotify

Listen on YouTube

Josh and Tanner explain that if a project has no structure or communication, it can be difficult to complete successfully. They tell the story of a client who originally worked with a different development company but switched to RedSky Engineering partway through the project timeline. The original company didn't communicate the project timeline, features were missing, and the overall product was unfinished. Josh and Tanner go over their process and what they do to avoid this error. They say that it’s important to have a clear understanding of what the client wants before starting work on a project. They also recommend setting up regular check-ins and communication channels so that everyone is on the same page.

Also Check Out

DevShop Stories #6 - The Story of How We Do Our Processes

Why are processes important? We discuss all the technologies we employ to track, manage, and develop throughout this episode. The justifications for using these particular tools and recommendations to improve client relations. We talk about why it is crucial to hold regular meetings with the product

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.

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.