When developing a product, it’s important to build things the right way—high-quality code that’s tightly aligned to requirements. But even perfectly built software is worthless if it has no value to the end user. That’s where results-driven development comes in. We explore how to build products the right way, while making sure we're building the right products.
The concept of Dual-Track Scrum was first evangelized by Marty Cagan back in 2012, and more recently elements of it have been incorporated into Google's Design Sprint. We recently wrote about how Dual-Track works from a design perspective, and want to demonstrate how it can be applied in practice. By leveraging Dual-Track Scrum, teams are more focused, reduce their rework and significantly improve their ability to plan while still retaining their agility. In this article, we'll review the benefits of Dual-Track Scrum and show how we implement it in practice using agile tools.
In a recent post, Aurimas talked about product thinking—building what your customers need, and a culture of innovation. In that post, he mentioned a recent workshop wherein one of the executives asked how we could avoid failure. Figuring out a Minimum Viable Product (MVP) is a great place to start. But how do you create a good MVP? And why?
Estimation. Such a hotly debated, time-consuming exercise. Are they a necessary evil? Should we eliminate estimates? Where do we stand?