Tejus Parikh

After 14 years of working on startups in Atlanta, GA, in 2018 I moved cross country to be an IC for Amazon.com in Seattle. This blog contains occasional musings about software development and working in the field. If that sounds interesting, follow me on or connect on Linkedin.

Get my next post in your inbox:

Layout comprehensives in an agile process

Posted on June 9, 2020

Pictures may be worth a 1,000 words, but don't assume they are the right ones

Pictures may be worth a 1,000 words, but don't assume they are the right ones

When you peel back the covers on most agile software teams you'll often find a collection of processes that are more accurately modeled by a waterfall. Comprehensive layouts ("comps") created by design teams to often put a hard stop to any true agile process. Comprehensives look like an application. This is doubly true with modern mock-up tools that can simulate user flow. So when it comes time to evaluate the output of the engineering team, there is a natural inclination to compare the live application to the comp and determine success based on how closely they match. This is not agile.

Read the full post »