Jonathan Babcock

As I was skimming the book Agile Project Management—How to Succeed in the Face of Changing Project Requirements by Gary Chin, I came across a method I liked for determining whether to use classic or agile management methods.

According to Chin, the determination is made by evaluating project environments and organizational stakeholders.

In my business analysis group, we identify user requirements through use cases, but we don’t use user stories. As I am not extremely well-versed when it comes to some of the agile methods, I thought I’d do some research to learn more about user stores and to determine how user stories are different from use cases and from traditional requirements.

Welcome! This site specializes in providing tips and tools for Business Analysts and systems development in general. If you’re new here, you may want to subscribe to my RSS feed. If you’d prefer, you can also receive my posts directly to your e-mail. Thanks for visiting! Matt Lockhart of Magenic Technologies, Inc. posted an excellent [...]

Ok, time for something light. This is funny stuff. Forget the phases or iterations - THIS is how the development lifecycle really plays out… Right?

Programmer produces code he believes is bug-free.
Product is tested. 20 bugs are found.
Programmer fixes 10 of the bugs and explains to the testing department that the other 10 aren’t [...]

In any kind of business, whether it be it your blog, your retail establishment or your software engineering shop, you have to have a solid, attractive product to be successful. To have a solid product, you have to have an (at least) equally solid approach to defining and developing it.
Now, you can err on [...]