"Think Globally, Act Locally." I recall first hearing this phrase in my youth, applied to connecting our personal choices to environmental impact. I'm thinking about it today in the context of Agile teams: having the bigger picture in mind is an important piece of our overall success. I've seen this recently with several team interactions…
What we have to say, what you want us to hear.
That’s how our blog works. It’s interactive. Let’s learn together.
At what level should you automate tests? Unit test only? GUI-driven tests? Something else? In this blog post, I reflect on a recent experience with both pain and value, and how I am coming to imagine a portfolio approach to test automation.
Are our retrospectives valuable? Are our teams improving? These are two questions that come to mind when I think about comments or articles I've seen about resistance to retrospectives or the time spent in them. I think we can learn a lot by conducting a retrospective… on our retrospectives. Through such a retrospective we seek learning by exploring the following questions:
The Hardest Part of Software Project Management
I have been a software engineer and project manager for over 20 years. Can you guess what I’ve found to be the hardest part of managing software engineer projects? It isn’t persuading the engineers to put aside their running shoes and holey T-shirts for customer visits. It’s not riot prevention when the coffee pot breaks down. It’s figuring out how much it’s going to cost to build the software and then persuading the customer that that’s really how much it costs to build the software. As a rule of thumb, if the price feels right the first time you hear it, it’s too low.