Skip to content

Thoughts on milestones vs. projects

Recently read a really great post by Jade Rubrick on Great engineering teams focus on milestones instead of projects. Recently my team at Venmo decided to switch to kanban in order to deal with constantly changing requirements. Across the organization, historically we've been pretty terrible at managing the scope and controlling for risk of projects. We claim to be agile but we're actually still delivering things as a waterfall. The next step for our team, and is a complement to the flexbility of kanban, is to truly adopt the mindset of iterative value delivery as discussed in this article.

Some key highlights from the blog post:


Protect your AWS secrets from broad access with resource policies

Granting EKS Cluster Access to AWS SSO Roles