Skip to content

Category Archives: Software Development

Admitting that you have a problem

It’s not always easy to recognize when your project is in trouble. Yes, if your project crashes and burns and completely fails to deliver, it’s failed. But sometimes you don’t realize that you’ve  or you’ve built the wrong software and are about to make your users very unhappy. The first step in fixing your project problems is admitting that you have a problem.

Requirements 101: User Stories vs. Use Cases

Here’s a question that I get over and over again: What’s the difference between user stories and use cases? — Ron K. Before I dive into an answer to that question, let’s rewind a little bit and talk about where user stories came from. I like them because they’re a great example of how the [...]

“That estimate seems a little long.”

Ever spend time working up an accurate estimate with your team, and find that it gets rejected because it doesn’t match a magic number in somebody’s head? You did your homework; talked to the people who’ve done this kind of work before, compared your estimate to past projects, and made sure that your estimates are [...]

What about Agile?

One of the best things about writing a Head First book is that you get feedback from other Head First authors. Our editor, Brett (who you may know from Head First OOA&D), got some interesting feedback from Bert Bates. Bert was going through Head First PMP, and pointed out — and rightly so — that [...]