Business Requirements

[James Barrow]

Awright kids, this is an invitation to brainstorm for 60 seconds.

 

One of my projects at work is documenting the re-platforming of a legacy
app.  The A1 system was developed and used for four years.without any
documentation at all.  No business requirements before the development, no
functional specs, no technical specs, no user guides.

 

The project team for the A2 project has been assembled and were to begin
development once the business requirements were determined (for both the
leagcy app and the new app).  In fact, there was a lot of emphasis placed on
producing the 'as is' documentation for the legacy app.  This is what I have
been working on for a few weeks.

 

Today, one of the powers that be sneezed, shifted a brain cell, and suddenly
decided that no documentation was needed for the 'as is' app.  In fact, he
decided that we could skip the business requirements for the A2 app and go
directly to the functional requirements.

 

At the moment I'm putting together a brief memo that details the importance
of establishing business requirements before starting the A2 project, and
establishing at least some business requirements for the legacy app.

 

Do you agree?  Disagree?  Why?

 

Thanks,

 

Jim