#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

#33 Justin Mills, Yesware


Summary
Justin Mills, software engineer at Yesware tells me about their flat organizational structure and development practices.

Details
Little about Justin and Yesware; team structure, no test team, no defined team leads; no cohesive architecture; shared infrastructure, hierarchy might be needed; getting approval to reduce technical debt; assigning teams to tasks, trying open allocation, ending open allocation; no titles in engineering but other departments have titles; no one in a position to make a tough decision; struggling with agile, speed of development is the goal.
**extended interview** SDLC, frequent releases probably break often,
Justin's hopes for the company's future.

Extended Interview

#31 Jason MacInnes, Draft Kings


Summary
Jason MacInnes, CTO of Draft Kings tells me about their architecture and scaling demands.

Details
A little about Jason; what Draft Kings is, why it's not gambling, how Draft Kings started; controlling growth, SDLC, Agile growing pains, aligning skills; software stack (MySql, RabbitMq, MassTransit), choice of ASP.NET; scaling the system; transitioning to micro-services, dev ops; service level agreements, dealing with unpredictable events; where the statistics and data come from, customer privacy, future work.

#25 Jeff Glennon, Improving Software Delivery

Jeff Glennon

Summary
Jeff Glennon of Software Delivery Labs and I talk about how to improve the software delivery process.

Details
Jeff's background and company, what is software delivery vs project management; getting all teams working together, deathmarch towards a release date; blame always lands on engineering; other problems, forcing new processes on teams, disputes, transparency is the best approach; power and politics, no silver bullet; how to improve the process, responsibility without blame; agile seems to be the only choice, what if the client doesn't want scrum; end to end example, miscommunication, delays, finger pointing, lost money, get to prototype and fire 'em all; when is your work done; outsource mentoring.

Book Recommendations
The Art of Possibility: Transforming Professional and Personal Life

How We Learn: The Surprising Truth About When, Where, and Why It Happens

The Five Dysfunctions of a Team: A Leadership Fable

Presentation Zen: Simple Ideas on Presentation Design and Delivery

The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win

#7 Rebecca O’Dette, Agile at RunKeeper

Discussion with Rebecca O’Dette about Agile development at RunKeeper. We cover Rebecca’s role, company growth over the past few years, development structure, introduction of agile processes, moving from waterfall, choice of scrum over other agile options, first steps in agile, team size, current team structure, changes over past few years, scaling and syncing teams, scrum of scrums, QA and release processes, release bottlenecks, release cycles, missing Microsoft project, agile for marketing, support, business development and user experience, kanban, story points, planning poker, complexity and time, explaining story points to upper management, culture team, vacation, book choice – The Five Dysfunctions of a Team.

Book Recommendations

The Five Dysfunctions of a Team: A Leadership Fable

Good to Great: Why Some Companies Make the Leap…And Others Don’t