OverviewUpdated: 10/16/2015 Note that for 2016, changes have been implemented to the web project competition to facilitate a wider range of project management approaches. Please read the problems statement carefully, and if you have any questions contact contest coordinator Larry Friedlander at email@example.com and/or leave a comment on this page.
The Web Application Project Competition is a real-life system analysis/design and implementation project. All teams (1 to 5 members) are expected to complete the first 3 phases of this competition in order to qualify for the final product presentation at the National Collegiate Conference in April 2016 in Chicago, IL.
There are many different ways for a Project to be accomplished and we recognize that, the tools and methods you use will be up to the team; this can include Agile/Scrum method, traditional Waterfall method, or another you might pick. As part of the Phase I documentation we are asking for you and your team to write a small description on what method you choose to use (this will help the judges in determining how to grade your project). We will require all teams to submit the same type of documentation at the end of each phase, but how you get to that will depend on what you use for the project method management style.
The grading for the Traditional Methods will stay the same, using the grading matrix we have used for many years. The grading for the Agile/Scrum method will be done by the major
deliverables that the contest requires. It will be up to these teams to come up with a project schedule that takes these deliverables into mind when submitting them for grading. Once I receive your proposed Scrum break down then I will come up with a grading matrix for that team.
- A school may enter more than one project team.
- A team may consist of 1 to 5 team members.
- A student member can be on only one team.
- Each member of the team must be an AITP student member.
- The teams competing in this contest can be part of an academic class and can have undergraduates as well as graduate students (the only stipulation on team members is that they cannot be IT Professionals in the Web programming profession, this will be left up to the AITP advisor to determine the eligibility of all team members).
- At least 2 of the members of the team must be present at the AITP National Conference to participate in the final presentation.
Please note there are different schedules for traditional vs. agile development
- Phase 1 / Scrum 1: November 14, 2015
- Scrum 2: December 11, 2015
- Phase 2/ Scrum 3: February 12, 2016
- Scrum 4: March 4, 2016
- Phase 3 / Scrum 5: March 25, 2016
- Final presentation at conference: April 9, 2016
For the Agile Based Teams you must complete all parts of the Analysis and Design by the end date of the Phase III for traditional project management. You must list all of your scrums and when those parts of the project were completed (ex. Scrum #1 Completed 12/15/15 included the following parts: 2,3,5,7). Please submit your scrums every two weeks (or agreed upon scrum schedule) for grading at that time.
For the Tradition Method Teams you must complete each phase by the dates indicated in the publish schedule of the Problem Statement, and all documents are due at that time. All teams picked for the final Presentation must complete all requirements for the project by the time of the presentation in April. Please make sure your final document includes of the work done, and in a form that follows the steps of the project.