One of many improvements the latest version of Microsoft Dynamics Sure Step methodology has brought along is the revised purpose of the Functional Requirements Document (FRD). This document has long served as cornerstone of every Analysis process of every implementation project: it was the main deliverable of the Analysis phase and it both documented customer’s requirements and explained how they will be met with Microsoft Dynamics NAV solution.
Don’t you just love when users come up with new feature ideas at a microprocessor clock rate. Even before you finish developing one, five new requests pop up. This is a disease, and it’s called featuritis!
Some time back, as I was riding a taxi from Prague airport to Holiday Inn hotel, I wondered about the fixed price I was about to pay for the ride.
- “Airport to city is 700 flat.” – said the driver when I asked how much approximately will it cost.
Common wisdom goes that flat rates mean you get it worse than if it wasn’t flat. Indeed, if it was on meter, and if the driver took the shortest route (I had a GPS device on me, I could’ve easily checked it!), the fare would’ve been lower. And yet, I decided I loved the flat rate.