Preview Mode Links will not work in preview mode

Agile Coaches' Corner shares practical concepts in an approachable way. It is for agile practitioners and business leaders seeking expert advice on improving the way they work to achieve their desired outcomes. If you have a topic you'd like discussed, email it to, or tweet it with #agilethoughtpodcast.

Nov 30, 2018

Today’s episode of Agile Coaches’ Corner is all about full cycle development. Joining your host is Eric Landes — a colleague of Dan’s and a certified professional Scrum trainer.


Eric comes from a DevOps background, originally starting out as a developer. Currently, he serves as a Senior DevOps Consultant, ALM Director, and Solutions Architect. In his roles, he helps clients deliver value to customers in their software delivery pipeline, and has tons of experience leading organizations in adopting Agile and Lean frameworks, like Scrum and Kanban. His specialties are in Agile Project Management, Lean Software Development, Enterprise Project Management Implementation, and many more.


In this episode, Eric explains what a full cycle developer is, what a full cycle development team looks like, who he sees this model working for, how to take steps towards this model and improving your team, and where to get started. He also gives a ton of recommendations, valuable resources, and actionable tips and tricks you can begin using today.


Key Takeaways

  • What is a full cycle developer?
    • Your development team has all the skills needed to build, deploy, etc.
    • Responsible for the full software lifecycle
    • Your team owns it from beginning to end
  • What to keep in mind when transitioning to Agile or full cycle development:
    • The journey takes a long time and the company needs to support the workers through structure and community
    • A good leader is crucial
  • Who does full cycle development work for?
    • It depends on the context — experiment to find out what works for your team
    • Not everybody; different models for different organizations
    • Identifying the problem you’re trying to solve can indicate which model you should use
  • Steps to take towards improving your DevOps team:
    • Measure to help drive improvement
    • Monitor things in production so you can give feedback to the team on what’s working and what’s not
    • Implement hypothesis-driven development
  • Where to get started on your full cycle development journey:
    • Start with Agile and XP principles if you haven’t already
    • Check out the Netflix Tech Blog
    • Understand the principles and practices of DevOps
    • Be sure to experiment, experiment, experiment

Key Learnings:

  • A full cycle developer has a general skill set and is responsible for the whole software lifecycle
  • The transition to Agile or full cycle development takes a long time — the company needs to support their workers in this transition through structure and community
  • The full cycle developer model doesn’t work for all companies; you should experiment to see what works best for your team
  • Drive improvement by measuring data and providing feedback


Mentioned in this Episode:

DevOps Enterprise Summit

Eric Landes’ LinkedIn

Full Cycle Developers (Netflix Model)

Woody Zuill’s LinkedIn

“7 Habits of Successful DevOps” (with Sam Guckenheimer)

Implementing Hypothesis-Driven Development

XP Principles

Netflix Tech Blog



Eric Landes’ Book Picks

Turn the Ship Around!: A True Story of Turning Followers into Leaders, by L. David Marquet

Training from the Back of the Room!, by Sharon L. Bowman


Want to Learn More or Get in Touch?

Visit the website and catch up with all the episodes on!

Email your thoughts or suggestions to or Tweet @AgileThought using #AgileThoughtPodcast!