A small batch of validated features is better than a big batch of completed features, with Franck Liso

July 29, 2019 Michael Coté

This week, we've got another profile of an application that's benefited from being a product, not just a project. I talk with Franck Liso about Protostellar's logistics business and one of the applications that runs the business. As Franck tells it, the application needed a fresh, well designed second version to extend Protostellar reach beyond just one port. We focus on talking through the design process that used small batches to validate features rather than large, big batches. It's a good example of why doing less code more frequently results in better, more useful software.

Also, check out videos from Pivotal Paris.

Subscribe, follow, feedback

About the Author

Michael Coté

Michael Coté works on the advocates team for VMware Tanzu. See @cote for more.

More Content by Michael Coté
Previous
Product Design, Unicorns, & the Full Stack Designer
Product Design, Unicorns, & the Full Stack Designer

TLDRAt its heart, product design is problem solving that covers the full stack of design. It starts by aski...

Next
Streamline Your Teams' API Design and Strategy with User-Centered Documentation
Streamline Your Teams' API Design and Strategy with User-Centered Documentation

How great documentation allows you to respond quickly to change, prevent developer fatigue, and develop API...