Here is the recording from the 3rd November where I had the pleasure to talk at the Technical Excellence community.
Interesting points in the video:
5:30 One Way To Find Where To Start Coding
6:40 The Key Concept (via John Ousterhout)
7:45 We Are Always In a Product Context
8:00 Project VS Product
9:40 Build the Right It, Built It Right and Right Time
13:00 You Can’t Be Agile If Your Code Sucks
14:55 Talk To Managers About “Risk”
16:00 PretoTyping and the XYZ Hypothesis (via Alberto Savoia)
18:15 ATDD – Start on Day1
19:50 Complicated VS Complex
22:50 How much time should we spend Planning?
27:30 The Model Attachment Syndrome (via Neal Ford)
28:00 Task Breakdown VS Slicing
32:00 Acceptance Testing https://www.youtube.com/watch?v=7CZit… 34:30 Good Things in Product + Relationship to Scrum & Kanban
36:00 Slicing Without a Goal is Dangerous
43:20 Concrete Slices Spark Your Creative Juices
46:00 Technical Slicing
47:45 Every Slice Should Be Driven By an Acceptance Test
49:10 Why should Slice Our Product?
51:00 Deployed VS Released https://youtu.be/RBQz9QhFfdc
52:30 Conway’s Law Extended
56:00 End Of Talk
57:00 #noPlanning Hashtag Idea
57:55 Strong Product Vision Kills Bullshit
1:04:40 Interview Users Where They are Expert In
1:11:00 QUESTION: Do Pareto rules also apply to validate the hypothesis
1:12:40 QUESTION: I would like to know more about Complicated VS Complex.
1:15:00 QUESTION: The moment we are stopping planning and start doing is related to doing MVP instead of huge product?
1:18:55 QUESTION: Slicing and structuring a Team https://www.youtube.com/watch?v=EOKEx…
1:24:05 QUESTION: What Strategies would you use to change the way PMs look at this topic? (Usually they’re biased towards “I’ve always done this way and worked”)