Standards and Specifications

The Jahia project is currently based on an agile methodolgy strongly inspired from XP (eXtreme Programming) that we have called Jahia XP.

Jahia XP reflects the main processes of the XP methodology:

• Programming based on User Stories (a list of new functions)
• Strong Customer Interaction
• Small but Frequent Releases
• Better Management of Budget, Resources, Scope, Quality and Time
• Quick Design Session
• Programming and Testing Phases
• • Always keep the Simpliest Design
  • Collective Code Ownership
  • Pair Programming and/or Peer Review
  • Permanent Refactoring
  • Coding and Documentation Standard
  • Teamwork oriented

What is specific to Jahia XP?

Jahia XP observes the basis of the XP methodology but specifies:

• Every Community member may create a new User Story but planning of the developments are decided by the customers in collaboration with the development committee.
  
• Development cycles are based on monthly user story development and on quarterly software release. The last 10 open days of each quarter are in a "freezed mode" with CVS access blocked to focus on release testing.
  
• Each assignation of a new user story is published on the public development mailing list. Once assigned, each in charge developer has to publish a "Design Proposal" on this mailing list. These design/architecture notes will be reviewed and crtized by the community and/or customers until final acceptance.
  
• A permanent task force is in charge of:
• • debugging the product,
  • tested compatiblity with new application servers and databases release,
  • releasing weekly builds and the final quartely production release,
  • adjusting the documentation (User and Developer documentation)
  • and also maintaining the community web site.