Skills Inventory

Posted October 18, 2018 by Mike Rieser in Coaching, Learning

A team is asked to take on a special project but they feel uneasy because they lack all of the skills necessary for a successful outcome. Have you experienced that problem before? Perhaps a Skills Inventory could help. This is a skills inventory I helped a team create in the past (I’ve redacted their names […]
Read more

No comments


How long is too long for a build?

Posted July 6, 2018 by Brett Schuchert in Continuous Delivery, Learning

Synopsis Short builds enable responding to change, continuous code improvement, and keeping your customers happy. When the build slows beyond certain thresholds, there are predictable responses by a team that lead to slower builds, lower code quality, and continuous code rot. We’ll look into why this is, why it is worth investing in speeding up […]
Read more

2 comments


A Few Tips for Mob Programming

Posted June 20, 2018 by Tim Ottinger in Learning

Mob programming is great stuff! We have found it to be the best way (so far) to teach technical skills to teams of programmers, and the best way for them to continue developing and teaching their skills well beyond our workshops. Here are a set of tips that help us to make mobbing more successful […]
Read more

1 comment


Managing Programmer Productivity

Posted December 11, 2017 by Tim Ottinger in Amplify, Culture, Learning, Mob Programming, Tech Safety

Several decades ago, the software industry was obsessed with counting lines of code per programmer per month. That metric practice famously drove teams to create bloated, defect-ridden software products. After only a few years, the practice was abandoned as detrimental. Sadly, the biases and flaws behind that practice are with us still, influencing our practices […]
Read more

6 comments


Make Your Testing Affordable

Posted November 28, 2017 by Tim Ottinger in Learning

It’s great to have reliable tests in your pipeline to avoid escaped defects and to shorten the feedback loop for your programmers. Sometimes the build-and-test processes becomes a productivity-limiting problem. What do you do when your test suite takes too long to run?
Read more

No comments


Make People Awesome through Real Work

Posted April 5, 2017 by Tim Ottinger in Learning

Typical training workshops are informative and can be a lot of fun. Teams get away from their normal work for a week or so, try out new technologies and techniques on prefab examples, give the instructor a quick rating, and then go home to their normal jobs. Is this the time for traditional classroom training?
Read more

2 comments


Transcend the “Feature Factory” Mindset Using Modern Agile and OKR

Posted March 18, 2017 by alex in Agile Transition, Culture, Estimates, Kanban, Lean Startup, Learning, Modern Agile, Trust

By Alexandre Freire Kawakami and Felipe Castro Agile adoption in most companies focuses on software delivery. Very few achieve business agility.
Read more

No comments


Cycles of Mistrust

Posted January 24, 2017 by Joshua Kerievsky in Anzen, Anzeneering, Learning, Modern Agile

Have you ever felt that someone’s behavior was hostile or aggressive towards you, formed a negative opinion about them and then taken protective action(s) against them? If so, you’ve likely participated in a Cycle of Mistrust. In their must-read book, Driving Fear Out of the Workplace: Creating the High-Trust, High-Performance Organization, Kathleen Ryan and Daniel […]
Read more

3 comments


What Should We Measure?

Posted November 17, 2016 by Tim Ottinger in Learning

The Agile world is awash in metrics and measures, but most provide little benefit to teams. What if we could change our set of measurements to support safer software development, continuous improvement, happiness of our project community, and careful craftsmanship? In short, what are some Modern Agile metrics?
Read more

2 comments


Evolution, Cupcakes, and Skeletons: Changing Design

Posted November 15, 2016 by Bill Wake in Learning

What’s the best way to deliver and grow systems? There are several possible approaches. One approach is pure waterfall: “plan the work and work the plan”, phase by phase, with a big bang delivery at the end. Measure progress by “(estimated) % complete”. A second approach is used by many Scrum teams: develop a Release […]
Read more

No comments