article thumbnail

AoAD2 Chapter 3: How to Be Agile

James Shore

As we’ve seen in the previous chapters, Agile is a philosophy: a way of thinking about software development. In addition, Agile practices often perform double- and triple-duty, solving multiple software development problems simultaneously and supporting each other in clever and surprising ways. How to Be Agile. Practicing Agile.

Agile 103
article thumbnail

AoAD2 Chapter 6: Invest in Change

James Shore

Large changes—those that directly impact more than 30-70 people—require professional change management. Depending on the size of your organization, your HR department may have change management experts on staff who can help. If not, you can hire consultants. The manager was looking for someone to lead a small team.

Agile 94
Insiders

Sign Up for our Newsletter

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

article thumbnail

Why a data scientist is not a data engineer

O'Reilly Media - Ideas

All of their complaints about Java verbosity or why programming best practices need to be used come into focus with large software projects. One way to know the difference between data scientists and data engineers is to see what happens when they write their own distributed systems. A few of these are: Source control.

article thumbnail

From Engineer to Executive: An Interview with Eric Muntz of MailChimp

Marcus Blankenship - Podcasts

Announcer: Welcome to the Programming Leadership podcast, where we help great coders become skilled leaders and build happy, high-performing software teams. Engineers having seen that, then it turned into an Engineering 1 job, helping fix bugs and work on their software. It was a very small little consulting practice.