If you plan to add a feature or create a new product, there is one overall guideline that might make your efforts more useful. That is this: Know who this feature or product is for. What does that user want to do? How does your product support that user in solving their problem(s)? If you […]
I use many apps on my Mac, iPad, and iPhone. There is clearly something in the air because, during the past three weeks, most of them broke. Here’s a partial list: The password manager (on all three devices, with at least 4 failure modes) Two different health-based apps Various kinds of email-based apps What do
Each week for a little over a year, I’ve been recording a little podcast and video. It’s called “60 Seconds of Johanna’s Writing WIP.” I’m doing this as an experiment for two reasons: Market the writing before I publish it. (Yes, the “launch” is a form of marketing, but I’m also planning to experiment with
How do you know when you finished a feature? You might have a checklist, to make sure multiple people looked at all the artifacts, and that everything is checked in. (This is easier if you work as a mob/ensemble, pair, or swarm.) In addition, a product leader might approve the feature. Finally, the team, a
A reader asked me this question: “How do I report on the 1000 (or so) defects in our system? I have 10 minutes on the status call.” If you are working on a legacy application where the team was not able—for any number of reasons—to maintain technical excellence, you might have a problem like this. So