Raines' Rules are available at http://mysite.verizon.net/ambur/raines.htm and in somewhat abbreviated form at http://mysite.verizon.net/ambur/itmra.htm    (38ED)

Please help us document lessons learned and roads not taken by contributing your perspective to the pages we have establshed for each of those "rules", as follows:    (38EE)

RainesRule_1 - Support core/priority mission functions that need to be performed by the Federal government.    (38EN)

RainesRule_2 - Be undertaken because no alternative private sector or governmental source can efficiently support the function.    (38EO)

RainesRule_3 - Support work processes that have been simplified or otherwise redesigned to reduce costs, improve effectiveness, and make maximum use of commercial off-the-shelf (COTS) technology.    (38EP)

RainesRule_4 - Demonstrate a projected return on investment that is clearly equal to or better than alternative uses of available resources.    (38EQ)

RainesRule_5 - Be consistent with Federal, agency, and bureau information architectures which: integrate agency work processes and information flows with technology to achieve the agency's strategic goals ... and specify standards that enable information exchange and resource sharing, while retaining flexibility in the choice of suppliers and in the design of local work processes.    (38ER)

RainesRule_6 - Reduce risk by: avoiding or isolating custom-designed components ...; using fully tested pilots, simulations, and prototypes ...; establishing clear measures and accountability for project progress; and securing substantial involvement and buy-in ... from program officials who will use the system.    (38ES)

RainesRule_7 - Be implemented in phased, successive chunks as narrow in scope and brief in duration as practicable, each of which solves a specific part of an overall mission problem and delivers a measurable net benefit independent of future chunks.    (38ET)

RainesRule_8 - Employ an acquisition strategy that appropriately allocates risk between government and the contractor, effectively uses competition, ties contract payments to accomplishments, and takes maximum advantage of commercial technology.    (38EU)

Return to October 24, 2006, Expedition Workshop Home Page    (38F6)