Download as PDF, PPTX
Uploaded byMichele Titolo
Tackling the Big, Impossible Project
Michele Titolo discusses the concept of 'big, impossible projects' in software engineering, defining them as large scope initiatives that can involve creating new products or making significant changes to existing ones. She emphasizes the importance of clearly defining the 'definition of done,' identifying dependencies early, and maintaining transparency throughout the project to avoid blockers and ensure communication. Titolo highlights strategies for managing complexity, including breaking tasks into smaller chunks and addressing risky elements first.
More Related Content
Similar to Tackling the Big, Impossible Project
Tackling the Big, Impossible Project
- 1. Tackling The Big, ImpossibleProject Michele Titolo Lead Software Engineer, Capital One
- 2. What Is ABig, Impossible Project? Photo by Johannes Plenio on Unsplash
- 3.
- 4.
- 5. @micheletitolo Can Be NewProduct Or Existing
- 6.
- 7. • Definition ofDone • Dependencies • Transparency 3 Key Things @micheletitolo
- 8. Definition Of Done Photoby Jean-Frederic Fortier on Unsplash
- 9.
- 10.
- 11.
- 12.
- 13.
- 15. @micheletitolo Beginning: 120 Line- ItemSpreadsheet
- 16.
- 17. • New Features •Breaking things into smaller chunks • Surprises the list grew because @micheletitolo
- 18. Dependencies Photo by AnnieSpratt on Unsplash
- 19.
- 20. @micheletitolo Any Work That NeedsTo Get Done That You/Your Team Cannot Do
- 21.
- 22.
- 23. @micheletitolo Plan To GetBlocked
- 24.
- 25.
- 26. @micheletitolo Having a Dependency -> Beinga Dependency
- 27. Transparency Photo by JustinMedina on Unsplash
- 28. @micheletitolo Make It Easyfor Others To See How You're Doing
- 29.
- 30.
- 31.
- 32.
- 33.
- 34.
- 35.
- 36. @micheletitolo Change Was Well Knownand Well Estimated
- 37.
- 38. Photo by KristineWeilert on Unsplash
- 39.