19 April 2011

The Requirements Discovery Project

Requirements discovery, and resulting documents and communications activities can be defined as specific projects.  Should they be?  Possibly.  I have been thinking about this topic for years now.

Corporate projects, with a discreet discovery activity and deliverable should probably call out the requirements discovery work as it's own project.  Combining it with the solution delivery component becomes a programme.

I am just making a note for myself now, but this concept lines up with a lot of industry leading thinkers of the last few decades.  And it fits perfectly as a mental model for managing the contextual dependency for requirements discovery up front or parrallel to solution development.

Thoughts?  Should I elaborate further?

Search This Blog