7. Goals, Non-Goals and
• What do we want to make (better)?
• What is out-of-scope for this project?
• What could happen that would make the situation
• They can tell us if we're on track with what we're building
• They help deﬁne success & accept milestones
• Do they change over time?
• What are the technical risks of this project?
• Stakeholders help prioritize risk
• Is there another, less-risky way of accomplishing the
10. Unclear Requirements
• Identify them early
• Provide context and information that can help clarify
• If we can't clarify them...
• Do we need more data?
• Can we move the decision out until later?
12. – Eric Ries
Creator of the Lean Startup Methodology
“A minimum viable product (MVP) is a product with
just enough features to satisfy early customers, and
to provide feedback for future development.”
13. What is the Minimum Viable
• What is the smallest thing we can build to prove out that we're on
the right track?
• Get something out quickly and iterate
• Are we starting to make progress on our goals?
14. What is the Minimum Viable
• Often times all requirements feel "MVP"
• It's a bit of an art to break up requirements
• Identify what can move out to fast-follow releases
• Custom administration
• Supporting behaviors
• Tech Debt Cleanup / Refactoring *
• What are the MVP workarounds?
26. Leverage Different
• Diversity of backgrounds at Ibotta
• Ask for opinions
• Ask for background / historical information
• Challenge teammates to push themselves
• Delegate research / implementation details
• Listen to diﬀerent ideas; be aware of "Be Like Me"
27. Be Available
• You will write less code while you're tech leading
• Time management
• Review PRs quickly
• Answer any questions
• Pair / Whiteboard
• Handle issues as they come up
29. Be Communicative
• You are the face of the technical implementation of the
• Make sure everyone's aware of project status
• Other Tech Leaders
• Know Your Audience
30. Be Explicit
• Don't assume; if in doubt, talk about it!
• Titles (EM, PM, Tech Lead) vary by company
• "Who is the tech lead?"
• Extremely helpful to...
• Communicate decisions made
• Provide living design docs
• Reiterate the "why"
• Provide visual representations of the solution
41. Project Conﬂuence Page
• One-Stop for all the project info
• Product Briefs
• MVP Descriptions / Decisions
• Breakdown of phased rollouts
• Are owned by the team
• Help with team buy-in on the project
• Write stories from high-level design docs
• Identify cases you didn't think about
• Deﬁnition of done
• Decide how to call out issues and risk we didn't originally
• Decide the checkpoints for stakeholders
• Add additional resources for communication
• Standups / Check ins / Slack Room
44. Iteration Progression
• Make sure we're on track
• Consider the timeline
• Do we need to re-scope or reconsider MVP?
• Are there risks to be prioritized by the stakeholders?
• Beware of external events that might aﬀect the project
45. Iteration Finalization / Retro
• Are we done?
• Did we hit our goals? What about anti-goals?
• Did we complete all necessary fast-follow work / feature ﬂag cleanup?
• What do we move to next?
• Safe-Space Retro
• Are people happy with the solution we built?
• Did everyone have the information needed?
• What could I do (better) next time?