Today we wanted to help lead developers understand what should be expected of them and also help managers understand what they should be getting from their top software team members.  Please note that this list is not exhaustive but it should help steer you in the right direction in terms of expectations.

Delivery and Quality of Product

  • Following Established Development and Delivery Process
  • The Process Policy
  • Sprint Adherence and Compliance

Communication of Product Status

  • Daily, Standup, Weekly, and Sprint Updates, and Why We Do Them
  • Communication of Blocking or Blocked Tasks
  • Announcements of New Features
  • Communication of Unusual Budget or Resourcing Situations

The Care and Keeping of Happy Customers

  • Customer Sentiment Checkups
  • Gifts and Celebrations
  • Free Services
  • Customer recovery
  • Pleasant Surprises
  • At-No-Charge and Pro-bono work

Clarifications of Expectations

  • Confronting Errors in Clients “Reflective Listening”
  • Constructively Resetting Unrealistic Expectations
  • Apologizing for Post Outcomes While Clarifying Expectations
  • Continuously Affirm the Expertise of Developers and Designers
  • Controlling the Implementation
  • Work Consistent Business Hours
  • Set Expectation of Special After-Hours Circumstances

Selling the Completed Product

  • Affirm Completion of Functionality
  • Highlight Iterative Improvements
  • Set a Positive Tone for Budget Discussions
  • Explain Future Success Plan
  • Explain Process Advantage
  • Proactively Identify and Explain Any Omissions

Encourage Your Team

  • Mention Desirable Traits and Behaviors
  • Treat your Team
  • Mention Team Members in Blogs or Tweets

Sprint Planning

  • Ensure Each Sprint Has a Single High-Level Deliverable
  • Focus on Largest Stories First
  • Add Refinements, Iterative Work, and Polish last
  • Identify and Communicate About Missed Commitments
  • Address Scope Creep
  • Scrum Agile
  • Kanban Agile
  • Measure Sprints in hours, not days
  • Focus on Functionality

Do the Hard Things

  • On the Historical Origins of Give-A-Shit
  • Leadership
  • Responsibility
  • Addressing Unknowns
  • Pre-existing issues
  • Refactoring and Technical Debt
  • Communicate Failures to the Client
  • Ensure Testing is Complete

If you have any more questions about lead developers or feel as if your team could use some guidance please feel free to reach out to us HERE or at

code guidelines developer best practices leadership senior software developer