testing

MPD

When to Spend Time Architecting

  Thierry poses a question I’ve heard in several of my PM workshops this week and last week: When should the team do the architectural work? Thierry’s concerned if his team continues to implement by feature, how can the team do the architectural work? If they take an iteration or two to deal with architecture, […]

MPD, requirements

Implicit Requirements are Still Requirements

  I have an all-in-one machine, a fax/copier/scanner/printer, that I use for copying, scanning and primarily faxing. It’s fine fax machine. And it’s a great copier. But when I hook it up to my computer for scanning to a file, it falls apart. Half the time (or more), my computer can’t establish a USB connection

MPD, project management

PMs Need Trend Data to Guide the Project

I’ve encountered a number of projects where people didn’t know the context of their work. As developers, they were working on the thing they had to develop or fix today. They might remember what they had done yesterday, but there was no sense that they knew what they needed to do tomorrow, or that they

management, MPD

Why Do Some Testers/Test Managers Have a Siege Mentality?

  I facilitated a management problem-solving session at the STARWest conference yesterday. When I was debriefing the activities, one participant said he’s met a bunch of testers and test managers who had a “siege” mentality. He was surprised by that. I’m still surprised when I meet people like that. I sometimes see developers who feel

MPD, requirements

Projects Have Requirements and Goals

  I’m in the midst of writing the PM book (which is why I haven’t blogged much). One of my tips is that projects have both requirements and goals–and that the PM (at least) needs to know the difference. A requirement can be a use case, user story, a shall statement, whatever. So can a

MPD, risk

Reducing Infrastructure Risk

  It’s been quite the Monday so far. My office toilet started spewing water, a cabinet door fell off one of the cabinets in the kitchen, and I’m trying to back up and duplicate my hard disk because both latches on my Powerbook broke at the Agile conference and I need to send my computer

MPD

Testing Design

In Architects Must Write Code, several architects responded that I was too prescriptive (I’m summarizing their comments). Maybe. But I don’t think so. I’m in a nice hotel, where things just don’t work completely right. Yes, the hotel is clean (that’s the big thing with me). The hotel upgraded me to a suite with an

MPD, risk

Degrading Gracefully is an Oxymoron

  I changed ISPs last Friday. At some point Friday, my ISP bounced my email with a strange (to me) message. This is the same ISP that had problems just a few months ago, so I was done. I need email up virtually 100% of the time. And if I can’t receive email, I need

MPD

A Sometimes Useful Practice: One Automated Test per Feature

  Not every product has smoke tests (a series of tests you can run after each build to make sure the product works well enough to continue development and testing). Smoke tests provide early feedback to developers about their work. So, for the last several years, I’ve been suggesting to my clients that as they

defect, MPD

Tirade on Stupid User Interfaces

  I have several accounts with a credit card company: two cards and a merchant account. They don’t want the expense of printing monthly statements for the merchant account, so they sent me a letter to enroll my merchant account in online statements to avoid the paper charge. In my default browser (Safari), I attempt

Scroll to Top