Re: charter update with two year cycle

Jason wrote:

“My proposal does not change the scope of the work that would actually be completed under the draft Charter; it merely removes the signals that would indicate an intention to commit to agile development prior to having experienced what happens to version 2.1.”



It seems like the trick to chartering is to specify as little as possible, in which case that seems sensible…



Also, re-assessing what you’ve learned before the next ‘sprint’ (e.g. starting 2.2) might be considered quite agile ;-)



-Alastair