Leading Agile

OCTOBER 22, 2018

In the 1960s, it was considered a baseline good practice in software engineering to test your code as you wrote it. The pioneers of software development in that era were proponents of various levels of testing; some advocated “unit” testing and some didn’t, but all recognized the importance of testing code.

Software Review 95

Software Review Infrastructure Engineering Executing 95

Leading Agile

APRIL 15, 2019

At a larger scale, a software delivery organization should limit the number of projects in flight concurrently, and strive to “stop starting and start finishing,” as David Anderson put it. Many software developers will tell you it takes between 10 and 20 minutes to get back into the zone, depending on the task.

Software Review 117

Software Review Underperforming Technical Team Lean Technical Review 117

Leading Agile

FEBRUARY 11, 2019

It’s time now to move forward to the next level of proficiency in software delivery; what we might call “post-Agile.” I’d like to consider the following in this post: Sustainable Pace. Sustainable Pace. How can the same principle be a good idea in 2002 and a bad idea in 2019? What has changed?

Agile 115

Agile Underperforming Technical Team Software Review Technical Review 115

MPUG

OCTOBER 9, 2019

You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. Today’s session is eligible for one PMI PDU in the technical category and the code for claiming today’s session is on the screen now.

Agile 40

Agile Technical Review Lean Underperforming Technical Team 40