If you know ahead of time that the software is going to be purchased instead of built, how does the requirements process differ from that of a standard development project? I think a key difference in a supplier selection project comes from the fact that you are buying functionality that already exists. And while you [...]
Archive for April, 2007
I’ve recently had some troubles getting all team members to provide approval for a requirements document. I know the reluctance is a sense of not knowing what the requirements contain. I thought maybe if I could tailor how I disseminated the information to different communication styles, I could receive feedback in a more complete and [...]
On every project in the software world there are numerous owners responsible for the success of the project and whether the business objectives are met at the end. Some companies has some embraced the idea of group ownership that they forgotten the value of accountability and hierarchy and, as a result, encounter problems completing projects. [...]
When I was a teenager, I cut grass for the Tooth Fairy. Quite frankly, she was unpleasant to work for, and she was very slow to pay. I resolved to never work for anthropomorphic representations of mythological creatures again. To my dismay, I found myself rolling off a project a few months ago, and I [...]
In my last post, I explained the difference between validation and verification. In this post, I’ll further explain validation and provide some best practices. To ensure that software requirements validation goes smoothly, the following questions should be posed: Are all requirements necessary and sufficient? Do lower level detailed software requirements meet the objectives of higher [...]
