project plan for classroom scheduling app

This criterion is linked to a Learning OutcomeReadability

2.0 pts

This criterion is linked to a Learning OutcomeTitle Page

2.0 pts

This criterion is linked to a Learning OutcomePages Numbered

2.0 pts

This criterion is linked to a Learning OutcomeTable of contents

2.0 pts

This criterion is linked to a Learning OutcomeChange History

2.0 pts

This criterion is linked to a Learning OutcomeExternal Refernces

1.0 pts

This criterion is linked to a Learning OutcomeOverallProject goals, objectives, milestones and deliverables stated clearly.

5.0 pts

This criterion is linked to a Learning OutcomeMilestones SufficientAre there sufficient milestones to gauge progress and catch problems before they have a chance to cause irreparable harm to the project?

5.0 pts

This criterion is linked to a Learning OutcomeEstimate Cost and DurationAre there rough estimates for project cost and duration?

5.0 pts

This criterion is linked to a Learning OutcomeHigh level scheduleIs there a high-level schedule that shows the timing of major milesstones and deliverables?

5.0 pts

This criterion is linked to a Learning OutcomeIteration ScheduleDoes the schedule show start and stop dates for planned iterations?

5.0 pts

This criterion is linked to a Learning OutcomeAllocation of features from Requirements documentDoes the project plan show a rough allocation of features (from the requirements document) to iterations?

5.0 pts

This criterion is linked to a Learning OutcomeProject Organization structureIs the project organizational structure defined? Are all roles within the organization structure specified and clearly defined? Are lines of authority and reporting relationships clear from the organizational structure? Are responsibilities and authority assigned to each role? If responsibilities and authority are assigned to each role it should be possible to identify the person and/or procedure responsible for answering each of the following questions: Who decides what features are included in each iteration? Who decides system architecture? How will technical disputes be resolved? Who decides the user interface elements of the product? Who decides how a particular feature will be implemented? Who decides what is or isn’t a necessary requirement? Who has authority to make a change to planned schedule, requirements, or design? Who has authority to add or remove members from the project?

5.0 pts

This criterion is linked to a Learning OutcomeCommunication Plan

3.0 pts

This criterion is linked to a Learning OutcomeDocument on Github

1.0 pts

Total Points: 50.0