Updated: 9/23/2016
Note that for 2017, 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 aitp-web@hotmail.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 AITP National Collegiate Conference and Career Fair® in April 2017 in St Louis, MO.

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. The grading will be based on the information noted in the Problem statement, the Database, Web Site and Documentation will be done after Phase 5. For the Sprints in this years contests, we will be using a Phased Approach for grading, each Phase will be 6 weeks long, and you may use 1 week, 2 week or 3 week Sprints. At the end of each Phase you are required to turn in the paperwork for the Sprints that were completed during that Phase (Please see the Agile Problem Statement for more information).

Team Composition

  • 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 Collegiate Conference and Career Fair® to participate in the final presentation.


Please note there are different schedules for traditional vs. agile development

  • Phase 1 (for all Teams): October 7, 2016
  • Phase 2 for Traditional, Sprints 1,2,3 : November18, 2016
  • Phase 3 for Traditional, Sprints 4,5,6 : January 6, 2017
  • Phase 4 for Traditional, Sprints 7,8,9 : February 17, 2017
  • Phase 5 for Traditional. Sprints 10,11 : March 17, 2017
  • Final presentation at conference: April 8, 2017

For the Agile Based Teams you must complete all Phase Sprints by the end date of those Phases for traditional project management. You must list all of your Sprints and when those parts of the project were completed. Please submit your Sprints each Phase noted.

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.


Problem Statement                               Updated 9/23/2016

Problem Statement – Agile                   Updated 9/22/2016

Sample Contract                                   Updated 9/23/2016

Sample Team Charter Statement        Updated 9/22/2016

Agile Grading Rubric                             Will be uploaded by October 7, 2016

Traditional Grading Rubric                   Will be uploaded be October 7, 2016



Leave a Reply

Your email address will not be published. Required fields are marked *