Remove Coaching Remove Culture Remove Engineering Management Remove SCRUM
article thumbnail

Changing How We Change Software with GeePaw Hill

Marcus Blankenship - Podcasts

What if we could create a trade culture that allowed for change rather than relying on mechanical thinking? Drawing on his 40 years in the software industry, GeePaw’s solution is to develop a thick culture in which certain standards are established across the industry. Defining Thick Culture, Thin Culture, and the Frame (4:01).

article thumbnail

AoAD2 Chapter 3: How to Be Agile

James Shore

1 To succeed with Agile, follow these steps: 1 The method in this book is primarily based on Extreme Programming, but it also draws inspiration from Scrum, Kanban, Lean Software Development, the DevOps movement, and Lean Startup. If you have a document-oriented culture, kaizen will help you streamline your documents. Counterintuively.

Agile 103
Insiders

Sign Up for our Newsletter

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

article thumbnail

Scaling Organizational Empathy With Box’s VPE, Saminda Wijegunawardena

Gitprime

In this Perspectives in Engineering interview series, engineering leaders talk about how to build, coach, and scale world-class technology teams. Saminda Wijegunawardena , VP of Engineering at Box, calls this increasing distance “abstraction.” This role doesn’t change whether an engineering org is 5, 500, or 5000 strong.

article thumbnail

Organise your engineering teams around the work by reteaming

Abhishek Tiwari

Both models work on the scale, particularly when the company's core values, priorities, and culture all three are well aligned. As a bare minimum, I can think of an engineering organisation of 6 Spotify like squads with each team consisting of 8-10 people including engineers (frontend/backend), BA, PO, and an agile coach.

article thumbnail

Bridging the PM Gap with Rich Mironov

Marcus Blankenship - Podcasts

According to Rich, this is the result of two very different work cultures existing in the same organization – one that’s collaborative and one that’s highly individualistic. The culture gap can be hard to cross. Differences in design principles between product and engineering management (1:35). Show Notes.

article thumbnail

Bridging the Gap Between Developers and Marketers with Rich Mironov

Marcus Blankenship - Podcasts

According to Rich, this is the result of two very different work cultures existing in the same organization – one that’s collaborative and one that’s highly individualistic. The culture gap can be hard to cross. Differences in design principles between product and engineering management (1:35). Show Notes.

article thumbnail

The One Constant with Don Gray

Marcus Blankenship - Podcasts

And we have no way of, I mean culture is basically invisible. Don: Those two sets of rules pretty much determine corporate culture and a lot of change, especially now that we’re getting into digital transformation and organizational transformation of all of agile transformations, transformation means change. Marcus: I am.