Saturday, July 2, 2011

Requirements? What requirements?

Recently we came across an organization that was following a development cycle that was so agile that things went live before they compiled!
All kidding aside, have you ever found yourself or your organization in a similar situation? Below linked diagram depicts a possible solution to this ever so common scenario:

In this sample scenario the company uses a central DOC where all features and requests for work to be done by the software team are listed and prioritized. The dev team then goes to work on the features, after they are assigned and report status in a scrum style weekly meeting. The management team meets once weekly where status is reported on the PRIORITY items.



As an output, this simple process will produce the following artifacts:
1. A defined set of business rules for future versions
2. A manual test procedure
3. An automated regression test

No comments:

Post a Comment

Creative Commons License
VGP-Miami Web and Mobile Automation Blog by Alfred Vega is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.