Toward an Agile W3C Process

November 2013, Shenzhen, China

Original Process Goal:
Support Waterfall Development

Specification development
- in smaller chunks
- with implementation and experimental deployment
- and developing tests in conjunction with the Specification
Most of this can be done without Process Changes

12 items were identified; 6 of these, retaining the numbers from the original 12, drove the Proposed changes

1. "Integrating implementations into the Process."

2. "Process document does not match modern development methodologies & tools."

4. "Desire for stable reference."

7. "Last Call (LC) may not be as useful as intended."

8. "Going to Last Call (LC) is misleading for Candidate Recommendation (CR) changes."

9. "Lack of test cases is a major contributor to schedule delay."

AB had identified a number of Process Changes that could help
It realized a number of the above issues were concerned with
- Last Call,
- Candidate Recommendation
- and Proposed Recommendation
All these are in Chapter 7, Recommendation Track Process
Reduced focus to updating this chapter
Other changes are possible in the future

Definitions of “widely reviewed” and “implementation experience” have been clarified
Directors response to AC Review MUST be Public prior to Decision