Managing a long-term client relationship, or any relationship for that matter, takes work. You have two organizations, each with its own business goals, attempting to interact with one another through two or more people. Those people also each have their own personal goals and their own way of interpreting and applying all of these goals […]
Consulting is an abstract term and open to interpretation. My interpretation is that, at its core, consulting is about listening, identifying options, identifying tradeoffs, and making a recommendation.
It’s ideal to write stories that can deliver a feature, end-to-end, all at once. But sometimes–especially when integrating with new systems, dealing with complex data processing, or working with a complex story dependency graph—it makes more sense to break up the work so you can deliver each story as its own link in a long […]
Every project falls somewhere on a spectrum between extremes of short-term, get-it-done-ism and eternal, future-proofed longevity. Unfortunately, while you may have a ballpark sense for where a project fits on this spectrum at the outset, each user story needs its own consideration. Working out the right tradeoffs for each of these stories is the project.
Every Agile project needs user stories. But where do stories come from? I’m not asking who types the description into your backlog, I’m really asking how a team works together to create the definition of features that developers should complete.
These days, most companies are expected to have some sort of digital or connected solution. Even industries that have been paper-based or seem removed from connected solutions are feeling pressure. Their executives may think they need a solution, but what should it be? And how do you determine if software is the right solution?
The other day, I was golfing in my league, at a course I had played many times. As I was trying to figure out which club I should use for my second shot, I looked around the course for something specific—an indicator to let me know how far away I was from the pin. This […]
Estimating work is helpful for managing teams and planning for the future. But working through every nuance to provide an estimate can cause frustration and be time-consuming.
Software makers, like surfers, need to be ready for unexpected problems. We need to “surf with our knees bent,” using a stance that takes the unexpected into account. Here are four ways you should adjust your stance to avoid being thrown into the water… metaphorically.
Over the years, I have seen business people and stakeholders become frustrated with the teams who make custom software for them. It’s understandable! Few people have any preparation for their first custom software project. They dive in with enthusiasm and subject matter expertise. Sometimes, it goes great. Sometimes, it goes poorly. I believe that the […]