Work out the requirements on a wiki or other doc sharing/editing tool
We have to stop writing up the requirements via multiple draft documents sent around via email. Decrease time from identification of need to contract by streamlining this step. Multiple editors at one time = efficiency.
Chris Hamm commented
Quick update on the mechanics of doing this. . . . . GSA already has the wiki software that many relatied "wiki" sites use. I asked the GSA technical folks to stand up a specific implementation for the BetterBuy project, and it was created and ready for use in under two weeks. I was able to create new pages, and build a structure for the first pilot project myself in about an hour. From a user standpoint, I can already see the value of developing requirements this way rather than emailing MS Word documents back and forth.
Jeff Smith commented
A quick note on the ROI of doing this successfully. The UK's Office of Government Commerce (OGC) reported today a total of £1.4bn savings in its annual statement, with IT making up £196m in procurement savings due to collaboration and a central contracts database. I wonder what kind of comparative studies are being looked at in the Acquisition 2.0 world? follow the url to read more: http://bit.ly/8FgWdq
Chris Hamm commented
One of the hardest aspects of the requirements development process is finding a subject matter expert in the Federal Govertment who likes to write, AND has the time to write well, AND also knows a thing or two about acquisition. Opening up the process to allow multiple authors and industry will absolutely shorten the time required to develop good requirements.
I think using a wiki is important to ensure that the process is open and collaborative. We're using Mediawiki in SF to manage our requirements. However, we're looking for another open source wiki that is more user friendly. Any suggestions?
Dennis D. McDonald commented
Emma - did you havea lot of need to compare versions as they cnaged over time? Or was the primary value based on being able to ensure that people were all working on the same version at a time?
This is a great idea. If top-level management supports the concept and "pushes" it downwards, I am sure the security professionals will find a way for the federal requirements team to communicate and share. The next step will be to involve industry at the appropriate point since they have direct knowledge of the existing capabilities of the market. This is a tougher problem to address, both from a sceuity standpoint, but more imporatantly from a procurement process fairness standpoint.
Within my agency, this is the way my RFP team wanted to work. Getting a tool considered "secure enough" was a challenge. Eventually what we got was a hybrid - a team workspace that tracked versions, even if you still had to work in a word document.