Rights

February 6, 2008 @ Better Projects from Craig

Vote This Post DownVote This Post Up (No Ratings Yet)
Loading ... Loading ...


You can draw useful lessons from a variety of places. Back when I was an undergraduate student, amongst other things, I studied politics. One of the discussions we had was whether Australia should adopt a bill of rights.

Many readers will instantly jump to the conclusion that of course a bill of rights is an excellent thing, as it protects the rights of the citizens, and especially those from minority and disenfranchised groups.

Well, there are arguments both for and against a bill of rights. A summary of some of the arguments can be read here.

How does this relate to requirements management?
For a start, it's a warning to think through your assumptions, but that is pretty obvious and you don't need to be reminded of that (today).

The point I wanted to suggest is more specific; when defining requirements and designing solutions, be aware that if you entrench certain rights for users - in either systems or processes - you may be forcing them into a mode of operation that someday in the future will fail the business and the customers.






The photo is care of El Fotopakismo at Flickr.
You can see he original here.


This article is syndicated from Better Projects . The original article is available here. Read more in Better Projects, Project Management News .

No tag for this post.
Popularity: 1%
Reminder : PMToolbox has ZERO tolerance to copyright violation and agrees to follow strictly PMI's Professional Responsibility. That's why each post on this site includes a link to the original version at its source site.

Related Posts

Comments

Got something to say?






[?]