Remove Leadership Remove Programming Remove Technical Leadership Remove Weak Development Team
article thumbnail

Effective Technical Leadership

NeverFriday

Some notes from the Effective Technical Leadership talk given by David Byttow. Attributes of an effective technical lead. Load-balance work among the team. Knowledge: “A strong tech lead’s knowledge is broad and deep…A tech lead should be a master of several technologies.” ” Activities. .”

article thumbnail

Why Having a Tech Lead or Manager as Scrum Master is a Bad Idea

Agile Pain Relief Notes from a Tool User

Tell them that the role of ScrumMaster is as a servant-leader, coach, and facilitator, navigating the dynamics of the team to ensure Scrum practices are followed and value is delivered effectively. Servant Leadership: prioritizing the needs of the team and helping others to perform as highly as possible.

SCRUM 98
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Nurturing Design in Your Software Engineering Culture

Strategic Tech

I love pair programming and mobbing because every small decision is debated and challenged. For many people, this is a waste of time; it’s pretentious developers geeking out over unnecessary perfectionism. The same mindset should also be applied to architecture; involve the whole team and challenge the small details.

article thumbnail

How Buffer.com Develops Engineering Leadership Skills From Day 1 With Katie Womersley

Marcus Blankenship - Podcasts

Leaders and managers both require skills that can be taught, and developing those employees from within the company can be the most timely and economically efficient way to do so. Setting expectations for leadership growth. Developing leaders from within the organization. Marcus: Welcome to the Programming Leadership podcast.

article thumbnail

Meta-methodology

The Programmer's Paradox

What has become obvious over the years is that for the full range of software development there is no one consistent methodology that will work effectively for every possible project. A methodology is so necessary that a bad one is often better than nothing. The lead software developer.