#66 Ben Day, Therapist for Teams

Summary
Ben Day, Plualsight author, coach and trainer talks to me about real world agile and scrum.

Details
Who he is, what he does, Pluralsight, how long it takes to make a course; what agile and scrum are, agile is abstract, scrum is concrete; why daily standups are boring, shortening the cycle between dev and qa; Bryan doesn't think you need the meetings if the project is going well, Ben explains why you do; scrum masters should not be project managers, scrum masters are coaches, scrum masters are not leaders; Ben doesn't like the three common stand up questions; scrum should provide a framework; "multitasking is death"; people don't like being screamed at, how to deal with unrealistic expectations; software development vs software delivery; agile and scrum forget that people are involved, "Ben Day - Therapist for Teams"; it's all about people, leave ego out of it, Difficult Conversations; Ben's scrum courses on Pluralsight.

Links
Pluralsight courses

Book - Difficult Conversations

Download mp3 of podcast

#19 Michael O Church and state of software engineering

Summary
Michael O Church and I discuss whether software engineers have become the manual laborers of the 21st century, open allocation, agile development and how companies could be better.

Details
Michael’s background; being an engineer vs a manager; poor perception of engineers, value of engineers, makers vs takers, engineers as a commodity; not everyone with an MBA is a bad person; engineers are the manual laborers of the 21st century, craziness of interview processes; continuing low status after staring a job, getting credit for work done; open allocation solves many problems, better work, better rewards, happier engineers, language choices, learning new code is harder than learning a new language; agile in an open allocation company, agile as micromanagement, scrum masters, lords and knights, sprints; what Michael’s company would be, constrained open allocation, small, profit sharing; how companies can improve, become engineer driven, engineers should engage more with business, understand convexity; understanding company politics; hard to challenge bad ideas, open allocation helps; arrogance is rewarded; engineers are not always the best at communication or accepting criticism, engineers should learn to fight for themselves; reading broadly, book recommendations, Breaking Bad executions and map reduce.

Book recommendations
Parallel and Concurrent Programming in Haskell: Techniques for Multicore and Multithreaded Programming

Structure and Interpretation of Computer Programs

Concepts, Techniques, and Models of Computer Programming

The Prince

The Art Of War

A Game of Thrones

The John Locke Collection

Other Recommendations
Valve – Handbook for new Employees

Mad Men

Breaking Bad

The Walking Dead

Silicon Valley