I'm working on a mobile website project, whereby we are taking portions of the Full (desktop) site and making it "mobile friendly". I was asked today if I am documenting what the mobile site ISN'T doing. Meaning what the Full site does that the mobile site isn't.
I have always learned to only document what the system WILL do, not what it DOESN'T do. This was asked by my company's upper management and my guess it's more of a CYA exercise rather than proper practice.
I wanted to get people's opinion on this.
Thanks!
Hi:
If you know what the full site does, and the mobile site is just a subset of it, then it should only take you a little while to come up with the spec for the mobile. Sounds like the real issue is that what the full site does is not fully understood.
Tony
It's completely reasonable to document what a system doesn't do. That's what we call Gap Analysis. Now, if you are documenting what isn't done you don't have to document it at the same level of detail. Only document what makes sense, which is probably feature level and nothing more.
Chris
Remember it is always good practice to document the things you must, should, could and won't do. This is known as athe Moscow technique.
Hi Shaun,
I suggest capturing a list of function points in a spreadsheet then have a column for Full Site and a column for Mobile. Tick the columns where the function is delivered. That should be a sufficient CYA exercise. Of course, get everyone to sign off on your spreadsheet.
Kimbo
brought to you by enabling practitioners & organizations to achieve their goals using: