Blog

As a young product development company we knew that finding a development methodology that was right for us would be key in our ability to structure, plan and control our products. We were initially drawn to a development framework known as waterfall, but quickly realized it wasn't ideal for the type of products we were developing (read about more about our experience in Part One).

When Yeti was in it's infancy we knew that one of the keys to creating successful products would be our ability to adhere to a well defined development methodology that would allow us to structure, plan and control our projects.

Throughout our years of experience in product development one of the hard lessons we've learned is that the development of a great product can be seriously derailed by difficult client behavior. As anyone who works collaboratively with clients can attest to, it’s fairly common to encounter an individual or team that has the best intentions but perhaps lacks basic organizational skills, calls at all hours, or just isn't clear on their vision.

If you've spent any time in product development it's likely you've participated in a sprint retrospective. When done well, these agile meetings can be a great way for your team to weigh in on the previous sprint by discussing the work that was done and issues that were encountered. Unfortunately, in our experience we've learned that not all retrospectives are as effective as they could be. Check out these 7 agile sprint retrospective ideas to make sure your next retro is as engaging and efficient as possible!

The future of any startup hinges on it's ability to hit development home runs early on. 7 in 10 upstart tech companies fail within the first two years, so getting development process correct from the get-go is crucial to your company's success.