Tweet
Project Charter
This is first draft for a project charter. Please take a look at the attachment (Word 2003 format). Getting this into everybody's hands and making changes to something we all agree to is very important. If you have questions about the "Extreme Programming" methodology please check this link:
Obviously, we can't do the pair-programming parts, but I think the iterations, customer stories, and targeted incremental release schedules are things that will help us organize our efforts.
The central idea behind the "customer stories" is to break this HUGE project down into manageable parts. In some cases very small parts, like one procedure at a time.
With each small part tested before it goes into the release version errors & bugs will be minimized. Breaking it down into its smallest parts should make it easier to track and build. As always, open to ideas and suggestions.
Brian Chirgwin is working on setting up a site where we can store the actual project code with SVN and team access. More on that later from Brian.
Licensing is still an issue. I will compose a suggested license and post it today.
Fasten your seat belts, here we go!
Stan
Obviously, we can't do the pair-programming parts, but I think the iterations, customer stories, and targeted incremental release schedules are things that will help us organize our efforts.
The central idea behind the "customer stories" is to break this HUGE project down into manageable parts. In some cases very small parts, like one procedure at a time.
With each small part tested before it goes into the release version errors & bugs will be minimized. Breaking it down into its smallest parts should make it easier to track and build. As always, open to ideas and suggestions.Brian Chirgwin is working on setting up a site where we can store the actual project code with SVN and team access. More on that later from Brian.
Licensing is still an issue. I will compose a suggested license and post it today.
Fasten your seat belts, here we go!
Stan
Comment