We actually have a fairly clean slate here and are free to pick most any process (or mix and match elements from various processes). The biggest culture shock is going to be using any kind of up front documentation. To date the nature of the projects done here has allowed the "jump in and code, document afterwards -- if you get around to it" development process to actually result in successful completion even though it also results in a lot of rebuilding the wheel coding.
Any recommendations on a better then the other's overview of this [XP/Agile]? Before I jump in to Google and pick the top item returned?
--------------
Ian Skinner
Web Programmer
BloodSource
www.BloodSource.org
Sacramento, CA
"C code. C code run. Run code run. Please!"
- Cynthia Dunning
Confidentiality Notice: This message including any
attachments is for the sole use of the intended
recipient(s) and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the
intended recipient, please contact the sender and
delete any copies of this message.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
