RealXtend uses the scrum method of project management for it's internal development. Sprint cycles are traditionally 3 weeks long and start on Mondays.

To ensure smooth interaction with the open source community at large, we will have a need to synchronize our scrum cycles with the pulse of the community.

Therefore it is expected that every sprint task that includes, non-trivial amount of design, creation of a Working Group, or beginning a major re-factor or feature implementation should generate an email to the explaining that task's design and implementation rationale -- what, why, and how.

Internally we work in terms of teams, with membership in the team very dynamic, as time goes on.

Currently we have the following teams active:

• User Interface: Implementing functioning UIs
• Communications: Chat, Voice, and Video streaming
• Server: All server-side features
• Scripting: Expose viewer and server features in Python or JavaScript
• Content Creation Tools: Enable features for DCC
• Avatar: Make the avatar rich and portable
• Viewer Framework: API and Internals

• Documentation Priorities

Planned features for the next development cycle.

• Corus M2 Planning
• Corus M3 Planning

Sprints

Milestone 2

• Sprint 1
• Sprint 2
• Sprint 3
• Sprint 4
• Sprint 5
• Sprint 6
• Sprint 7

Milestone 3

• Sprint 1

• Corus M2 Test Plan