Basketball Camp Management SystemBasketball Camp Management System

Brendan Post

Andrew Proper

Nathaniel Rudd

8 May 2003

• The Basketball Camp Management System (BCMS) was developed for the Messiah College Men’s Basketball program.

• BCMS accommodates the data storage and manipulation needs of the program as related to their summer camp program.

• The system provides process automation and complete reporting utilities.

SummarySummary

BackgroundBackground

• Formerly a single table Access database was used to manage camp data including:– Participant Information– Team Placements– Housing Information– Health Information

• The system provided no automation for routine activities– Team Assignments– Roommate Assignments– Housing Placements– Balance Calculations

• Develop a web application to capture participant information via online registration

• Provide e-commerce solution to paying camp deposit and camp payments

• Store data in robust backend database

• Provide administrative functionality

• Develop automation for routine activities

The Original ConceptThe Original Concept

• Develop a web application to capture participant via online registration

• Provide e-commerce solution to paying camp deposit and camp payments

• Store data in robust backend database

• Provide administrative functionality

• Develop automation for routine activities

The Real World ConceptThe Real World Concept

Concept AnalyzedConcept Analyzed

• Through requirements analysis, modules were prioritized and the scope was reduced.

• Limited resources prevented the ability to develop low priority modules.

• Time constraints and team strengths also produced scope reduction.

Scope ReductionScope Reduction

• Milestone 4 completion report defines project as in a state of caution: Code Yellow.– 9 weeks into project with very limited implementation complete!

– 4 weeks left to complete all implementation and turn application over!

• Implementation takes over all project development time– Time to pull a Parnas and forget about documentation

• “A Rational Design Process: How to Fake It”

Highway to the Danger ZoneHighway to the Danger Zone

• Milestone 5 fails to meet expectations– Implementation not complete

– Development of some modules not yet started

– No significant testing occurs

– Documentation produced at last minute to meet milestone requirements

Caution ContinuesCaution Continues

• Milestone 6 completed– Implementation of all modules completed as desired

– System moved to stable home

– BCMS populated with existing information

– Testing completed

• Project goes code green for turnover to Men’s Basketball program for use this summer

Race to the FinishRace to the Finish

DemonstrationDemonstration

• Robust, stable, web-interfaced database system to manage camp participant and related information.

• Automated support for routine activities– Roommate Assignments– Balance Calculations

• Full reporting capabilities– Participant– Health– Team– League– Financial

BCMS ImpactBCMS Impact

• System Implemented to level desired

• Customized system tailored to client needs

• Modular approach allows for growth

• System migration completed and tested

StrengthsStrengths

• Milestone Lifecycle Approach– Unrealistic for project scope

• Participant Online Registration– Project for another semester

• E-Commerce Integration– Not feasible at this time

• Time, Energy, & Resources– Semester time constraints

– Team member background knowledge

– Maintaining team morale

WeaknessesWeaknesses

• Coach Van Pelt excited about employing the BCMS this summer to handle camp management.– Supportive throughout project

– Helpful in clarifying needs throughout development

• “Can you guys sell it?”– Potential exists for turning project into a product and marketing it

to other programs at Messiah and beyond.

Sponsor AssessmentSponsor Assessment

• Go Agile!– Milestone lifecycle process unrealistic for team with limited

resources, and background knowledge.

– Project scope and requirement unknowns require immediate launch into solid prototyping and implementation.

– The sooner you start building the better.

• Pull a Parnas– Project buried in administrative documentation.

– We found less than 50% of all documentation dramatically assisted development.

Lessons LearnedLessons Learned