Sprint Cycle

Fourteen day process, beginning at noon on Friday and concluding at noon on the second Thursday following the start.

DAY	Planning / Development	Testing
First Friday	Sprint starts Sprint report presented by Leader of Features Prioritization and Testing sub-group (see below for contents) Process discussed by Program manager, Developers, and Features Prioritization and Testing sub-group Contents of new sprint identified and discussed by Program manager, Developers, and Features Prioritization and Testing sub-group	Testing assignments delivered for sprint just concluded by Leader of Features Prioritization and Testing sub-group

First Friday to Second Thursday a.m.	Development of sprint contents by Developers

First Friday to Second Friday		Testing conducted and reported for sprint just concluded by members of the Features Priortization and Testing sub-group. Report of testing (Accepted / Restarted) are posted directly to corresponding JIRA tickets by Testers.

Second Friday	Start scoping of next sprint by Program Manager and Developers Development work candidates are identified and tagged for next sprint Time estimates to be provided by Developers Sprint plan is posted to the Development wiki	Testing completed

Second Monday-Thursday	Remediation of problems / bugs revealed by Testers is done by the Developers

Second Thursday	Sprint ends Sprint report prepared by Program Manager and delivered to Leader of the Features Prioritization and Testing sub-group What was tested What was completed What was deferred until following sprint

Following Friday	New sprint starts Past sprint report is filed by the Program Manager Wiki pages are updated by the Program Manager

Roles / Responsibilities:

Program Manager

- monitors sprint cycle from start to finish
- collaborates with Developers and Features Prioritization and Testing subgroup to determine development targets for a given sprint and for the sprint backlog.
- may participate as a tester of sprint contents
- prepares sprint reports and sprint plan
- posts sprint plans and reports to Development wiki
- modifies sprint calendar

Developers

- collaborate with Developers and Features Prioritization and Testing subgroup to determine development for a given sprint and for the sprint backlog
- complete sprint contents
- remediate problems reported by testers
- participate in sprint meetings

Feature Prioritization and Testing Sub-Group

- Leader
  - convenes and facilitaties sprint meeting
  - presents sprint report / plan
  - assigns testing to testers

- Members
  - attend sprint meeting
  - participate in discussions of sprint process
  - participate in planning of sprints
  - test sprint contents as assigned

Communciation:

Within development / prioritization team via reports, email, etc.
IRC channel: open 24/7
Standups: 10:00 – 10:30 a.m. EST Mondays and Wednesdays. 11:00 – noon Fridays is for planning within dev team.